ZMQActiveX.ocx file report

MD5 63c429a966dcb51da4b0d2bebf7b0313
Latest seen 2024-09-08 23:01:13 (2 years ago)
First seen 2018-07-27 05:05:59 (7 years ago)
Size 2 MB
Publisher Netease
Product ZMQActiveX

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2018-07-27 05:05:59 (7 years ago); latest analysis 2024-09-08 23:01:13 (2 years ago).

Publisher context

Company metadata: Netease. Product metadata: ZMQActiveX.

Digital signature

Signed by NetEase(Hangzhou) Network Co. 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.

ZMQActiveX.ocx is a Windows file recorded in the ThreatInfo database. It is associated with ZMQActiveX. The reported company name is Netease. The current detection status is Undefined, based on the latest analysis from 2024-09-08 23:01:13 (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: ZMQActiveX
Company Name: Netease
MD5: 63c429a966dcb51da4b0d2bebf7b0313
Size: 2 MB
First Published: 2018-07-27 05:05:59 (7 years ago)
Latest Published: 2024-09-08 23:01:13 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-09-08 23:01:13 (2 years ago)
Signed By: NetEase(Hangzhou) Network Co. Ltd.
Status: Valid

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

%programfiles%\ludashi\gamecenter
%appdata%\ldsgamecenter\ldsgamecenter
%programfiles%\ludashi\ludashi\gamecenter
%programfiles%\ludashi\gamecenter
%programfiles%\ludashi\gamecenter
%programfiles%\ludashi\ludashi\gamecenter
%programfiles%\ludashi\ludashi\gamecenter
%programfiles%\ludashi\gamecenter
%programfiles%\ludashi\gamecenter
%programfiles%\ldsgamecenter

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

51.6%
26.6%
6.3%
6.3%
3.1%
1.6%
1.6%
1.6%
1.6%

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

Windows 10 95.4%
Windows 7 4.6%

The most common operating system signal for ZMQActiveX.ocx is Windows 10 with 95.4% 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.

ZMQActiveX.ocx 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: 0x10000000
Entry Address: 0x001657ad

PE Sections:

Name Size of data MD5
.text 1704448 654ff34e88d6e984f002e96292fd1631
.rdata 389632 7f201a5677269c69100314a29d108233
.data 28672 075085f2b20faeb0c0cdb058da4d3eda
.gfids 110080 55bfabf731b16b7ee999ccd1f10e2653
.giats 512 34373211f78c98e18717409c13b53705
.tls 512 1f354d76203061bfdd5a53dae48d5435
.rsrc 10240 6a5b2ef95fa88c02d469f1d6c9a84d3b
.reloc 137216 629a257216e3d70acca3e42389396994

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: