File scan report
Verdict Suspicious
Is MSD WINDOWS S1
An unsigned, rarely submitted Windows program first seen on Oct 24, 2026, flagged by 4 of the 70 antivirus engines that checked it with generic machine-learning labels, while its…
Read the whole reasonShow less
Why Suspicious? 4 antivirus engines flag it; nothing else confirms it.
Limited evidence · One sign points to a problem; nothing else confirms it.
Avoid running this program unless you can confirm it came from a trusted official source. Rescan it later and keep your security software enabled.
What to do now5 steps
Some signs point to a problem, but nothing confirms it is harmful. Treat it with caution.
What to do
Don't run it unless you're sure where it came from.
Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.
If you can't confirm where it came from, delete it. If you need the program, download it again from the publisher's own website.
It is only 2 days old. If you're unsure, scan it again in a few days; antivirus engines often catch up on new files.
If you already ran it
Stop using it, run a full scan with your antivirus and watch for unexpected behavior or security alerts.
Not sure what to do?
Ask the MalwareTips community before you run it. If you already ran it, follow the cleanup guide.
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
Paste this report's link in your topic so helpers can see what was found.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
4 of 70 flagged
- Flagged 4
- No detection 66
- No result 5
- Code signing Unsigned
- Test run Completed
- First seen 2d ago
Chapter 02
Why we think so
4 points against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
Microsoft and three less reliable engines flagged this unsigned program with generic machine-learning labels, and no malware family is named. The sandbox runs produced a clean combined verdict with no high-risk behaviour. The file has no publisher signature and almost no history, so the evidence is too thin to call it safe or harmful.
The only major detection is Microsoft's generic machine-learning label Wacatac, and 17 other major antivirus engines did not flag it. The remaining detections come from less reliable machine-learning engines and do not name any family. The combined verdict over three sandbox runs was clean: no high-risk techniques, injection targets or dropped files were recorded, and the only network contacts were the analysis machine's background traffic. The program is unsigned, has no publisher history, and has been submitted by only three sources since Oct 24, 2026. Without a signature, wider prevalence or an inspection of the contents, a confident call either way is not supported.
What We Detected
4 of the 70 antivirus engines that checked it flagged this 64-bit Windows program. Microsoft labels it with a generic machine-learning trojan bucket, Wacatac. APEX, Cylance and Trapmine return generic machine-learning verdicts. No malware family is named, and 17 other major antivirus engines did not flag it. The file is unsigned, first seen on Oct 24, 2026, and submitted by three sources. Its resource section is highly compressed, but the antivirus analysis found no packer.
Threat Behavior
The combined sandbox verdict was clean. They recorded no high-risk techniques, no injection into other processes, no persistence and no dropped files. The only network contacts belonged to the analysis machine's background traffic, and our host reputation check flagged neither of them.
What To Do Now
Do not run this program unless you got it from a source you trust and can confirm. If you can, get it from the official publisher, then rescan it later as engine results mature. Keep your antivirus protection enabled.
Where this verdict could be wrong2 caveats
- The combined sandbox verdict was clean and no high-risk techniques were recorded, which fits a benign program flagged only by machine-learning engines.
- The flagging engines all use machine-learning or generic verdicts, and these often misfire on rare unsigned tools.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- The combined sandbox verdict was clean, with no high-risk techniques
- No injection, persistence or dropped files were recorded
- 17 major antivirus engines did not flag it
- No listings in malware reference databases or community rule sets
- Microsoft flags it with a generic trojan machine-learning label
- Three additional engines return generic malicious verdicts
- The program is unsigned, with no publisher identity
- It is rarely submitted and was first seen on Oct 24, 2026
6 sources checked · all complete. See every source
Chapter 03
What it did in our test
It ran in 3 isolated tests; no test environment rated what it did as risky.
Test run summary
Capture complete- 3isolated sandbox runs
- 8sandbox rule tags
- 2spawned processes
- 0network contacts
- 0filesystem & mutex artifacts
What the test run showed
What the file did on a test computer
Confirmed in the test run
Moderate concern: Contains packed or scrambled code that is harder to inspect (common in installers too).
Note: Loaded extra code modules while running.
Sandbox labels we could not confirm (common in safe files too)
Not confirmed: A sandbox rule tagged this run as code injection, but no injected program was recorded.
Not confirmed: A sandbox rule tagged this run as changing how Windows loads code; nothing confirms it.
This file was run on a test computer (a sandbox), not on yours. Labels we could not confirm are listed so you can see them, but they are not treated as evidence against the file.
Recorded behavior
What happened in the test
Grouped by step. The order is not a timeline.
- 1
Input file
The submitted object
- Evidence 1 of 3: FileSeen in the test run
MSD WINDOWS S1XLV.exe
00d3b57da399614e8b3ea748c4a0fb6833f7399e9b287b3c33ec80cafb3d1187
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 3: ProcessSeen in the test run
MSD WINDOWS S1XLV.exe
"C:\Users\<USER>\Desktop\MSD WINDOWS S1XLV.exe"
Test run - Evidence 3 of 3: ProcessSeen in the test run
MSD WINDOWS S1XLV.exe
"C:\Users\user\Desktop\MSD WINDOWS S1XLV.exe"
Test run - +1 more recorded observation
3 facts from the test run. See the full activity list.
What this file did when executed
This file was detonated in 3 sandboxes and its runtime behaviour was observed.
Sandbox verdicts
1- VT: CLEANclean
Techniques observed in the sandbox
8MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1027· Obfuscated code
- T1027.002· Obfuscated code
- T1036
- T1055· Process injection
- T1129· Loads modules
- T1553
- T1553.002
- T1574· Execution hijack
Observed activity
Processes started
2Programs the file ran, with their command lines.
MSD WINDOWS S1XLV.exe"C:\Users\<USER>\Desktop\MSD WINDOWS S1XLV.exe"MSD WINDOWS S1XLV.exe"C:\Users\user\Desktop\MSD WINDOWS S1XLV.exe"
Sandbox background — not the file
2The analysis machine's own processes and connections, recorded in every run.
- VM host
a1672.dscr.akamai.net - VM host
eip-terr-na.cdp1.digicert.com.akahost.net
Chapter 04
Technical details
4 of the 70 antivirus engines that checked it flag it; no publisher signature.
Sources checked
Every check behind this verdict
6 sources checked · all complete. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 4
- Microsoft (major engine)Trojan:Win32/Wacatac.C!ml
- APEXMalicious
- CylanceUnsafe
- Trapminemalicious.moderate.ml.score
File fingerprint
- Last analyzed
- Oct 25, 2026, 7:57 AM UTC
- SHA-256
00d3b57da399614e8b3ea748c4a0fb6833f7399e9b287b3c33ec80cafb3d1187- SHA-1
2b221f4ac022fd8f18c8b617660a51b246b9a994- MD5
371966b665f6faf80b6876312675d1e9
About this file
MSD WINDOWS S1XLV.exe is a Win32 EXE file of 438.8 kB.
- Claims to be
- MSD WINDOWS S1XLVFrom the file's own version information, written by whoever built it.
- Original name
- MSD WINDOWS S1XLV.exeMatches the shared file name.
- Type and size
- Win32 EXE · 438.8 kB
- Signer
- UnsignedNo code signature.
- First seen
- Oct 24, 2026On VirusTotal.
- Submitted by
- 3 distinct sourcesRarely seen: few people have submitted this exact file.
- Packer
- None detected
- Entropy
- 7.30 of 8
First scanned
Antivirus consensus
4 of 70 engines flagged this file
5 of the 75 engines returned no result for this file (file type not supported, or the scan did not finish), so they did not check it.
- Tier-118 engines1flagged
- Tier-235 engines0flagged
- Low-trust17 engines3flagged
View all 75 engine results
- APEXMalicious: Malicious
- CylanceMalicious: Unsafe
- MicrosoftMalicious: Trojan:Win32/Wacatac.C!ml
- TrapmineMalicious: malicious.moderate.ml.score
- AcronisClean
- AhnLab-V3Clean
- AlibabaClean
- alibabacloudClean
- ALYacClean
- Antiy-AVLClean
- ArcabitClean
- AvastClean
- Avast-MobileNo result
- AVGClean
- AviraClean
- BitDefenderClean
- BitDefenderFalxNo result
- BkavClean
- CAT-QuickHealClean
- ClamAVClean
- CMCClean
- CrowdStrikeClean
- CTXClean
- CynetClean
- DeepInstinctClean
- DrWebClean
- ElasticClean
- EmsisoftClean
- ESET-NOD32Clean
- F-SecureClean
- FortinetClean
- GDataClean
- GoogleClean
- GridinsoftClean
- huorongClean
- IkarusClean
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KasperskyClean
- KingsoftClean
- LionicClean
- MalwarebytesClean
- MaxSecureClean
- McAfeeDClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PaloaltoClean
- PandaClean
- RisingClean
- SangforClean
- SentinelOneClean
- SkyhighClean
- SophosClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisNo result
- TencentClean
- TrellixENSClean
- TrendMicroClean
- TrendMicro-HouseCallClean
- TrustlookNo result
- VaristClean
- VBA32Clean
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootClean
- XcitiumClean
- YandexClean
- ZillyaClean
- ZoneAlarmClean
- ZonerClean
Signatures and behavior heuristics
Low-severity pattern matches — worth noting but not on their own cause for alarm.
VirusTotal's sandbox summary maps this run to MITRE T1055 (Process Injection), but no injected process of the sample's own was recorded (the analysis VM's own WMI adapter, crash handlers and Chrome updater are not counted). VirusTotal maps T1055 on about half of all files no engine flags, so the mapping alone is not evidence of injection.
EvidenceT1055 (sandbox MITRE mapping)
Section entropy & packers
No high-entropy executable section or known packer signature was detected. Data and resource sections can still have high entropy without indicating packed code.
How widely this file has been seen
Barely seen in the wild and first surfaced recently. 4 antivirus detections make that low prevalence materially relevant, but rarity alone is not proof of malware.
Chapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is MSD WINDOWS S1XLV.exe safe, or is it malware?
What is MSD WINDOWS S1XLV.exe?
How many antivirus engines detected MSD WINDOWS S1XLV.exe?
What should I do if I already ran MSD WINDOWS S1XLV.exe?
What is the SHA-256 hash of MSD WINDOWS S1XLV.exe?
How up to date is this analysis of MSD WINDOWS S1XLV.exe?
Community
Member reviews and reports for this exact file hash.