File scan report
Verdict Safe
Is this Word document safe? Yes, no threats found.
No antivirus engine detected the Word document, and static intelligence found no malware family, hostile rule match, or confirmed malicious extracted child.
Read the whole reasonShow less
Moderate evidence · No engine flags it, but no publisher signature confirms who made it.
The document may be opened with normal Office security controls enabled after confirming the sender and context. Avoid enabling macros or external content unless clearly required and trusted.
Good practice2 tips
We found nothing harmful in this file.
Open it only if you trust the person or website it came from.
Keep your security software and system 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 65 flagged
- Flagged 0
- No detection 65
- No result 9
- Code signing Not applicable
- Test run Completed
- First seen 4mo 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
All 65 antivirus engines that checked it returned no malicious or suspicious finding, including 16 major antivirus engines. Static intelligence and extracted-child checks found no confirmed threat, although no completed sandbox run is available to verify behavior when the document is opened.
The document received zero malicious and zero suspicious detections across 74 antivirus engines. Sixteen major antivirus engines, including Microsoft, Kaspersky, BitDefender, ESET-NOD32, and Fortinet, reported no detection. Research intelligence produced no YARAify rules, CIRCL malicious reference, or MalwareBazaar match. One extracted child was inspected without a malicious result, but its final status remains unknown. Because sandboxCount is zero, no claims can be made about behavior in the test run, and the conclusion rests primarily on broad static scanning.
What We Detected
No malicious or suspicious result appeared across 74 antivirus engines. Research intelligence also returned no YARAify rule match, CIRCL malicious reference, or MalwareBazaar record.
Threat Behavior
No completed sandbox execution is available because no sandbox run was recorded, so behavior in the test run was not observed. One extracted child was inspected and was not identified as malicious, although it remains unresolved rather than confirmed benign. No complete contacted-host reputation result is available.
What To Do Now
The available evidence does not identify a threat. If the document was unexpected, verify the sender and open it with Microsoft Office protections enabled; do not enable macros, external content, or editing prompts unless the source and request are trusted.
Where this verdict could be wrong3 caveats
- The absence of a sandbox run means there is no completed observation from the test run to verify how the document behaves when opened.
- The one extracted child has droppedChildren.rollup.unknown=1, so it was not independently confirmed benign.
- The missing contacted-host reputation result means no complete contacted-host reputation result is available, although the payload records no observed contacts.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 0/65 engines reported a malicious or suspicious result.
- No malicious external-intelligence match was found.
- No confirmed malicious extracted child was found.
- No rule-based rule fired.
- No completed sandbox execution was available.
- One extracted child remains unresolved.
- The document has only one recorded submission.
- No complete contacted-host reputation result is available.
6 sources checked · 5 complete · 1 not needed or not applicable. 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- 0spawned processes
- 0network contacts
- 0filesystem & mutex artifacts
Includes every process, file, registry and network entry and 1 dropped file.
Show the technical evidenceChapter 04
Technical details
None of the 65 antivirus engines that checked it flag it.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 not needed or not applicable. Complete means the check returned a usable result; it does not mean the file is safe.
File fingerprint
- File name
- Word document
- Format
- Office Open XML Document
- Size
- 2.7 MB
- Code signing
- Not applicable to this file type
- Last analyzed
- Sep 8, 2026, 6:43 PM UTC
- SHA-256
44ed480889bb8585b41cec3423aeae16b9af69566feab68cda356152482a3b56- SHA-1
2c419f8f265690e1eb90b31eec3cf5db28d8cda6- MD5
9be3ccb01b3433af1e39fca9ed22358e
First scanned Updated
Includes every engine result (74) 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 this Word document safe?
What is this Word document?
How many antivirus engines detected this Word document?
What is the SHA-256 hash of this Word document?
Is it safe to open this Word document?
How up to date is this analysis of this Word document?
Community
Member reviews and reports for this exact file hash.