Is File Closure Letter.pdf safe?
No antivirus engine detected a threat in this PDF, although its very recent appearance and lack of runtime analysis warrant ordinary attachment caution.
All 75 antivirus engines returned no malicious or suspicious detection, including 16 tier-1 engines, and no external intelligence source matched the document. Confidence is moderated because the PDF is newly observed, has only two submissions, and was not executed in a completed sandbox.
9c3b953f55fccabf19…061fb7d8b812feRecommended 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 75 antivirus engines returned no malicious or suspicious detection, including 16 tier-1 engines, and no external intelligence source matched the document. Confidence is moderated because the PDF is newly observed, has only two submissions, and was not executed in a completed sandbox.
The strongest evidence is broad static agreement: 0 of 75 engines flagged the PDF, with Microsoft, Kaspersky, BitDefender, ESET-NOD32, and other tier-1 products reporting no detection. Research intelligence also produced no YARAify, MalwareBazaar, or CIRCL match. No heuristic rule fired, and there is no brand mismatch or contaminated input field. However, the file is newly observed and has only two submissions, so reputation history remains limited. No completed runtime observation or complete contacted-host reputation result is available, preventing conclusions about execution-time behavior.
What We Detected
None of 75 antivirus engines identified the PDF as malicious or suspicious. Sixteen tier-1 engines reported no detection, including Microsoft, Kaspersky, BitDefender, ESET-NOD32, and Avast. YARAify returned zero matching rules, while MalwareBazaar and CIRCL returned no record.
Threat Behavior
No completed sandbox observation is available, so the document's execution-time behavior was not observed. A complete contacted-host reputation check is also unavailable. The PDF is newly observed and has only two recorded submissions, which limits reputation-based assurance.
What To Do Now
Open the attachment only if it was expected and the sender can be verified through a trusted channel. Keep endpoint protection and the PDF reader enabled and fully updated, especially because runtime evidence is unavailable.
Where this verdict could be wrong3 caveats
- prevalence.classification=rare_new means the file was first observed recently and has only two recorded submissions.
- behaviour=null leaves embedded actions, exploit attempts, and other runtime behavior unobserved.
- contactedHosts=null means no complete reputation cross-check of possible network contacts is available.
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 of 75 engines reported a malicious or suspicious detection
- 16 tier-1 engines reported no detection
- No YARAify, MalwareBazaar, or CIRCL match
- No triggered heuristics
- No brand mismatch or adversarial-input flag
- Newly observed file with only two recorded submissions
- No completed sandbox observation
- No complete contacted-host reputation result
- No similar-hash history available
The scan evidence supports opening only when the attachment is expected and its sender is verified. Keep endpoint protection active and use an updated PDF reader.
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
- 2sources 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 75 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 2 times from 2 sources.
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
- File Closure Letter.pdf
- Format
- Code signing
- Not applicable to this file type
- Size
- 236.0 KB
- Last analyzed
- Sep 11, 2026, 12:59 PM UTC
9c3b953f55fccabf193e53b99ffbfcbd23f60968abd8f3aabb061fb7d8b812feSafety & 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 File Closure Letter.pdf safe?
What is File Closure Letter.pdf?
How many antivirus engines detected File Closure Letter.pdf?
What is the SHA-256 hash of File Closure Letter.pdf?
Is it safe to open File Closure Letter.pdf?
How up to date is this analysis of File Closure Letter.pdf?
Community
Member reviews and reports for this exact file hash.