Is Document_2026-07-22.pdf safe?
Zero detections across 74 engines on a newly submitted PDF with no behavioural or external-intel red flags.
All 74 engines returned clean results and no tier-1 or low-trust malicious labels were recorded. Similar PDF files in our history were also rated safe. The file is rare and new, but nothing in the evidence indicates malice.
9b9133d3382d0f2a7d…194a2653fe5e1bRecommended next actions
Before opening
Open it only when its sender or download source is one you independently trust.
If you already opened it
Keep normal device protection enabled and stop if the file behaves unexpectedly.
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 74 engines returned clean results and no tier-1 or low-trust malicious labels were recorded. Similar PDF files in our history were also rated safe. The file is rare and new, but nothing in the evidence indicates malice.
With zero malicious detections from any engine tier and no corroborating signals from YARAify, CIRCL, or sandbox behaviour, the file presents no observable threat indicators. The similar-hash RAG set shows a majority of prior PDF verdicts rated safe under the same low-signal conditions. While the file is rare_new, the complete absence of detections and external-intel hits outweighs the lack of established prevalence.
What We Detected
74 engines scanned the PDF; none flagged malicious content. No YARA rules matched, no sandbox execution data exists, and the file contacted no network hosts.
Threat Behavior
No MITRE techniques, dropped children, or malicious domains were observed. The filename follows a generic document pattern with no security-software or research-tool masquerading.
What To Do Now
Open the PDF with a current reader in a sandboxed environment if additional caution is desired. Re-scan after 24-48 hours to confirm the clean status as more engines gain coverage.
Where this verdict could be wrong2 caveats
- If the PDF contains an embedded exploit that no engine currently detects, the zero-detection count would be misleading — but absence of YARAify rules and sandbox data reduces that likelihood.
- rare_new classification means the file has not yet built a reputation, so future detections remain possible.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Zero engine detections across all tiers
- No external intelligence hits
- Majority of similar PDF files previously rated safe
The file can be considered safe for normal use; continue monitoring for any future engine updates.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 74 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 / 74engines 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
0 of 74 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
No completed runtime observation is available for this file.
ProvenanceDerivedSourceRuntime coverageObserved 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 74 engines flagged this file
View all 74 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
- Document_2026-07-22.pdf
- Format
- Code signing
- Not applicable to this file type
- Size
- 1.7 MB
- Last analyzed
- Jul 23, 2026, 12:28 PM UTC
9b9133d3382d0f2a7da6c2ca8568c089841e068f8287e2c107194a2653fe5e1bSafety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file appears low risk based on the evidence available now.
- Recovery step 01
Open it only when its sender or download source is one you independently trust.
- Recovery step 02
A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.
- Recovery step 03
Keep your antivirus and Windows updates switched on so you stay protected.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is Document_2026-07-22.pdf safe?
What is Document_2026-07-22.pdf?
How many antivirus engines detected Document_2026-07-22.pdf?
What is the SHA-256 hash of Document_2026-07-22.pdf?
Is it safe to open Document_2026-07-22.pdf?
How up to date is this analysis of Document_2026-07-22.pdf?
Community
Member reviews and reports for this exact file hash.