File scan report
Verdict Safe
Is Run-
None of the 61 antivirus engines that checked it flagged this tiny batch file, and no external threat intelligence corroborates malware, though behavior in the test run was not…
Read the whole reasonShow less
Moderate evidence · No engine flags it, but no publisher signature confirms who made it.
Good practice2 tips
We found nothing harmful in this file.
Run it only if it came from the developer's own website or an official app store.
Keep your antivirus and Windows updates switched on.
No scanner can promise a file is 100% safe.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
0 of 61 flagged
- Flagged 0
- No detection 61
- No result 14
- Code signing Not applicable
- Test run Not run
- First seen 14d ago
Chapter 02
Why we think so
3 points against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
None of the 61 antivirus engines that checked it flagged the 114-byte batch file, including the major antivirus engines represented in the results. No external threat-intelligence match was found, but the file is and lacks completed sandbox analysis, so its script contents should still be reviewed before execution.
The strongest evidence is the absence of detections: none of the 61 antivirus engines that checked it flagged the file, and all 17 reporting major antivirus engines were silent. MalwareBazaar, CIRCL, and YARAify supplied no corroborating hit or malware-specific rule match. Code signing is not meaningful for a batch file, so the missing signature does not count against it. The five prior file-type matches were all assessed as clean, although file-type similarity alone is weak support because their formats and names differ. The file is only 114 bytes, and seen from one source, which limits reputation confidence. No observation from the test run or complete contacted-host reputation result is available, so the actual commands should be inspected before use.
What We Detected
None of the 61 antivirus engines that checked it flagged the 114-byte DOS batch file. Microsoft, Kaspersky, ESET-NOD32, BitDefender, Fortinet, and the other reporting products supplied no malware label, and no independent detector raised an alert. MalwareBazaar, CIRCL, and YARAify also returned no matching intelligence.
Threat Behavior
No completed sandbox run is available, so the script's commands and runtime effects were not observed. A complete reputation check for any hosts it might contact is also unavailable. Because this is an executable command script, its small size does not by itself prove that its contents are harmless.
What To Do Now
Open the file in a plain-text editor and verify every command before running it, especially commands that download files, invoke PowerShell, alter security settings, or execute another payload. Keep security software enabled and obtain the file again from its expected source if its purpose or origin is unclear.
Where this verdict could be wrong2 caveats
- The batch file is and has only one known submission, so its reputation is not yet established.
- No completed sandbox observation or complete contacted-host reputation check is available, leaving the script's actual commands and runtime effects unverified.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- None of the 61 antivirus engines that checked it flagged the file.
- All 17 reporting major antivirus engines returned no detection.
- No matching malware intelligence or malware-specific research rule was found.
- All five loosely similar historical file-type results received clean assessments.
- The file was first observed very recently and has only one known submission.
- Batch files can execute system commands despite their small size.
- No completed the test run or comprehensive contacted-host reputation check is available.
6 sources checked · 4 complete · 1 not run · 1 not needed or not applicable. See every source
Chapter 03
Technical details
None of the 61 antivirus engines that checked it flag it.
Sources checked
Every check behind this verdict
6 sources checked · 4 complete · 1 not run · 1 not needed or not applicable. Complete means the check returned a usable result; it does not mean the file is safe.
File fingerprint
- Last analyzed
- Oct 12, 2026, 10:25 AM UTC
- SHA-256
e136ace218cec5ef4e8d10330cdf3acf11e1c57b4a0a9c4acaf9e045e0aa379a- SHA-1
66296fe05fd0ce224b387d9493a2e6e2a9fc489a- MD5
78f53a8dbfa24f653533983526cf910a
About this file
Run-Poseidon.cmd is a DOS batch file file of 114 B.
- Type and size
- DOS batch file · 114 B
- Signer
- Not applicable
- First seen
- Oct 12, 2026On VirusTotal.
- Submitted by
- 1 sourceRarely seen: few people have submitted this exact file.
First scanned
Includes every engine result (75) and how widely the file has been seen.
Show the technical evidenceChapter 04
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is Run-Poseidon.cmd safe?
What is Run-Poseidon.cmd?
How many antivirus engines detected Run-Poseidon.cmd?
What is the SHA-256 hash of Run-Poseidon.cmd?
Is it safe to run Run-Poseidon.cmd?
How up to date is this analysis of Run-Poseidon.cmd?
Community
Member reviews and reports for this exact file hash.