Is SoHjhRdU55FBePWaeRjdf.bin safe?
Zero detections on a brand-new Office Open XML file with no sandbox or external-intel data.
All 75 engines returned clean. The file is a newly submitted Office Open XML document with no prior history or runtime observations. Coverage is too low to issue a definitive verdict.
b88e7e265c6313916b…582f2b01f56e47Recommended next actions
Before opening
Treat the file as unverified and avoid opening it until more evidence is available.
If you already opened it
Run a full device scan. If its origin cannot be confirmed, delete this file and use a fresh copy from a trusted source.
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
The reasoning behind this verdict
This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.
All 75 engines returned clean. The file is a newly submitted Office Open XML document with no prior history or runtime observations. Coverage is too low to issue a definitive verdict.
No engine flagged the sample and no tier-1 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 low coverage. 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 dropped children 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 endpoint protection enabled while the sample remains rare and unseen by most of the community.
- zero engine detections
- no external-intel hits
- rare_new prevalence
- zero prior reputation
- no sandbox coverage
Treat the file as untrusted until more engines or sandbox results become available; do not open it on production systems.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 75 engines flagged the file.
Sandbox
PartialRuntime data is present, but no completed sandbox environment is recorded.
Network
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
CompleteRule evaluation completed with no recorded matches.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime behavior was not available
The report does not treat a missing runtime observation as a clean result.
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 0rule hits recorded
- 0 / 75engines flagged
- 1sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
No completed runtime observation is available for this file.
Verdict inputView chapterProvenanceDerivedSourceRuntime coverageObserved at - 02
0 of 75 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 1 time from 1 source.
ProvenanceDerivedSourceSaved report factsObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
YARA rules
No matchesThe rule pass completed without a saved public match.
0 of 75 engines flagged this file
View all 75 engine results
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
How widely this file has been seen
Barely seen in the wild and first surfaced recently. That limits reputation evidence, but rarity alone is not proof of malware.
Fingerprint and provenance
- File name
- SoHjhRdU55FBePWaeRjdf.bin
- Format
- Office Open XML Document
- Code signing
- Not applicable to this file type
- Size
- 36.7 KB
- Last analyzed
- Aug 13, 2026, 12:51 AM UTC
b88e7e265c6313916bd99bd0abbc7a5182a84d6c825757564c582f2b01f56e47Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
There isn't enough information to give this file a clear rating.
- Recovery step 01
Be cautious — an unknown rating is not the same as a clean bill of health.
- Recovery step 02
Open it only when its sender or download source is one you independently trust.
- Recovery step 03
When in doubt, don't open it — or scan it again later once it's more widely seen.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is SoHjhRdU55FBePWaeRjdf.bin safe? What is it?
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.