File scan report
Verdict Safe
Is Among Us.
No antivirus engine detected the established executable, while complete host checks and one sandbox found no confirmed threat despite unusual updater-process injection records.
Read the whole reasonShow less
Strong evidence · Widely seen for a long time, and nothing harmful found.
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 71 flagged
- Flagged 0
- No detection 71
- No result 4
- Code signing Unsigned
- Test run Completed
- First seen 1y ago
Chapter 02
Why we think so
3 points against it and 5 in its favour, checked against the scan evidence.
The reasoning behind this verdict
None of the 71 antivirus engines that checked it flagged the file, and it has been submitted by 2,494 sources over 508 days. One sandbox recorded no malicious verdict or offensive technique, though its reported injection into updater processes and one specific YARA match justify retaining some caution.
The strongest evidence is the absence of detections across 75 engines, including all 17 reporting major antivirus engines. The executable is also well established, with 3,102 submissions from 2,494 sources over 508 days. One completed sandbox produced a clean assessment and mapped no high-risk technique, while reputation checks covered every observed host without an adverse cached result. However, the runtime record names six updater processes as injection targets, and one community YARA rule matched a Cobalt Strike-related filename pattern. Those counter-signals are not corroborated by engine labels, malicious hosts, persistence, dropped files, or a malicious sandbox outcome, so the overall evidence favors benign software with residual uncertainty.
What We Detected
None of the 71 antivirus engines that checked it flagged this executable, including 17 reporting major antivirus engines. It is widely established rather than appearing in 3,102 submissions from 2,494 sources over 508 days. The executable is unsigned, so its publisher identity cannot be authenticated.
Threat Behavior
One completed sandbox produced a clean assessment and recorded no high-risk MITRE techniques, persistence indicators, written files, or files it created. The host-reputation check covered all 17 distinct observed domains and IP addresses and found no known-malicious or known-suspicious hosts. The sandbox nevertheless listed injection into six Google updater processes, which is unusual and prevents an entirely unqualified assessment. One malware-specific YARA rule referenced a Cobalt Strike temporary filename pattern, but no engine identified Cobalt Strike and two other YARA matches were generic debugger and Go-binary rules.
What To Do Now
Use the file only if it came from the expected distributor and behaves as expected. Keep security software enabled, and obtain a fresh copy from an official source if unexpected updater folders, injected processes, or runtime errors appear.
Where this verdict could be wrong3 caveats
- The executable is unsigned, so no publisher identity or certificate history supports it.
- Runtime records list injection into six updater processes, an unusual action that warrants caution despite the absence of an offensive MITRE classification.
- One malware-specific community rule referenced a Cobalt Strike temporary filename pattern, although no antivirus engine identified Cobalt Strike and the other two rules were generic.
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 71 antivirus engines that checked it flagged the file, including 17 reporting major antivirus engines.
- The file has 3,102 submissions from 2,494 sources and has been observed for 508 days.
- The completed sandbox returned a clean assessment and mapped no high-risk techniques.
- All 17 observed hosts received reputation coverage, with none known as malicious or suspicious.
- No packed or high-entropy code, persistence indicators, written files, or files it created were recorded.
- The executable has no digital signature, so its publisher cannot be verified.
- The sandbox record lists injection into six updater processes.
- One malware-specific community rule matched a Cobalt Strike-related temporary filename pattern.
6 sources checked · all complete. See every source
Chapter 03
What it did in our test
It ran in our isolated test environment; no test environment rated what it did as risky.
Test run summary
Capture complete- 8sandbox rule tags
- 3spawned processes
- 6network contacts
- 1filesystem & mutex artifacts
Includes the sandbox verdicts, 8 mapped techniques and every process, file, registry and network entry.
Show the technical evidenceChapter 04
Technical details
None of the 71 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.
File fingerprint
- Last analyzed
- Oct 11, 2026, 10:30 PM UTC
- SHA-256
209d0cda85a2f86a46b6f3f97843dfee86d18259c987708376f6e1bf87d208e3- SHA-1
d3ee59ea8493a4f36a5acffafd42ea85a1928a9c- MD5
b90b3d839872ae022e37a87b9636081c
About this file
Among Us.exe is a Win32 EXE file of 666.6 kB.
- Type and size
- Win32 EXE · 666.6 kB
- Signer
- UnsignedNo code signature.
- First seen
- May 22, 2025On VirusTotal.
- Submitted by
- 2,494 distinct sources
- Packer
- None detected
- Entropy
- 4.53 of 8
First scanned
Includes every engine result (75), 3 matched signature rules, PE section entropy and packers and how widely the file has been seen.
Show the technical evidenceChapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is Among Us.exe safe?
What is Among Us.exe?
How many antivirus engines detected Among Us.exe?
What is the SHA-256 hash of Among Us.exe?
Is it safe to run Among Us.exe?
How up to date is this analysis of Among Us.exe?
Community
Member reviews and reports for this exact file hash.