Is Document-b37c6769-f919-49b2-8f64-02607c1232a5.pdf safe?
Zero engine detections but sandbox shows credential-dumping and process-injection activity in a brand-new PDF.
All 75 engines returned clean, yet the sandbox recorded LSASS access and process injection. The file is rare and newly submitted, so the conflicting signals place it in the suspicious category.
b1546972048677a143…606d1a8343dbcbRecommended 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 engines returned clean, yet the sandbox recorded LSASS access and process injection. The file is rare and newly submitted, so the conflicting signals place it in the suspicious category.
The complete absence of engine detections is a strong benign indicator, but the sandbox captured three offensive MITRE techniques including credential dumping and process injection. No external intelligence or dropped malicious children corroborate malice, yet the file is only hours old and has almost no history. The combination of clean engine consensus and high-severity runtime behaviour produces mixed signals that cannot be resolved without further evidence.
What We Detected
75 antivirus engines scanned the PDF and none flagged it malicious. Sandbox execution, however, recorded LSASS memory access (T1003) and process injection (T1055) plus data-wiping activity (T1485). Three temporary files were dropped; none matched known malware.
Threat Behavior
The observed techniques match credential-stealing and defensive-evasion patterns, yet no C2 traffic, persistence mechanisms or malicious children were found. The file’s extreme rarity (first seen today) prevents any historical context.
What To Do Now
Do not open the PDF on production systems. If analysis is required, run it in an isolated VM with current endpoint protection enabled and monitor for LSASS access or unexpected outbound connections.
Where this verdict could be wrong1 caveat
- All 75 engines returned clean detections; tier-1 engines (Avast, AVG, Avira, BitDefender, DrWeb, Emsisoft, ESET-NOD32, F-Secure, Fortinet, GData, Ikarus, Kaspersky, Microsoft) unanimously silent.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Zero detections across 75 engines including 17 tier-1 engines
- No malicious dropped children
- No external intelligence hits
- Sandbox observed LSASS access and process injection
- File is less than one day old with minimal prevalence
Treat the document as untrusted; keep endpoint protection enabled and avoid execution until additional sandbox or dynamic-analysis results are available.
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
- 12MITRE ATT&CK techniques
- 13spawned processes
- 0network contacts
- 24filesystem & 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
Document-b37c6769-f919-49b2-8f64-02607c1232a5.pdf
b1546972048677a1432d784940140bd38bd56ccc1d95ff4c7c606d1a8343dbcb
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Program Files\Adobe\Acrobat DC\Acrobat\Acrobat.exe" "C:\Users\<USER>\Desktop\attachment.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\Tmp6F0.tmp
- C:\Users\<USER>\AppData\Local\Temp\Tmp858.tmp
- C:\Users\<USER>\AppData\Local\Temp\A9zjbgse_1ehohlk_1n0.tmp
- C:\Users\<USER>\AppData\Roaming\Adobe\Acrobat\DC\JSCache\GlobSettings
- C:\Users\<USER>\AppData\Local\Packages\Microsoft.XboxGamingOverlay_8wekyb3d8bbwe\LocalCache\KnownGameList.bin
- C:\Users\<USER>\AppData\Local\Microsoft\GameDVR\KnownGameList.update
- Global\_MSIExecute
- Global\MSILOG_60308c5a1dd34e0GOL.04911ISM_pmeT_lacoL_ataDppA_onurB_sresU_:C
- Global\AdobeCrashProcessorLocalLowLock
- \Sessions\1\BaseNamedObjects\{100184D2-BDC3-477a-B8D3-65548B67914C}_6812
- \Sessions\1\BaseNamedObjects\Local\{100184D2-BDC3-477a-B8D3-65548B67914C}_6956
Files this sample writes at runtime
This file drops 3 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
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
- 2sources 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 4 times from 2 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: Document-b37c6769-f919-49b2-8f64-02607c1232a5.pdf — b1546972048677a1432d784940140bd38bd56ccc1d95ff4c7c606d1a8343dbcb
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Program Files\Adobe\Acrobat DC\Acrobat\Acrobat.exe" "C:\Users\<USER>\Desktop\attachment.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
- Document-b37c6769-f919-49b2-8f64-02607c1232a5.pdf
- Format
- Code signing
- Not applicable to this file type
- Size
- 150.0 KB
- Last analyzed
- Aug 25, 2026, 6:17 PM UTC
b1546972048677a1432d784940140bd38bd56ccc1d95ff4c7c606d1a8343dbcbSafety & 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 Document-b37c6769-f919-49b2-8f64-02607c1232a5.pdf safe, or is it malware?
What is Document-b37c6769-f919-49b2-8f64-02607c1232a5.pdf?
How many antivirus engines detected Document-b37c6769-f919-49b2-8f64-02607c1232a5.pdf?
What should I do if I already opened Document-b37c6769-f919-49b2-8f64-02607c1232a5.pdf?
How do I remove Document-b37c6769-f919-49b2-8f64-02607c1232a5.pdf?
What is the SHA-256 hash of Document-b37c6769-f919-49b2-8f64-02607c1232a5.pdf?
How up to date is this analysis of Document-b37c6769-f919-49b2-8f64-02607c1232a5.pdf?
Community
Member reviews and reports for this exact file hash.