GridinSoft Threat Intelligence

wscript.exe file report

Under review File reputation report
MD5 c2c84b385e66969d214caf5ea102c1bf
Latest seen 2023-11-18 23:24:15 (2 years ago)
First seen 2019-09-20 03:28:46 (6 years ago)
Size 165 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Category context

Malware disguised as legitimate software or delivered through deceptive packaging. Related Trojan reports help compare this file with nearby detections, publishers, and hashes.

Timeline

First seen 2019-09-20 03:28:46 (6 years ago); latest analysis 2023-11-18 23:24:15 (2 years ago).

Publisher context

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

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.

wscript.exe is a Windows file recorded in the ThreatInfo database. It is associated with Microsoft ® Windows Script Host. The reported company name is Microsoft Corporation. The current detection status is Undefined, based on the latest analysis from 2023-11-18 23:24:15 (2 years ago). ThreatInfo groups this verdict with Trojan reports for broader family-level investigation.

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
Company Name: Microsoft Corporation
MD5: c2c84b385e66969d214caf5ea102c1bf
Size: 165 KB
First Published: 2019-09-20 03:28:46 (6 years ago)
Latest Published: 2023-11-18 23:24:15 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2023-11-18 23:24:15 (2 years ago)
%system%
%appdata%
%localappdata%
%temp%

ThreatInfo has observed wscript.exe 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 7 98.9%
Windows Vista 1.1%

The most common operating system signal for wscript.exe is Windows 7 with 98.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.

wscript.exe is identified as pe for 64-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 64-bit
Subsystem Windows GUI
Entry point 0x0000973c
Image base 0x0000000100000000

PE Sections:

Sections 5
Raw data 167936

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

.text 120832 bytes · 72.0% of section data
MD5 fefc7468a480777cfd2a4b7ddcef4fa0
.data 2048 bytes · 1.2% of section data
MD5 29e2ef46d473604f79c30ffae015e486
.pdata 3584 bytes · 2.1% of section data
MD5 36251703162d942c79afad84d255ee9c
.rsrc 38400 bytes · 22.9% of section data
MD5 2155df50162eaedbd22446fec618aa91
.reloc 3072 bytes · 1.8% of section data
MD5 f169eb619b97cad336c4125d188ce116

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 c2c84b385e66969d214caf5ea102c1bf.
  • 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. Use the Trojan category to compare similar reports.