GridinSoft Threat Intelligence

264dmmx.dll file report

Under review File reputation report
MD5 a8189f7a407b4127ef37bc3b0a9102ed
Latest seen 2022-11-14 23:37:22 (3 years ago)
First seen 2017-05-21 04:03:44 (9 years ago)
Size 701 KB
Publisher CyberLink Corp.
Product Cyberlink PowerEncoder
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:44 (9 years ago); latest analysis 2022-11-14 23:37:22 (3 years ago).

Publisher context

Company metadata: CyberLink Corp.. Product metadata: Cyberlink PowerEncoder.

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

264dmmx.dll is a Windows file recorded in the ThreatInfo database. It is associated with Cyberlink PowerEncoder. The reported company name is CyberLink Corp.. The current detection status is Undefined, based on the latest analysis from 2022-11-14 23:37:22 (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 PowerEncoder
Company Name: CyberLink Corp.
MD5: a8189f7a407b4127ef37bc3b0a9102ed
Size: 701 KB
First Published: 2017-05-21 04:03:44 (9 years ago)
Latest Published: 2022-11-14 23:37:22 (3 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2022-11-14 23:37:22 (3 years ago)

Overview

Signed By: CyberLink
Status: Valid

The signature on 264dmmx.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
%programfiles%\qvodplayer\codecs\cyberlink
%appdata%\pplive\codec\1.0.0.2
%programfiles%\tencent
%programfiles%\qvodplayer\codecs
%programfiles%\haihaisoft universal player
%programfiles%\tencent\qq player

ThreatInfo has observed 264dmmx.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 264dmmx.dll across 70 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Egypt
Share 64.7%
Low High activity

The strongest geographic signal for this file is Egypt with 64.7% 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 52.6%
Windows XP 20.6%
Windows 10 17.3%
Windows 8.1 7.7%
Windows 8 1.4%
Windows Vista 0.3%
Windows Server 2012 R2 0.1%
Windows Embedded Standard 0.1%

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

264dmmx.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 0x002f7060
Image base 0x1c600000

PE Sections:

Sections 9
Raw data 708608

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

557056 bytes · 78.6% of section data
Uncommon name
MD5 92152530382a66fc8d740df6e5ac1ad4
4096 bytes · 0.6% of section data
Uncommon name
MD5 576dc72929fc052676aa7fb1b4abb75a
32768 bytes · 4.6% of section data
Uncommon name
MD5 8f4294832db7d1866ff662715a6a11fe
40960 bytes · 5.8% of section data
Uncommon name
MD5 00d95d7fc7111a1c16ddafa935cf963c
4096 bytes · 0.6% of section data
Uncommon name
MD5 d68c77e0bd2f8781aad4d684540b0d88
4096 bytes · 0.6% of section data
Uncommon name
MD5 f7398896d5e5787f67673a7ad1445727
53248 bytes · 7.5% of section data
Uncommon name
MD5 1787ae5f809772d8f516eb507c809370
8192 bytes · 1.2% of section data
Uncommon name
MD5 1829e671e9ba599cd8fc71a5fcf4c320
.clc 4096 bytes · 0.6% 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 a8189f7a407b4127ef37bc3b0a9102ed.
  • 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.