GridinSoft Threat Intelligence

cxcore100.dll file report

Under review File reputation report
MD5 3a32f6154f3f0132fbd44fa54bac72ac
Latest seen 2024-08-04 23:08:23 (2 years ago)
First seen 2017-08-20 08:29:44 (8 years ago)
Size 988 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:23 (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.

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

ThreatInfo has observed cxcore100.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 cxcore100.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.

cxcore100.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 0x000bb029
Image base 0x10000000

PE Sections:

Sections 6
Raw data 1007616

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

.text 774144 bytes · 76.8% of section data
MD5 b7cd117457f0920d87d83933b865c952
.rdata 45056 bytes · 4.5% of section data
MD5 148fa6fb4326997af9a8dd5398c04aa6
.data 28672 bytes · 2.8% of section data
MD5 09a89b5b0b9b4ff080398fe9358315f0
.data1 118784 bytes · 11.8% of section data
Uncommon name
MD5 ee04d6a63eb3ad3d53522f73cb09ff7d
.rsrc 4096 bytes · 0.4% of section data
MD5 af3fea2d3d3056ed1c1d628c9109aeae
.reloc 36864 bytes · 3.7% of section data
MD5 7c0a8340185cb8fbcc6844cb7c8c46b5

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 3a32f6154f3f0132fbd44fa54bac72ac.
  • 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.