MyActiveX.ocx file report
ThreatInfo file report
MyActiveX.ocx
Why it matters
Evidence available for this file
No final classification is available yet.
First seen 2017-05-21 18:08:19 (8 years ago); latest analysis 2022-03-24 23:16:09 (4 years ago).
Company metadata: Haihaisoft Co., Ltd.. Product metadata: Haihaisoft Universal Player ActiveX Control.
Signed by Haihaisoft Limited. The signature is reported as valid, but signed files can still be bundled or abused.
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
- Use the hash and metadata below to verify the exact file identity.
- Review publisher, signature, paths, and PE details for inconsistencies.
- Run a local scan if the file appears unexpectedly or starts with Windows.
File context
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 2022-03-24 23:16:09 (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.
File Details
| Product Name: | Haihaisoft Universal Player ActiveX Control |
| Company Name: | Haihaisoft Co., Ltd. |
| MD5: | ec573e6cf5300191b1815a4cac82eb63 |
| Size: | 6 MB |
| First Published: | 2017-05-21 18:08:19 (8 years ago) |
| Latest Published: | 2022-03-24 23:16:09 (4 years ago) |
| Status: | Undefined (on last analysis) | |
| Analysis Date: | 2022-03-24 23:16:09 (4 years ago) |
Overview
| 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.
Common Places:
| %programfiles%\haihaisoft universal player |
| %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.
Geography:
| 26.7% | ||
| 20.0% | ||
| 13.3% | ||
| 13.3% | ||
| 13.3% | ||
| 6.7% | ||
| 6.7% |
The strongest geographic signal for this file is Egypt with 26.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 | 50.0% | |
| Windows 8.1 | 18.8% | |
| Windows XP | 12.5% | |
| Windows Embedded Standard | 6.3% | |
| Windows 8 | 6.3% | |
| Windows 10 | 6.3% |
The most common operating system signal for MyActiveX.ocx is Windows 7 with 50.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.
Analysis
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: | 0x003e77e3 |
PE Sections:
| Name | Size of data | MD5 |
| .text | 4851712 | d8efe92a65ec8ad8553a39f703cc5650 |
| .rdata | 1208320 | 1695b42b37a2b736b1ef893de14f7474 |
| .data | 246272 | 227112392cd6d5a471778900f87f1bd1 |
| .rodata | 512 | a5a27dad246d9ed9fcff5f39ee9093ef |
| .debug_l | 1024 | 2ef8bfe83a0c006ee30611e0ae7bf261 |
| .debug_i | 5120 | 878707d25e8c24412a010f74689736da |
| .debug_a | 1536 | df2b8566260fba0c3c85c33db3054db7 |
| .debug_a | 512 | ce6830552f1417658ec03aec6966cdba |
| .debug_f | 512 | bfd3c00e313437766cc7a30a6a8a9d07 |
| .debug_l | 3584 | 6c660c3ecd8f06e3aa8bea5dbf944439 |
| .debug_p | 512 | 076bcbad46dd8511ab158b6d09cf5b6f |
| .debug_r | 512 | 091d65f08156d9106b0ff56a43b9b536 |
| .rsrc | 66560 | 9fc65591d938ab8291366b03f3408182 |
| .reloc | 324096 | 04718c2f72e54bee45d211a7b625416a |
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:
