GridinSoft Threat Intelligence

264be.dll file report

Under review File reputation report
MD5 2393f25444318d9fef32b656b1962b7a
Latest seen 2022-11-14 23:32:21 (3 years ago)
First seen 2017-05-21 04:03:43 (9 years ago)
Size 749 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:43 (9 years ago); latest analysis 2022-11-14 23:32:21 (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

264be.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:32:21 (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: 2393f25444318d9fef32b656b1962b7a
Size: 749 KB
First Published: 2017-05-21 04:03:43 (9 years ago)
Latest Published: 2022-11-14 23:32:21 (3 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2022-11-14 23:32:21 (3 years ago)

Overview

Signed By: CyberLink
Status: Valid

The signature on 264be.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 264be.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 264be.dll across 69 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Egypt
Share 64.5%
Low High activity

The strongest geographic signal for this file is Egypt with 64.5% 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.2%
Windows XP 20.8%
Windows 10 17.4%
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 264be.dll is Windows 7 with 52.2% 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

264be.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 0x0011f060
Image base 0x1c600000

PE Sections:

Sections 9
Raw data 757760

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

659456 bytes · 87.0% of section data
Uncommon name
MD5 8fc0ca13196d8618fdf3d1798f71f512
4096 bytes · 0.5% of section data
Uncommon name
MD5 e7375d0d5ecedf1de2d1f1f9916f0909
12288 bytes · 1.6% of section data
Uncommon name
MD5 9ebcdbea6efd4e7de377015848c10297
16384 bytes · 2.2% of section data
Uncommon name
MD5 613c9402957a4e87ec96939faf15057c
4096 bytes · 0.5% of section data
Uncommon name
MD5 0d7b2e5a617dd4d5118eb76b7c07b28c
4096 bytes · 0.5% of section data
Uncommon name
MD5 3e058fc5888d2aa7a0b9ba3d1ed0cdfc
45056 bytes · 5.9% of section data
Uncommon name
MD5 191943a314c607bf6ccbd90dfadef720
8192 bytes · 1.1% of section data
Uncommon name
MD5 67a6f80796471c8096b63699500ad688
.clc 4096 bytes · 0.5% 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 2393f25444318d9fef32b656b1962b7a.
  • 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.