264dmmx.dll threat report

MD5 872ee78d055b1a4adb51c2998b6242c7
Latest seen 2025-11-06 23:01:19 (6 months ago)
First seen 2025-11-06 23:01:19 (6 months ago)
Size 705 KB
Publisher CyberLink Corp.

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as Trojan.Heur!. Download GridinSoft Anti-Malware to scan the device, confirm whether this file is present, and remove the detected object if it is found.

Detection name
Trojan.Heur!
Recommended action
Scan and remove
Last analysis
2025-11-06 23:01:19 (6 months ago)
File hash
872ee78d055b1a4adb51c2998b6242c7
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Trojan.Heur!.

Timeline

First seen 2025-11-06 23:01:19 (6 months ago); latest analysis 2025-11-06 23:01:19 (6 months ago).

Publisher context

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

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. Compare the MD5 above with the file found on the device.
  2. Check whether the file appears in the observed locations or under one of the alternate names.
  3. Run GridinSoft Anti-Malware to confirm the detection and remove the file if it is present.

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 Trojan.Heur!, based on the latest analysis from 2025-11-06 23:01:19 (6 months ago).

If 264dmmx.dll appears on your computer unexpectedly, treat it as suspicious. Check its location, digital signature, and recent system changes before allowing it to run. A full anti-malware scan is recommended when this file is detected as Trojan.Heur!.

Product Name: Cyberlink PowerEncoder
Company Name: CyberLink Corp.
MD5: 872ee78d055b1a4adb51c2998b6242c7
Size: 705 KB
First Published: 2025-11-06 23:01:19 (6 months ago)
Latest Published: 2025-11-06 23:01:19 (6 months ago)
Status: Trojan.Heur! (on last analysis)
Analysis Date: 2025-11-06 23:01:19 (6 months ago)
264dmmx.dll detection screenshot

The screenshot is a visual record of a GridinSoft Anti-Malware detection for this sample. Use the hash and metadata above as the primary identifiers when comparing the file on your system.

%programfiles%\final codecs\codecs

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.

100.0%

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

Windows 10 100.0%

The most common operating system signal for 264dmmx.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.

264dmmx.dll is identified as pe for 32 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.

Subsystem: Windows GUI
PE Type: pe
OS Bitness: 32
Image Base: 0x1c600000
Entry Address: 0x002f9060

PE Sections:

Name Size of data MD5
557056 d842b73554464c7fddcbc04d5bf4b865
4096 b7bcd3be4edc990682906cd2f854a9e8
32768 abb580cd4c9b0706a5efc7b8b7f0a429
49152 dc821b8a91ffff990a18f6089bdede07
4096 50433c8e9e24c76dc1ed5b5743d2b51e
4096 15c4c33d5d70c297919c1bf0ab10e7aa
53248 8e39751d5aa96cbd9fe3762c4b746478
4096 14ed006271c4495e1fc14dbcba000c35
.clc 4096 8dd581b84ed5a1e92bbb5fd8c7acfa94

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.

More information: