GridinSoft Threat Intelligence
WinHoster.exe threat report
GridinSoft Anti-Malware detection
Detected by GridinSoft before you download
The current ThreatInfo record shows this exact file hash detected as Ransom.Sabsik. Download GridinSoft Anti-Malware to scan the device, confirm whether this file is present, and remove the detected object if it is found.
- Detection name
- Ransom.Sabsik
- Recommended action
- Scan and remove
- Last analysis
- 2021-11-17 21:56:59 (4 years ago)
- File hash
- 3a6a0c884f89d7f8f05f8d0a6aa1c635
Why it matters
Why GridinSoft flags this file
GridinSoft identifies the sample as Ransom.Sabsik.
First seen 2021-11-05 21:16:28 (4 years ago); latest analysis 2021-11-17 21:56:59 (4 years ago).
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
- Compare the MD5 above with the file found on the device.
- Check whether the file appears in the observed locations or under one of the alternate names.
- Run GridinSoft Anti-Malware to confirm the detection and remove the file if it is present.
File context
WinHoster.exe is a Windows file recorded in the ThreatInfo database. It is associated with WinHost. The reported company name is WinHost. The current detection status is Ransom.Sabsik, based on the latest analysis from 2021-11-17 21:56:59 (4 years ago).
If WinHoster.exe appears on your computer unexpectedly, treat it as suspicious. Check its location, digital signature, and recent system changes before allowing it to run. A full anti-malware scan is recommended when this file is detected as Ransom.Sabsik.
File Details
| Product Name: | WinHost |
| Company Name: | WinHost |
| MD5: | 3a6a0c884f89d7f8f05f8d0a6aa1c635 |
| Size: | 66 KB |
| First Published: | 2021-11-05 21:16:28 (4 years ago) |
| Latest Published: | 2021-11-17 21:56:59 (4 years ago) |
| Status: | Ransom.Sabsik (on last analysis) | |
| Analysis Date: | 2021-11-17 21:56:59 (4 years ago) |
Detection screenshot
The screenshot is a visual record of a GridinSoft Anti-Malware detection for this sample. Use the hash and metadata above as the primary identifiers when comparing the file on your system.
Common Places:
| %localappdata% |
| %appdata% |
ThreatInfo has observed WinHoster.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.
Geographic signal
Observed country distribution
ThreatInfo has seen WinHoster.exe across 9 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is India with 30.8% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
The most common operating system signal for WinHoster.exe is Windows 10 with 92.3% 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
WinHoster.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.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
956111ff99091036da0b0dfe207e531f
afa6e3e52c9777878ad3a8dd82170445
04fad8b099f3da2697d56e05a4b773f0
dae28bfd61433c92b984508af324ec42
cd1e316db503f037d3bf772d6d74a2f4
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
GridinSoft detects this file as Ransom.Sabsik
This report identifies WinHoster.exe by MD5 3a6a0c884f89d7f8f05f8d0a6aa1c635. If the same file is present on your device, scan the system and remove the detected object after confirming the hash and location.