Is pdf-warhammer-fantasy-battles-1st-edition_compress.pdf safe?
No antivirus engine detected the PDF, but one sandbox mapped activity to credential access and process injection, warranting caution until independently rechecked.
All 75 antivirus engines were silent, including 16 tier-1 engines, and no sandbox issued a malicious verdict. However, the single runtime observation mapped activity to credential access and process injection, while the file is newly observed and its four written child files remain individually unresolved.
58d60dcc1ceed69bdd…b6ea50fbb87833Recommended next actions
Before opening
Do not open it until the source can be verified independently.
If you already opened it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from the original trusted source and verify its exact hash when possible.
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 were silent, including 16 tier-1 engines, and no sandbox issued a malicious verdict. However, the single runtime observation mapped activity to credential access and process injection, while the file is newly observed and its four written child files remain individually unresolved.
The static scan result is strongly reassuring: 0 of 75 engines detected the PDF, including Microsoft, Kaspersky, ESET, and BitDefender. One completed sandbox run nevertheless mapped activity to T1003 credential access, T1055 process injection, and T1485 data destruction. Those mappings are not corroborated by a malicious sandbox verdict, engine detection, external intelligence, or a malicious dropped child, and the process list is dominated by Adobe Acrobat components. Attribution is therefore uncertain and may reflect sandbox instrumentation, reader activity, or overbroad behavioral mapping rather than actions caused by the document. Confidence is limited because the file is only three days old, has one known submission, and all four written child files lack individual verdicts.
What We Detected
None of 75 antivirus engines flagged the PDF, and 16 tier-1 engines reported no detection. No named malware family, corroborated hacktool label, curated intelligence hit, or matching research rule was present.
Threat Behavior
One sandbox opened the document with Adobe Acrobat and mapped activity to T1003 credential access, T1055 process injection, and T1485 data destruction. It did not issue a malicious sandbox verdict, and the saved evidence does not conclusively attribute those actions to the PDF. Four child files were inspected without a malicious rollup, but each child still has an unknown individual verdict. No network contacts were recorded; a separate host-reputation cross-check was not available.
What To Do Now
Do not open the document on a sensitive system until it has been rescanned after engine signatures and reputation data have matured. If access is necessary, use a fully patched PDF reader with protection enabled and avoid allowing scripts, embedded files, or external content.
Where this verdict could be wrong4 caveats
- The T1003 and T1055 behavioral mappings are significant counter-signals because credential access and process injection can indicate exploitation, even though no sandbox issued a malicious verdict.
- The file has only 1 submission from 1 source and was first observed 3 days ago, so reputation history is very limited.
- contactedHosts is null, meaning no complete host-reputation cross-check is available; however, the sandbox recorded no contacted domains, IPs, or URLs.
- All four dropped children have unknown individual verdicts, so hasMaliciousChild=false does not establish that those files are benign.
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.
- 16 tier-1 engines reported no detection.
- behaviour.hasMaliciousSandboxVerdict=false.
- droppedChildren.hasMaliciousChild=false.
- YARAify, CIRCL, and MalwareBazaar returned no corroborating hits.
- Sandbox mappings include T1003 credential access and T1055 process injection.
- MalwareTips.Synth.CredentialDumper references activity involving lsass.exe.
- The PDF was first observed only 3 days ago and has one known submission.
- Four written child files have unknown individual verdicts.
- No complete contacted-host reputation cross-check is available.
Quarantine the PDF pending a fresh scan and, if possible, analysis in another isolated environment. Keep endpoint protection enabled and use a fully patched reader if the document must be opened.
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
Complete1 isolated runtime environment contributed observations.
Network
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
Complete2 signature or behavior rules matched.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 13MITRE ATT&CK techniques
- 15spawned processes
- 0network contacts
- 21filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Accessed operating-system credential data, which can expose saved passwords.
High concern: Injected code into another process, a technique that can conceal execution.
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Checked the environment for virtualisation or analysis tools.
Note: Reads your Windows user-account details.
Note: Collects details about your system.
These are observed capabilities from an isolated analysis. A technique does not prove malicious intent on its own, and the file never ran on your device.
Attack story
Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.
Input file
The submitted object
- FileObserved
pdf-warhammer-fantasy-battles-1st-edition_compress.pdf
58d60dcc1ceed69bdd2f54f53442e69a612ca3903b3459a543b6ea50fbb87833
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Program Files\Adobe\Acrobat DC\Acrobat\Acrobat.exe" "C:\Users\<USER>\Desktop\pdf-warhammer-fantasy-battles-1st-edition_compress.pdf"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Program Files\Adobe\Acrobat DC\Acrobat\Adobe Crash Processor.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
NGL
C:\Users\<USER>\AppData\Local\Temp\NGL\
04Isolated runtime analysis - Written fileObserved
acroNGLLog.txt
C:\Users\<USER>\AppData\Local\Temp\acroNGLLog.txt
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
5 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.
What this file did when executed
This file was detonated in 1 sandbox and its runtime behaviour was observed.
Adversary techniques mapped to the MITRE ATT&CK framework.
- C:\Users\<USER>\AppData\Local\Temp\NGL\
- C:\Users\<USER>\AppData\Local\Temp\acroNGLLog.txt
- C:\Users\<USER>\AppData\Local\Temp\Tmp1F4A.tmp
- C:\Users\<USER>\AppData\Local\Temp\Tmp23FF.tmp
- C:\Users\<USER>\AppData\Local\Temp\A9wpfant_111v03_3xk.tmp
- C:\Users\<USER>\AppData\Roaming\Adobe\Acrobat\DC\JSCache\GlobSettings
- Local\SessionImmersiveColorMutex
- Global\_MSIExecute
- Global\MSILOG_292c6bf71dd3db3GOL.cae21ISM_pmeT_lacoL_ataDppA_onurB_sresU_:C
- Local\SyncServiceThread
- \Sessions\1\BaseNamedObjects\{100184D2-BDC3-477a-B8D3-65548B67914C}_1588
Files this sample writes at runtime
This file drops 4 children at runtime. None are currently flagged malicious in our cache.
- eacad3e01b8b0a44ac03…df796dNever scannednever seen before
- 513fb5d3b4195ab59af2…64de2eNever scannednever seen before
- a779a261df447a4c298c…b1b86dNever scannednever seen before
- 98d0eee59b55ed5ecf17…073c4cNever scannednever seen before
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 2rule 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
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
0 of 75 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 1 time from 1 source.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: pdf-warhammer-fantasy-battles-1st-edition_compress.pdf — 58d60dcc1ceed69bdd2f54f53442e69a612ca3903b3459a543b6ea50fbb87833
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Program Files\Adobe\Acrobat DC\Acrobat\Acrobat.exe" "C:\Users\<USER>\Desktop\pdf-warhammer-fantasy-battles-1st-edition_compress.pdf"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Program Files\Adobe\Acrobat DC\Acrobat\Adobe Crash Processor.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: NGL — C:\Users\<USER>\AppData\Local\Temp\NGL\
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: acroNGLLog.txt — C:\Users\<USER>\AppData\Local\Temp\acroNGLLog.txt
ProvenanceObservedSourceIsolated runtime analysisObserved 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.
Signatures and behavior heuristics
A community signature or high-severity behavioral heuristic matched. Signatures identify known patterns; heuristics are strong leads but are not proof on their own.
The saved runtime evidence maps this activity to MITRE T1055 (Process Injection). The mapping supports possible process injection, but it does not prove the exact injection method or the operator's intent.
EvidenceC:\Windows\Explorer.EXESandbox observed process activity targeting LSASS (Windows credential store). Legitimate software has no business reading LSASS memory — this is Mimikatz-shape behaviour.
EvidenceC:\Windows\system32\lsass.exe
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
- pdf-warhammer-fantasy-battles-1st-edition_compress.pdf
- Format
- Code signing
- Not applicable to this file type
- Size
- 1.9 MB
- Last analyzed
- Sep 8, 2026, 6:50 PM UTC
58d60dcc1ceed69bdd2f54f53442e69a612ca3903b3459a543b6ea50fbb87833Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
We couldn't fully clear this file. Treat it with caution.
- Recovery step 01
Don't open it unless you're certain it came from a source you trust.
- Recovery step 02
Check where you got it — an unexpected attachment or a random download link is a red flag.
- Recovery step 03
If its origin cannot be confirmed, delete this file and use a fresh copy from a trusted source. Get a fresh copy from the original trusted source and verify its exact hash when possible.
- Recovery step 04
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is pdf-warhammer-fantasy-battles-1st-edition_compress.pdf safe, or is it malware?
What is pdf-warhammer-fantasy-battles-1st-edition_compress.pdf?
How many antivirus engines detected pdf-warhammer-fantasy-battles-1st-edition_compress.pdf?
What should I do if I already opened pdf-warhammer-fantasy-battles-1st-edition_compress.pdf?
How do I remove pdf-warhammer-fantasy-battles-1st-edition_compress.pdf?
What is the SHA-256 hash of pdf-warhammer-fantasy-battles-1st-edition_compress.pdf?
How up to date is this analysis of pdf-warhammer-fantasy-battles-1st-edition_compress.pdf?
Community
Member reviews and reports for this exact file hash.