File scan report
Verdict Safe
Is this PDF document safe? Yes, no threats found.
None of the 63 antivirus engines that checked it flagged this encrypted PDF, and its completed sandbox run returned clean despite several unsupported behavioral technique mappings.
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.
Antivirus results
0 of 63 flagged
- Flagged 0
- No detection 63
- No result 12
- Code signing Not applicable
- Test run Completed
- First seen 12d ago
Chapter 02
Why we think so
5 points against it and 3 in its favour, checked against the scan evidence.
The reasoning behind this verdict
The T1003, T1055, and mappings warrant caution, but they lack target details, process-injection evidence, persistence, or other corroboration.
The strongest evidence is the absence of detections across 75 engines, including no major alerts. One completed sandbox run returned clean and recorded no injected process or persistence indicator. Although the runtime report mapped T1003, T1055, and T1485, those abstract mappings do not identify a target or demonstrate that the PDF performed those actions. No malware-specific YARA rule or malware-repository match corroborates the mappings. Confidence is moderated because the encrypted document is three dropped files lack saved verdicts, and no complete contacted-host reputation result is available.
What We Detected
None of the 63 antivirus engines that checked it flagged the PDF, including 17 major antivirus engines that reported no detection. No malware-specific YARA rule, named threat family, or malware-repository match was present.
Threat Behavior
The completed sandbox run returned clean and showed the document opening through Adobe Acrobat. It mapped T1003, T1055, and T1485, but did not identify a credential target, injected process, destructive action, or persistence mechanism. Those unsupported mappings are insufficient to establish hostile behavior. Three dropped files have no saved verdict, and no complete contacted-host reputation result is available.
What To Do Now
The document can be handled with ordinary caution. Keep the PDF reader and security software enabled and updated; if the file came from an unexpected sender or requests credentials, scripts, or external content, verify the source before interacting further.
Where this verdict could be wrong4 caveats
- The PDF is encrypted and only one day old, so static inspection and reputation history are limited.
- The sandbox mapped credential dumping, process injection, and data destruction techniques, although it supplied no target details and returned a clean verdict.
- Three dropped files have no saved verdict, leaving their nature unresolved rather than establishing them as harmful.
- No complete contacted-host reputation result is available, although the completed run recorded no sample 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.
- None of the 63 antivirus engines that checked it flagged the file.
- The completed sandbox run returned clean and recorded no injected process or persistence indicator.
- No malware-specific researcher rules or malware-repository matches were found.
- The PDF is encrypted, which can limit static inspection.
- It was first observed on Oct 13, 2026 and has a single known submission.
- The sandbox mapped credential dumping, process injection, and data destruction techniques without enough detail to validate them.
- Three generated files have no saved classifications.
- No complete reputation check is available for contacted hosts.
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- 17sandbox rule tags
- 7spawned processes
- 0network contacts
- 22filesystem & mutex artifacts
Includes the sandbox verdicts, 17 mapped techniques, every process, file, registry and network entry and 1 dropped file.
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 · 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
- PDF document
- Format
- Size
- 133.1 kB
- Code signing
- Not applicable to this file type
- Last analyzed
- Oct 14, 2026, 11:33 AM UTC
- SHA-256
da862fe8c7d81a7b47675731ae1328af4942304a74f51d6b7606037f9fb90013- SHA-1
45b5af1bcfa7920fc014d3448562391523011f29- MD5
907f2899f24c66ba99fd567d80c0b2b4
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.