Is ROScheatsheet.pdf safe?
No antivirus engine detected this long-observed PDF, and independent threat-intelligence checks found no known malware family or matching research rule.
All 70 antivirus engines returned no malicious or suspicious finding, including 18 high-trust engines. The document has been observed for over eleven years, and available threat-intelligence checks produced no hit; however, no completed runtime analysis or contacted-host assessment is available.
a82bcaff6deb3ecd40…193f631ddd711fRecommended 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 70 antivirus engines returned no malicious or suspicious finding, including 18 high-trust engines. The document has been observed for over eleven years, and available threat-intelligence checks produced no hit; however, no completed runtime analysis or contacted-host assessment is available.
Static scanning produced zero malicious and zero suspicious findings among 70 antivirus engines. All 18 reporting high-trust engines were non-detecting, with no family consensus or hacktool label. The PDF has an observation history exceeding eleven years and eight submissions from four sources, reducing concern that it is an unrecognized new sample. Research-rule and known-malware checks also returned no matches. Runtime behavior was not captured, and host reputation was not checked, so those areas remain unverified rather than clean.
What We Detected
None of the 70 antivirus engines flagged the PDF as malicious or suspicious. This includes 18 high-trust engines such as Microsoft, Kaspersky, BitDefender, ESET-NOD32, and Avast. No malware family, hacktool label, known-malware record, or research-rule match was reported.
Threat Behavior
No completed sandbox observation is available, so the document's behavior was not directly observed. The file carries an automatic-action tag, but that metadata alone does not establish harmful activity. No complete contacted-host reputation result is available.
What To Do Now
The available static evidence supports normal use. Open the document with an updated PDF reader and keep endpoint protection enabled, especially if its source is unfamiliar or unexpected.
Where this verdict could be wrong3 caveats
- behaviour=null, so embedded actions were not observed in a completed sandbox run.
- contactedHosts=null, so no complete reputation assessment exists for any network destinations the document might contact.
- file.tags includes "autoaction", indicating the PDF may contain an automatic document action even though no engine detected it.
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/70 engines reported a malicious or suspicious result.
- engines.tier1ReportedClean=18 and engines.tier1Malicious=0.
- file.ageDays=4188 provides a long observation history.
- externalIntel.yaraify.ruleCount=0 and externalIntel.circl.hit=false.
- externalIntel.malwareBazaar.hit=false.
- No completed runtime observation is available.
- No contacted-host reputation cross-check is available.
- The file.tags array contains "autoaction", indicating a possible automatic PDF action.
Open it only if the source and context are expected, using an updated PDF reader while keeping endpoint protection enabled. Seek a fresh sandbox analysis if the document behaves unexpectedly.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 70 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 / 70engines flagged
- 4sources 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 70 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 8 times from 4 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 70 engines flagged this file
View all 70 engine results
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- ROScheatsheet.pdf
- Format
- Code signing
- Not applicable to this file type
- Size
- 429.2 KB
- Last analyzed
- Sep 12, 2026, 12:18 AM UTC
a82bcaff6deb3ecd40bf4c3bb04a99bc28848c7fb16b49787f193f631ddd711fSafety & 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 ROScheatsheet.pdf safe?
What is ROScheatsheet.pdf?
How many antivirus engines detected ROScheatsheet.pdf?
What is the SHA-256 hash of ROScheatsheet.pdf?
Is it safe to open ROScheatsheet.pdf?
How up to date is this analysis of ROScheatsheet.pdf?
Community
Member reviews and reports for this exact file hash.