Is 73e4fd.pdf safe?
No antivirus engine detected the PDF, and independent intelligence produced no hits, although its recent appearance and absent runtime analysis limit certainty.
All 75 antivirus engines returned without a malicious or suspicious finding, including 16 tier-1 engines reporting no detection. No external intelligence matched the PDF, but it is newly observed and was not executed in a completed sandbox, so normal caution remains appropriate.
818e5d373c6729438a…8cb8e619b09ebcRecommended 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 without a malicious or suspicious finding, including 16 tier-1 engines reporting no detection. No external intelligence matched the PDF, but it is newly observed and was not executed in a completed sandbox, so normal caution remains appropriate.
The strongest evidence is the complete absence of detections across 75 antivirus engines, with no tier-1 engine flagging the document. MalwareBazaar, CIRCL, and YARAify supplied no corroborating threat match. The five historical comparisons were also assessed as benign, although they match only by PDF file type and therefore carry little sample-specific weight. The document has just one recorded source and submission, so reputation history is minimal. No completed runtime observation or comprehensive contacted-host assessment is available, preventing conclusions about behavior after opening.
What We Detected
None of 75 antivirus engines marked the PDF as malicious or suspicious. Sixteen tier-1 engines reported no detection, including Avast, BitDefender, ESET-NOD32, Kaspersky, and Microsoft. MalwareBazaar, CIRCL, and YARAify also returned no matching threat intelligence.
Threat Behavior
No completed sandbox observation is available, so the document's behavior after opening was not observed. A complete reputation assessment of any potential network contacts is also unavailable. The file is newly observed, with one recorded source and one submission, which limits reputation-based assurance.
What To Do Now
Open the document only if its source and expected contents are familiar. Keep the PDF reader and endpoint protection enabled and fully updated, and avoid interacting with unexpected links or attachments inside the document.
Where this verdict could be wrong3 caveats
- prevalence.classification=rare_new: the PDF is newly observed and has only one recorded submission.
- behaviour=null and contactedHosts=null: no runtime execution or complete host-reputation assessment is available.
- The 5/5 prior safe similarHashes entries use matchKind=filetype only, which provides limited sample-specific assurance.
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/75 antivirus engines reported a malicious or suspicious result
- engines.tier1Malicious=0 and 16 tier-1 engines reported no detection
- externalIntel.malwareBazaar.hit=false
- externalIntel.circl.hit=false
- externalIntel.yaraify.ruleCount=0
- Newly observed file with one recorded source and one submission
- No completed sandbox execution
- No complete contacted-host reputation result
- Generic hexadecimal-style filename provides little context
The scan findings support ordinary handling if the sender and purpose are expected. Keep protection enabled, use an updated PDF reader, and avoid embedded links or attachments that were not anticipated.
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
- 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 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 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 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
- 73e4fd.pdf
- Format
- Code signing
- Not applicable to this file type
- Size
- 4.8 MB
- Last analyzed
- Sep 11, 2026, 4:39 AM UTC
818e5d373c6729438a640d8da3b7cf5c7302cdacc3523b9a998cb8e619b09ebcSafety & 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 73e4fd.pdf safe?
What is 73e4fd.pdf?
How many antivirus engines detected 73e4fd.pdf?
What is the SHA-256 hash of 73e4fd.pdf?
Is it safe to open 73e4fd.pdf?
How up to date is this analysis of 73e4fd.pdf?
Community
Member reviews and reports for this exact file hash.