Is feeReciept.pdf safe?
No antivirus engine detected a threat in this PDF, although its automatic-action tag and lack of runtime analysis justify routine document-opening precautions.
All 74 antivirus engines returned without a malicious or suspicious finding, including 17 tier-1 engines. No external threat-intelligence source identified the hash, but the PDF is newly observed, carries an automatic-action tag, and has not undergone completed runtime analysis.
da68914272bca3f330…eb35f9da017427Recommended 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 antivirus engines returned without a malicious or suspicious finding, including 17 tier-1 engines. No external threat-intelligence source identified the hash, but the PDF is newly observed, carries an automatic-action tag, and has not undergone completed runtime analysis.
The strongest evidence is unanimous static scanner silence: 0 of 74 engines flagged the file, including Microsoft, Kaspersky, BitDefender, ESET, and Avast. External intelligence produced no MalwareBazaar, CIRCL, or YARA rule match. Five prior PDF examples also received clean assessments, although file-type-only similarity provides limited sample-specific support. The document is newly observed and tagged for an automatic action, so those details modestly limit confidence. No sandbox result or complete contacted-host reputation check is available, preventing conclusions about runtime behavior or network activity.
What We Detected
None of the 74 antivirus engines reported a malicious or suspicious result. This includes 17 tier-1 engines, while MalwareBazaar, CIRCL, and YARA-based intelligence returned no match.
Threat Behavior
No completed sandbox observation is available, so the document's runtime behavior was not observed. The PDF carries an autoaction tag, which can indicate an action configured to run when the document is opened; this feature is not malicious by itself. No complete host-reputation result is available because contacted-host checking was not saved.
What To Do Now
Open the document only if its source and expected purpose are known. Keep PDF reader and endpoint protection enabled, and avoid approving unexpected prompts, external links, attachments, or scripted actions.
Where this verdict could be wrong4 caveats
- file.tags includes 'autoaction', indicating the PDF may contain an automatic action that warrants care despite the absence of detections.
- behaviour=null, so no completed sandbox run confirms what the document does when opened.
- contactedHosts=null, so no complete host-reputation result is available.
- prevalence.classification=rare_new reflects only one source and one submission.
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/74 antivirus engines reported a malicious or suspicious result.
- All 17 tier-1 engines that reported results found no detection.
- MalwareBazaar, CIRCL, and YARA-based intelligence produced no hits.
- No malicious dropped child was reported.
- Five file-type peers have prior safe assessments.
- The PDF is newly observed, with only one source and one submission.
- The file carries an automatic-action tag.
- No completed sandbox observation is available.
- No complete contacted-host reputation result is available.
The file may be opened with normal caution if it came from an expected source. Keep protection enabled and use an updated PDF reader, especially because the document has an automatic-action tag.
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
- feeReciept.pdf
- Format
- Code signing
- Not applicable to this file type
- Size
- 92.2 KB
- Last analyzed
- Sep 19, 2026, 3:39 PM UTC
da68914272bca3f33048290a0deb14e0ee720d7d2a86319c05eb35f9da017427Safety & 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 feeReciept.pdf safe?
What is feeReciept.pdf?
How many antivirus engines detected feeReciept.pdf?
What is the SHA-256 hash of feeReciept.pdf?
Is it safe to open feeReciept.pdf?
How up to date is this analysis of feeReciept.pdf?
Community
Member reviews and reports for this exact file hash.