GridinSoft Threat Intelligence

cv100.dll file report

Under review File reputation report
MD5 d1d19d83afe38683b1c0bca9c437ec7f
Latest seen 2024-08-04 23:08:05 (2 years ago)
First seen 2017-08-20 08:29:44 (8 years ago)
Size 824 KB
Publisher Intel Corporation.

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-08-20 08:29:44 (8 years ago); latest analysis 2024-08-04 23:08:05 (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.

cv100.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:05 (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: d1d19d83afe38683b1c0bca9c437ec7f
Size: 824 KB
First Published: 2017-08-20 08:29:44 (8 years ago)
Latest Published: 2024-08-04 23:08:05 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-08-04 23:08:05 (2 years ago)
%commonappdata%\assistant\soft\kmplayer\app\kmplayer
%programfiles%\videobooth
%programfiles%
%commonappdata%\rightclick\kmplayer\app

ThreatInfo has observed cv100.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 57.5%
Windows 10 34.2%
Windows 8.1 4.1%
Windows 8 2.7%
Windows XP 1.4%

The most common operating system signal for cv100.dll is Windows 7 with 57.5% 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.

cv100.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 0x000afa57
Image base 0x10000000

PE Sections:

Sections 6
Raw data 839680

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

.text 724992 bytes · 86.3% of section data
MD5 62a5e7921b1f46b78e7df0cb927143c9
.rdata 36864 bytes · 4.4% of section data
MD5 293af0de6aa6b69940014a257f852974
.data 16384 bytes · 2.0% of section data
MD5 b093a0376da0d2a3f9536258358bb60a
.data1 36864 bytes · 4.4% of section data
Uncommon name
MD5 e0ecfff51c9e41e619b7b4d33774aaf1
.rsrc 4096 bytes · 0.5% of section data
MD5 fe39dac679343dd384023c4b447387bc
.reloc 20480 bytes · 2.4% of section data
MD5 7677ad44e5c3e4ab95aee3c8c6a3636c

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 d1d19d83afe38683b1c0bca9c437ec7f.
  • 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.