Is Request for Trade Reference.pdf safe?
No engine detected this PDF, including 17 tier-1 products, although its recent appearance and lack of runtime analysis warrant ordinary document precautions.
All 75 antivirus engines returned no malicious or suspicious detection, including 17 tier-1 products. No external intelligence source corroborated a threat, but the PDF is newly observed and has no completed runtime analysis, so open it with an updated, protected PDF reader.
f85f2ade62ef17d99f…70d0e051c888cfRecommended 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 17 tier-1 products. No external intelligence source corroborated a threat, but the PDF is newly observed and has no completed runtime analysis, so open it with an updated, protected PDF reader.
The strongest evidence is the complete absence of malicious or suspicious detections across 75 engines. Seventeen tier-1 products, including Microsoft, Kaspersky, BitDefender, ESET-NOD32, and Avast, reported no detection. MalwareBazaar, CIRCL, and YARAify supplied no corroborating threat intelligence. The five historical comparisons were also assessed as clean, although they match only by PDF file type and therefore carry limited weight. Confidence is moderated because this document has been submitted only once, no sandbox execution completed, and no host-reputation cross-check is available.
What We Detected
None of 75 antivirus engines flagged the PDF as malicious or suspicious. Seventeen tier-1 engines reported no detection, and MalwareBazaar, CIRCL, and YARAify supplied no matching threat intelligence.
Threat Behavior
No completed runtime observation is available, so the document's behavior after opening was not observed. The host-reputation cross-check was also unavailable, meaning any embedded links or remote resources were not comprehensively assessed here.
What To Do Now
Open the document only if its business context and sender are expected. Keep endpoint protection enabled, use an updated PDF reader, and avoid enabling embedded content or following unexpected links.
Where this verdict could be wrong3 caveats
- prevalence.classification=rare_new means the file has little established reputation despite the absence of detections.
- behaviour=null, so embedded actions, scripts, links, or exploit behavior were not observed in a completed sandbox run.
- contactedHosts=null, so no complete host-reputation result 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/75 engines reported a malicious or suspicious result
- 17 tier-1 engines reported no detection
- No MalwareBazaar, CIRCL, or YARAify hit
- No brand mismatch detected
- Five file-type comparisons previously received safe verdicts
- Newly observed file with only one recorded submission
- No completed sandbox execution
- No complete contacted-host reputation result
- Business-themed PDF could still be used for phishing or social engineering
Open it only when the sender and trade-reference request are expected, using an updated PDF reader with endpoint protection enabled. Treat unexpected links, forms, or credential requests cautiously.
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
- Request for Trade Reference.pdf
- Format
- Code signing
- Not applicable to this file type
- Size
- 235.0 KB
- Last analyzed
- Sep 24, 2026, 4:18 PM UTC
f85f2ade62ef17d99ff71b00240a176a104e34fe96bc3842e370d0e051c888cfSafety & 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 Request for Trade Reference.pdf safe?
What is Request for Trade Reference.pdf?
How many antivirus engines detected Request for Trade Reference.pdf?
What is the SHA-256 hash of Request for Trade Reference.pdf?
Is it safe to open Request for Trade Reference.pdf?
How up to date is this analysis of Request for Trade Reference.pdf?
Community
Member reviews and reports for this exact file hash.