GridinSoft Threat Intelligence

highgui100.dll file report

Under review File reputation report
MD5 d3e159a9cef48112caa5563408b16b88
Latest seen 2024-08-04 23:08:21 (2 years ago)
First seen 2017-09-27 16:04:34 (8 years ago)
Size 612 KB
Publisher Intel Corporation

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-09-27 16:04:34 (8 years ago); latest analysis 2024-08-04 23:08:21 (2 years ago).

Publisher context

Company metadata: Intel Corporation. Product metadata: Intel® Open Source Computer Vision Library..

Observed locations

ThreatInfo has seen this file in user or system paths listed below. Unexpected locations increase the need for local verification.

Recommended action

What to do next

  1. Use the hash and metadata below to verify the exact file identity.
  2. Review publisher, signature, paths, and PE details for inconsistencies.
  3. Run a local scan if the file appears unexpectedly or starts with Windows.

highgui100.dll is a Windows file recorded in the ThreatInfo database. It is associated with Intel® Open Source Computer Vision Library.. The reported company name is Intel Corporation. The current detection status is Undefined, based on the latest analysis from 2024-08-04 23:08:21 (2 years ago).

ThreatInfo does not have a final classification for this file yet. Use the technical details below to compare the hash, size, signature, and observed locations with the copy found on your device.

Product Name: Intel® Open Source Computer Vision Library.
Company Name: Intel Corporation
MD5: d3e159a9cef48112caa5563408b16b88
Size: 612 KB
First Published: 2017-09-27 16:04:34 (8 years ago)
Latest Published: 2024-08-04 23:08:21 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-08-04 23:08:21 (2 years ago)
%programfiles%\videobooth
%programfiles%

ThreatInfo has observed highgui100.dll in the locations listed above. Files found in temporary folders, user profile folders, startup locations, or unusual application directories should be reviewed more carefully than files installed under a known program directory.

Windows 7 52.3%
Windows 10 38.5%
Windows 8.1 4.6%
Windows 8 3.1%
Windows XP 1.5%

The most common operating system signal for highgui100.dll is Windows 7 with 52.3% of observed hits. If your system differs from the common profile, check whether the file was introduced by a specific installer, archive, or removable device.

highgui100.dll is identified as pe for 32-bit systems. The subsystem is Windows GUI. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.

Format pe
Architecture 32-bit
Subsystem Windows GUI
Entry point 0x0007d597
Image base 0x10000000

PE Sections:

Sections 6
Raw data 622592

Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.

.text 520192 bytes · 83.6% of section data
MD5 bd607c5775f5710ff622a55ae49060db
.rdata 32768 bytes · 5.3% of section data
MD5 b9338607f856b1fa4bce0f8312dbc90d
.data 45056 bytes · 7.2% of section data
MD5 dc5f6472c82e80ff575711a35441a4b1
.data1 4096 bytes · 0.7% of section data
Uncommon name
MD5 5551333e9d8ccef8758ae2d1b9628e20
.rsrc 4096 bytes · 0.7% of section data
MD5 c36c81f250addc347f8d9cf9a5971d8f
.reloc 16384 bytes · 2.6% of section data
MD5 fb1455e3848311650cdb584c77f57078

PE section names and hashes can reveal packing, injected resources, or unusual build artifacts. Sections with uncommon names, very large raw data, or hashes that differ from a trusted copy deserve additional review.

Report conclusion

This file is still under review

ThreatInfo has not assigned a final verdict yet. Compare the file hash, location, signature, and publisher before trusting the file on a production system.

Scan with GridinSoft Anti-Malware Use a local scan if the file origin or behavior is unclear. Check this hash on VirusTotal

Recommended next steps

  • Compare the local file MD5 with d3e159a9cef48112caa5563408b16b88.
  • Check the file path, publisher, and signature against the details in this report.
  • Run a GridinSoft scan if the source, path, or behavior looks unusual.