File scan report
Verdict Low Risk
Is So
Zero detections on an Office Open XML file with no sandbox or external-intel data.
Why not Safe? Only one source had seen it when we scanned it.
Limited evidence · Nothing points to a problem, but little confirms who made it.
Treat the file as untrusted until more engines or sandbox results become available; do not open it on production systems.
Good practice2 tips
Low Risk: no threat found, but we could not fully confirm this file.
Get it from the publisher's own website or app store, not from a re-upload or a link someone sent you.
Keep your security software on, and stop if the file does anything you didn't expect.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
0 of 65 flagged
- Flagged 0
- No detection 65
- No result 10
- Code signing Not applicable
- Test run Not run
- First seen 2mo ago
Chapter 02
Why we think so
3 points against it and 2 in its favour, checked against the scan evidence.
The reasoning behind this verdict
All 65 antivirus engines that checked it returned clean. The file is an Office Open XML document with no prior history or observations from the test run. The evidence is too limited to issue a definitive verdict.
No engine flagged the sample and no major consensus exists. The file type does not support code signing, so the absence of a signature is neutral. Similar filetype matches in the RAG set were also marked unknown due to limited evidence. Without sandbox results or external-intel hits, the evidence is insufficient to classify the file as safe or malicious.
What We Detected
75 antivirus engines scanned the 37 kB Office Open XML file; none reported malicious or suspicious indicators. No YARA, CIRCL or MalwareBazaar rules matched.
Threat Behavior
No sandbox execution data or files it created are available. Network reputation checks were not completed, so host-contact safety cannot be asserted.
What To Do Now
Re-scan after additional engines report or obtain a sandbox trace. Keep security software enabled while the sample remains rare and unseen by most of the community.
- zero engine detections
- no external-intel hits
- rare and prevalence
- zero prior reputation
- no sandbox coverage
6 sources checked · 4 complete · 1 not run · 1 not needed or not applicable. See every source
Chapter 03
Technical details
None of the 65 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
- Aug 13, 2026, 12:51 AM UTC
- SHA-256
b88e7e265c6313916bd99bd0abbc7a5182a84d6c825757564c582f2b01f56e47- SHA-1
5f3079ac0a39c3fd98cde4d8795f609339c43fdf- MD5
9ef29c32f0866c2b041955609582354a
About this file
SoHjhRdU55FBePWaeRjdf.bin is an Office Open XML Document file of 37.6 kB.
- Type and size
- Office Open XML Document · 37.6 kB
- Signer
- Not applicable
- First seen
- Aug 13, 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 5 questions people ask most about this file.
Is SoHjhRdU55FBePWaeRjdf.bin safe?
What is SoHjhRdU55FBePWaeRjdf.bin?
How many antivirus engines detected SoHjhRdU55FBePWaeRjdf.bin?
What is the SHA-256 hash of SoHjhRdU55FBePWaeRjdf.bin?
How up to date is this analysis of SoHjhRdU55FBePWaeRjdf.bin?
Community
Member reviews and reports for this exact file hash.