Is Fee Receipt.pdf safe?
No antivirus engine flagged this PDF, and external intelligence found no matches, although its newness and absent runtime analysis warrant ordinary caution.
All 75 antivirus engines returned without a malicious or suspicious finding, including 17 tier-1 engines reporting clean. No external-intelligence match was found, but the document is newly observed and lacks sandbox or complete contacted-host evidence, so open it only if the receipt was expected.
7cd1c5f6f254a686fb…9b4f716771037dRecommended 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 17 tier-1 engines reporting clean. No external-intelligence match was found, but the document is newly observed and lacks sandbox or complete contacted-host evidence, so open it only if the receipt was expected.
Static scanning produced no malicious or suspicious detections across 75 antivirus engines. Seventeen tier-1 engines reported clean, and no engine family consensus exists. Research intelligence returned no CIRCL, MalwareBazaar, or YARAify match. However, the PDF was first observed today and has only one submission, while no completed runtime observation is available. The five similar prior results were all clean but share only the PDF file type, so they provide limited additional assurance.
What We Detected
The PDF received 0 malicious and 0 suspicious findings from 75 antivirus engines. Seventeen tier-1 engines reported clean, and no malware family or hacktool label was assigned. CIRCL, MalwareBazaar, and YARAify returned no match.
Threat Behavior
No completed sandbox observation is available, so the document's runtime behavior was not observed. The contacted-host cross-check was also not completed or saved, meaning no complete host-reputation conclusion can be made. The file is newly observed with only one recorded submission.
What To Do Now
If the receipt was expected and came through a trusted channel, it can be handled with normal precautions in an updated PDF reader. If it was unsolicited, verify the sender independently and avoid clicking embedded links or opening attachments referenced by the document.
Where this verdict could be wrong3 caveats
- The file was first observed today and has only one submission, so delayed detections or an unseen PDF exploit cannot be ruled out.
- No sandbox run completed, and contactedHosts=null means there is no complete host-reputation result.
- The five prior safe samples match only by file type, not content, signer, or a stronger binary characteristic.
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 malicious or suspicious findings
- 17 tier-1 engines reported clean
- No CIRCL, MalwareBazaar, or YARAify match
- No brand mismatch or adversarial-input flag was detected
- 5/5 file-type-only similar samples previously received safe verdicts
- First observed today with only one recorded submission
- No completed sandbox observation
- No complete contacted-host reputation result
- Receipt-themed PDFs can be used as phishing lures even when no malware is detected
Open the PDF only if the receipt is expected, using an updated reader while keeping endpoint protection enabled. Verify unexpected payment requests or embedded links through an independent channel.
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
- Fee Receipt.pdf
- Format
- Code signing
- Not applicable to this file type
- Size
- 549.5 KB
- Last analyzed
- Sep 24, 2026, 8:32 AM UTC
7cd1c5f6f254a686fb65b9e7690c23d24012238a4ede5c31ff9b4f716771037dSafety & 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 Fee Receipt.pdf safe?
What is Fee Receipt.pdf?
How many antivirus engines detected Fee Receipt.pdf?
What is the SHA-256 hash of Fee Receipt.pdf?
Is it safe to open Fee Receipt.pdf?
How up to date is this analysis of Fee Receipt.pdf?
Community
Member reviews and reports for this exact file hash.