GridinSoft Threat Intelligence

WLCoreCaptureDV.dll file report

Under review File reputation report
MD5 faecbe71bd84f8fa4670d6ca78e80cff
Latest seen 2024-08-22 23:06:21 (2 years ago)
First seen 2020-12-23 05:43:15 (5 years ago)
Size 181 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2020-12-23 05:43:15 (5 years ago); latest analysis 2024-08-22 23:06:21 (2 years ago).

Publisher context

Product metadata: WLCoreCaptureDV ActiveX DLL.

Digital signature

Signed by Sorentio Systems Ltd. The signature is reported as valid, but signed files can still be bundled or abused.

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.

WLCoreCaptureDV.dll is a Windows file recorded in the ThreatInfo database. It is associated with WLCoreCaptureDV ActiveX DLL. The current detection status is Undefined, based on the latest analysis from 2024-08-22 23:06: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: WLCoreCaptureDV ActiveX DLL
MD5: faecbe71bd84f8fa4670d6ca78e80cff
Size: 181 KB
First Published: 2020-12-23 05:43:15 (5 years ago)
Latest Published: 2024-08-22 23:06:21 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-08-22 23:06:21 (2 years ago)
Signed By: Sorentio Systems Ltd
Status: Valid

The signature on WLCoreCaptureDV.dll is reported as valid. A valid signature helps confirm publisher identity, but it does not automatically make the file safe if the installer was bundled, abused, or downloaded from an untrusted source.

%commondir%

ThreatInfo has observed WLCoreCaptureDV.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 10 100.0%

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

WLCoreCaptureDV.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 0x00018f0e
Image base 0x10000000

PE Sections:

Sections 5
Raw data 176128

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

.text 106496 bytes · 60.5% of section data
MD5 888164add713724241c646981aa6a963
.rdata 36864 bytes · 20.9% of section data
MD5 da4a2108a116c96bf4aa5701d69c7832
.data 8192 bytes · 4.7% of section data
MD5 8da48cc1b63cff4965a5fb2505e0ac2f
.rsrc 12288 bytes · 7.0% of section data
MD5 0a0ce37ef7d17b3b8ee16347f9d789a8
.reloc 12288 bytes · 7.0% of section data
MD5 41eeda6fec50ba978bb0458c0040433b

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