File scan report
Verdict Safe
Is this PDF document safe? Yes, no threats found.
No antivirus engine flagged this PDF, and its completed Acrobat sandbox run produced no corroborated malicious process, file it created, or network evidence.
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.
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 63 flagged
- Flagged 0
- No detection 63
- No result 12
- Code signing Not applicable
- Test run Completed
- First seen 16d 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 63 antivirus engines that checked it flagged the PDF, including the major antivirus engines, and the completed sandbox run returned clean.
The static scan produced no detection from any of the 75 engines, with all 17 major participants silent. One completed observation from the test run opened the document in Adobe Acrobat and did not produce a malicious sandbox assessment. Automated mappings included T1003, T1055, and T1485, but no injected process, persistence indicator, malicious child, or concrete credential-access action was recorded. All three observed sample domains received complete cache coverage without a malicious or suspicious match, while the public DNS contact was identified as sandbox background traffic. The file is and its ten generated files lack saved individual verdicts, so ordinary caution remains appropriate despite the strongly benign evidence.
What We Detected
None of the 63 antivirus engines that checked it flagged the PDF, including the 17 major antivirus engines that returned results. Malware-specific research rules and the external malware repository also produced no match.
Threat Behavior
The completed sandbox run opened the document with Adobe Acrobat and returned clean. Automated analysis mapped T1003, T1055, and T1485, but it recorded no injected target process, persistence mechanism, malicious child, or concrete credential-access event. Reputation checks covered all three observed sample domains and found no malicious or suspicious cache entries; the 8.8.8.8 contact was identified as analysis-environment background traffic.
What To Do Now
The evidence supports opening the document in a fully updated PDF reader with normal security software enabled. Because the hash is and ten generated files lack saved individual verdicts, avoid enabling embedded content or following unexpected links if the document behaves unusually.
Where this verdict could be wrong3 caveats
- The file is from only one submitter, so its wider reputation is not yet established.
- Sandbox mappings included T1003, T1055, and T1485; these are concerning labels, although the recorded process and injection details do not substantiate those actions.
- Ten generated files have no saved individual verdicts, leaving their identities unresolved even though none is currently identified as a malicious child.
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 63 antivirus engines that checked it flagged the PDF.
- All 17 major antivirus engines that returned results reported no detection.
- The completed sandbox run returned clean and showed the document opening in Adobe Acrobat.
- No injected process, persistence mechanism, or identified malicious child was recorded.
- Complete reputation coverage for the three observed sample domains found no malicious or suspicious matches.
- The exact hash is and has only one known submission.
- Automated sandbox mapping referenced credential dumping, process injection, and file deletion, though the underlying records did not confirm those actions.
- Ten generated files do not yet have saved individual verdicts.
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- 14sandbox rule tags
- 7spawned processes
- 3network contacts
- 35filesystem & mutex artifacts
Includes the sandbox verdicts, 14 mapped techniques, every process, file, registry and network entry and 5 dropped files.
Show the technical evidenceChapter 04
Technical details
None of the 63 antivirus engines that checked it flag it.
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
- File name
- PDF document
- Format
- Size
- 21.7 MB
- Code signing
- Not applicable to this file type
- Last analyzed
- Oct 10, 2026, 4:41 AM UTC
- SHA-256
7ac3b78f77fe5cc83878ffdd49fd4544ff591da74868537139ad2cc1d9e22126- SHA-1
8e2a3fe262b589fd593407b8f4b3e375c83166fd- MD5
8f83bfd007cbddb3320b4c424e1ee4d1
First scanned
Includes every engine result (75), 2 matched signature rules 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 PDF document safe?
What is this PDF document?
How many antivirus engines detected this PDF document?
What is the SHA-256 hash of this PDF document?
Is it safe to open this PDF document?
How up to date is this analysis of this PDF document?
Community
Member reviews and reports for this exact file hash.