GridinSoft Threat Intelligence

wshom.ocx file report

Under review File reputation report
MD5 f58923faafcb20984857287c32d828ec
Latest seen 2026-05-08 23:01:16 (2 weeks ago)
First seen 2023-03-02 23:55:42 (3 years ago)
Size 120 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2023-03-02 23:55:42 (3 years ago); latest analysis 2026-05-08 23:01:16 (2 weeks ago).

Publisher context

Company metadata: Microsoft Corporation. Product metadata: Microsoft ® Windows Script Host Runtime Library.

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.

wshom.ocx is a Windows file recorded in the ThreatInfo database. It is associated with Microsoft ® Windows Script Host Runtime Library. The reported company name is Microsoft Corporation. The current detection status is Undefined, based on the latest analysis from 2026-05-08 23:01:16 (2 weeks 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: Microsoft ® Windows Script Host Runtime Library
Company Name: Microsoft Corporation
MD5: f58923faafcb20984857287c32d828ec
Size: 120 KB
First Published: 2023-03-02 23:55:42 (3 years ago)
Latest Published: 2026-05-08 23:01:16 (2 weeks ago)
Status: Undefined (on last analysis)
Analysis Date: 2026-05-08 23:01:16 (2 weeks ago)
%programfiles%\videodownloader
%programfiles%

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

Windows 10 100.0%

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

wshom.ocx is identified as pe for 32-bit systems. The subsystem is Windows CUI. 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 CUI
Entry point 0x00007610
Image base 0x5cd80000

PE Sections:

Sections 6
Raw data 121856

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

.text 75264 bytes · 61.8% of section data
MD5 b0024e20446cdd4d65ad5cc21d520c94
.data 1024 bytes · 0.8% of section data
MD5 a7fc6934bf46db61215b1fd2054a1dcb
.idata 5632 bytes · 4.6% of section data
MD5 95a9e72c0ce31e1ae37480e1bc94b459
.didat 512 bytes · 0.4% of section data
Uncommon name
MD5 183b9518b6d6ecc1ae475becee4d421c
.rsrc 33280 bytes · 27.3% of section data
MD5 31f4b3ca0884eef2713da98ab763ff95
.reloc 6144 bytes · 5.0% of section data
MD5 8b052294014b851656d959a6b93f4e0a

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 f58923faafcb20984857287c32d828ec.
  • 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.