GridinSoft Threat Intelligence

CScript.exe file report

Under review File reputation report
MD5 791af7743252d0cd10a30d61e5bc1f8e
Latest seen 2021-12-06 21:51:42 (4 years ago)
First seen 2017-05-25 20:05:48 (9 years ago)
Size 152 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-25 20:05:48 (9 years ago); latest analysis 2021-12-06 21:51:42 (4 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.

CScript.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 2021-12-06 21:51:42 (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: Microsoft ® Windows Script Host
Company Name: Microsoft Corporation
MD5: 791af7743252d0cd10a30d61e5bc1f8e
Size: 152 KB
First Published: 2017-05-25 20:05:48 (9 years ago)
Latest Published: 2021-12-06 21:51:42 (4 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-12-06 21:51:42 (4 years ago)
%windir%\system32
%system%
%sysdrive%
%sysdrive%\rei\temp\20201109_1556\installer\c_drive\windows

ThreatInfo has observed CScript.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 99.7%
Windows Vista 0.3%

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

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

PE Sections:

Sections 6
Raw data 155136

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

.text 77312 bytes · 49.8% of section data
MD5 923fe5372e084864bc599be4a7ef26f8
.rdata 35840 bytes · 23.1% of section data
MD5 a578d3af4d0b5d9edf5cb66d68885333
.data 2560 bytes · 1.7% of section data
MD5 3b79a1c90a90e95cc34f0d59b86af452
.pdata 4608 bytes · 3.0% of section data
MD5 4e30eba928b5234b91b7bbe30050c1a8
.rsrc 32256 bytes · 20.8% of section data
MD5 5bfb7d9d09771e3ee8d2115a241f1a87
.reloc 2560 bytes · 1.7% of section data
MD5 c0f44d03e60004ceb1fd3305a8388dff

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 791af7743252d0cd10a30d61e5bc1f8e.
  • 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.