GridinSoft Threat Intelligence

bShutdownSched.exe file report

Under review File reputation report
MD5 73a768b3cefecd8af287b5e5fc4dfeb5
Latest seen 2021-01-05 13:47:31 (5 years ago)
First seen 2021-01-03 05:24:29 (5 years ago)
Size 3 MB
Signed by Softland SRL

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2021-01-03 05:24:29 (5 years ago); latest analysis 2021-01-05 13:47:31 (5 years ago).

Digital signature

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

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.

bShutdownSched.exe is a Windows file recorded in the ThreatInfo database. The current detection status is Undefined, based on the latest analysis from 2021-01-05 13:47:31 (5 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.

MD5: 73a768b3cefecd8af287b5e5fc4dfeb5
Size: 3 MB
First Published: 2021-01-03 05:24:29 (5 years ago)
Latest Published: 2021-01-05 13:47:31 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-01-05 13:47:31 (5 years ago)
Signed By: Softland SRL
Status: Valid

The signature on bShutdownSched.exe 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%
%programfiles%\softland

ThreatInfo has observed bShutdownSched.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 10 100.0%

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

bShutdownSched.exe is identified as pe for 32-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 32-bit
Subsystem Windows GUI
Entry point 0x00c40000
Image base 0x00400000

PE Sections:

Sections 6
Raw data 4038144

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

1569792 bytes · 38.9% of section data
Uncommon name
MD5 ebc469733b0413c9f1541d6265accad2
.rsrc 134144 bytes · 3.3% of section data
MD5 351fcb42f82c003b96ee3b6cc4bcf560
.idata 512 bytes · 0.0% of section data
Uncommon name
MD5 c27299dab7daf0cdd3a45dc07a9acf4d
512 bytes · 0.0% of section data
Uncommon name
MD5 68f98458e8510381b153ea91f69c1c9d
dtvanbbv 2332672 bytes · 57.8% of section data
Uncommon name
MD5 f5e8186fb9133bb3c33e4314512d5e08
olotogtr 512 bytes · 0.0% of section data
Uncommon name
MD5 1a860e0c647c9fd069092283eaf4138f

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 73a768b3cefecd8af287b5e5fc4dfeb5.
  • 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.