myactivex.ocx file report

MD5 eb1175c820b680813ace07bee993be47
Latest seen 2021-08-24 20:44:38 (4 years ago)
First seen 2017-06-12 08:12:15 (8 years ago)
Size 6 MB
Signed by Haihaisoft Limited

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-06-12 08:12:15 (8 years ago); latest analysis 2021-08-24 20:44:38 (4 years ago).

Publisher context

Company metadata: Haihaisoft Co., Ltd.. Product metadata: Haihaisoft Universal Player ActiveX Control.

Digital signature

Signed by Haihaisoft Limited. The signature is reported as valid, but signed files can still be bundled or abused.

Aliases

This hash has appeared under multiple file names, which can happen with repackaging, bundling, or deliberate renaming.

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.

myactivex.ocx is a Windows file recorded in the ThreatInfo database. It is associated with Haihaisoft Universal Player ActiveX Control. The reported company name is Haihaisoft Co., Ltd.. The current detection status is Undefined, based on the latest analysis from 2021-08-24 20:44:38 (4 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: Haihaisoft Universal Player ActiveX Control
Company Name: Haihaisoft Co., Ltd.
MD5: eb1175c820b680813ace07bee993be47
Size: 6 MB
First Published: 2017-06-12 08:12:15 (8 years ago)
Latest Published: 2021-08-24 20:44:38 (4 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-08-24 20:44:38 (4 years ago)
Signed By: Haihaisoft Limited
Status: Valid

The signature on myactivex.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%\haihaisoft universal player
%programfiles%
%programfiles%
%programfiles%
%programfiles%
%programfiles%
%programfiles%
%programfiles%
%programfiles%
%programfiles%

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

MyActiveX.ocx
myactivex.ocx

This hash has been seen with multiple file names. Alternate names can appear when software is updated, copied between folders, packed by an installer, or deliberately renamed to avoid recognition. Compare the exact MD5 above before assuming two names refer to the same file.

22.2%
16.7%
11.1%
5.6%
5.6%
5.6%
5.6%
5.6%
2.8%
2.8%
2.8%
2.8%
2.8%
2.8%
2.8%
2.8%

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

Windows 7 45.9%
Windows 10 37.8%
Windows XP 10.8%
Windows 8.1 5.4%

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

myactivex.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: 0x0018c003

PE Sections:

Name Size of data MD5
.text 4859392 59a30427c35d83774690adb9ac0cf4f2
.rdata 1210880 4e451dd7dbe5841669d27f56a999945b
.data 246272 cf6afb1e6e88c75394854b4ac5ef8eb3
.rodata 512 a5a27dad246d9ed9fcff5f39ee9093ef
.debug_l 1024 90c75c38a3541df5b7772cc1d2e84290
.debug_i 5120 9267fbe94e31a76f74c4a88a98e48b3c
.debug_a 1536 df2b8566260fba0c3c85c33db3054db7
.debug_a 512 d1dad754db99736ac102795f23938fd1
.debug_f 512 c9b8af098782b030e2d05cec89fa5609
.debug_l 3584 6c660c3ecd8f06e3aa8bea5dbf944439
.debug_p 512 076bcbad46dd8511ab158b6d09cf5b6f
.debug_r 512 091d65f08156d9106b0ff56a43b9b536
.rsrc 66560 0b7286e832967fc55b9fd7593c58c77d
.reloc 325120 5faa323af6b3b0a23c06ea2f122b0334

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: