GridinSoft Threat Intelligence

vc1dc.dll file report

Under review File reputation report
MD5 d45aa0f71f22105288b87ea46cfe3f62
Latest seen 2022-11-14 23:37:53 (3 years ago)
First seen 2017-05-21 04:03:43 (9 years ago)
Size 485 KB
Publisher CyberLink Corp.
Product Cyberlink VC-1 Decoder
Signed by CyberLink

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-21 04:03:43 (9 years ago); latest analysis 2022-11-14 23:37:53 (3 years ago).

Publisher context

Company metadata: CyberLink Corp.. Product metadata: Cyberlink VC-1 Decoder.

Digital signature

Signed by CyberLink. 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.

File context

vc1dc.dll is a Windows file recorded in the ThreatInfo database. It is associated with Cyberlink VC-1 Decoder. The reported company name is CyberLink Corp.. The current detection status is Undefined, based on the latest analysis from 2022-11-14 23:37:53 (3 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.

File Details

Product Name: Cyberlink VC-1 Decoder
Company Name: CyberLink Corp.
MD5: d45aa0f71f22105288b87ea46cfe3f62
Size: 485 KB
First Published: 2017-05-21 04:03:43 (9 years ago)
Latest Published: 2022-11-14 23:37:53 (3 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2022-11-14 23:37:53 (3 years ago)

Overview

Signed By: CyberLink
Status: Valid

The signature on vc1dc.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.

Common Places:

%programfiles%\tencent\qqplayer
%programfiles%\haihaisoft universal player\codec
%appdata%\pplive\codec\1.0.0.2
%programfiles%\tencent
%programfiles%\haihaisoft universal player
%programfiles%\tencent\qq player
%sysdrive%\adwcleaner\quarantine\fraqbc8wsa
%sysdrive%\tencent

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

Geographic signal

Observed country distribution

ThreatInfo has seen vc1dc.dll across 68 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Egypt
Share 65.3%
Low High activity

The strongest geographic signal for this file is Egypt with 65.3% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

OS Version:

Windows 7 50.8%
Windows XP 21.9%
Windows 10 17.2%
Windows 8.1 8.4%
Windows 8 1.3%
Windows Vista 0.3%
Windows Server 2012 R2 0.1%
Windows Embedded Standard 0.1%

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

Analysis

vc1dc.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 0x00080060
Image base 0x1ca00000

PE Sections:

Sections 9
Raw data 487424

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

253952 bytes · 52.1% of section data
Uncommon name
MD5 8df8a2a51793fa9fcb7aac27e6476380
4096 bytes · 0.8% of section data
Uncommon name
MD5 f53b934a16ff1e7567c5f125330eda41
184320 bytes · 37.8% of section data
Uncommon name
MD5 751f8dafd0b28f843a6497babdb000c5
4096 bytes · 0.8% of section data
Uncommon name
MD5 4a947a3d5f598a2abba2aca225cf37df
4096 bytes · 0.8% of section data
Uncommon name
MD5 423c1fead886f4912bdcb8680561882b
4096 bytes · 0.8% of section data
Uncommon name
MD5 2de5c1fe7d7996b19068e0ca335aec71
20480 bytes · 4.2% of section data
Uncommon name
MD5 75752fcc468ba4fdf65b3d6d73ef9836
8192 bytes · 1.7% of section data
Uncommon name
MD5 870c13a71a7b689afb596a2a701f9028
.clc 4096 bytes · 0.8% of section data
Uncommon name
MD5 0e5c04ddfff54ecc51a03c1cadcc2a11

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