Is (unnamed file) safe?
No antivirus engine detected this new PDF, but one sandbox mapped possible credential access, process injection, and data destruction requiring caution.
The PDF drew no detections from 75 engines, including 17 tier-1 products, and its sandbox run was labeled clean. However, that run also produced serious behavioral mappings involving LSASS, process injection, and data destruction, while network reputation coverage was incomplete, so opening it on a production system is not recommended yet.
b6d15f04c0ed7343f3…e267e67691f300Recommended 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.
The PDF drew no detections from 75 engines, including 17 tier-1 products, and its sandbox run was labeled clean. However, that run also produced serious behavioral mappings involving LSASS, process injection, and data destruction, while network reputation coverage was incomplete, so opening it on a production system is not recommended yet.
Static scanning provides substantial reassuring evidence: 0 of 75 engines flagged the PDF, including all 17 reporting tier-1 engines. One sandbox completed without a malicious verdict, and no confirmed malicious child, persistence indicator, or registry modification was found. However, the same runtime evidence mapped activity to T1003, T1055, and T1485, including possible LSASS targeting. Those mappings conflict with the mostly ordinary Adobe Acrobat process tree and may be environmental or attribution noise, but they are too serious to disregard for a newly observed file. Reputation checks covered only two hosts despite 13 contacted IPs and two URLs, so the network activity was not fully assessed.
What We Detected
The PDF was not flagged by any of 75 antivirus engines, and all 17 reporting tier-1 engines produced no detection. It is newly observed, with only one submission and no prior similar-file history available.
Threat Behavior
One completed sandbox run received a clean sandbox label, but its telemetry mapped possible credential access (T1003), process injection (T1055), and data destruction (T1485). A heuristic specifically associated activity with LSASS, although the visible process tree mainly contains Adobe Acrobat and standard Windows components. Eight written or dropped files were checked without a confirmed malicious result, but all eight remain unclassified. Only two network hosts were reputation-checked, which does not cover all 13 IP addresses and two URLs observed during execution.
What To Do Now
Do not open the document on a production endpoint until its origin is verified. If inspection is necessary, use an isolated, fully patched environment with endpoint protection enabled, and seek a fresh behavioral analysis that can attribute the reported LSASS and injection activity directly to the document.
Where this verdict could be wrong5 caveats
- All 75 antivirus engines were non-detecting, including 17 tier-1 engines.
- behaviour.hasMaliciousSandboxVerdict=false, and the only completed sandbox labeled the run clean.
- The process list is dominated by Adobe Acrobat and Windows components, so some behavioral mappings may reflect application or environment activity rather than the PDF itself.
- No persistence indicators or registry modifications were recorded.
- CIRCL returned no hit, while MalwareBazaar and YARAify coverage was unavailable.
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 detection
- 17 tier-1 engines reported no detection
- behaviour.hasMaliciousSandboxVerdict=false
- droppedChildren.hasMaliciousChild=false
- No persistence indicators or registry modifications were recorded
- Newly observed file with one recorded submission
- Possible credential access mapped to T1003
- Possible process injection mapped to T1055
- Possible data destruction mapped to T1485
- Host-reputation coverage did not include every observed network contact
- Eight dropped or written child hashes remain unclassified
Keep endpoint protection enabled and avoid opening the PDF on a production system until its source is verified. Reanalyze it in an isolated, patched sandbox with complete network and child-file coverage.
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
Partial2 of 15 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete3 signature or behavior rules matched.
External intel
PartialIndependent reference checks were attempted but are incomplete.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 16MITRE ATT&CK techniques
- 15spawned processes
- 15network contacts
- 40filesystem & 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: Contained obfuscated or packed code that makes inspection harder.
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
Scanned file
b6d15f04c0ed7343f31f3ec5cc3aa5730ee8fd7c437d527203e267e67691f300
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Program Files\Adobe\Acrobat DC\Acrobat\Acrobat.exe" "C:\Users\<USER>\Desktop\manual.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
acroNGLLog.txt
C:\Users\<USER>\AppData\Local\Temp\acroNGLLog.txt
04Isolated runtime analysis - Written fileObserved
NGL
C:\Users\<USER>\AppData\Local\Temp\NGL\
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
52.123.250.182
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
23.51.25.137
Contact observed during runtime.
07Isolated runtime analysis - +1 more recorded observation in Analyst mode
7 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.
- 52.123.250.182
- 23.51.25.137
- 135.232.92.137
- 150.171.109.154
- 23.195.81.107
- 23.2.94.216
- 4.150.223.108
- 52.123.128.14
- 199.232.210.172
- 23.11.33.159
- http://oneocsp.microsoft.com/ocsp/MFQwUjBQME4wTDAJBgUrDgMCGgUABBR0TBEVYklX7A9yLoLD9hqmCWDxFgQU3pGGSLehMVkx8UtfB6nciHnaqHYCEzMAAAALE+VmfUqbVYAAAAAAAAs=
- http://www.gstatic.com/generate_204
- C:\Users\<USER>\AppData\Local\Temp\acroNGLLog.txt
- C:\Users\<USER>\AppData\Local\Temp\NGL\
- C:\Users\<USER>\AppData\Local\Temp\TmpFEA3.tmp
- C:\Users\<USER>\AppData\Local\Temp\Tmp98.tmp
- C:\Users\<USER>\AppData\Local\Temp\A9n2wr5t_761c8w_ng.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
- C:\Program Files\Google\Chrome\Application\SetupMetrics
- C:\Users\user\AppData\Local\Google\Chrome\User Data\BrowserMetrics
- Global\_MSIExecute
- Global\MSILOG_788c5da71dd4c3eGOL.00411ISM_pmeT_lacoL_ataDppA_onurB_sresU_:C
- Global\AdobeCrashProcessorLocalLowLock
- \Sessions\1\BaseNamedObjects\{100184D2-BDC3-477a-B8D3-65548B67914C}_6980
- \Sessions\1\BaseNamedObjects\Local\{100184D2-BDC3-477a-B8D3-65548B67914C}_7048
Files this sample writes at runtime
This file drops 8 children at runtime. None are currently flagged malicious in our cache.
- eacad3e01b8b0a44ac03…df796dNever scannednever seen before
- 0f1bad70c7bd1e0a6956…780443Never scannednever seen before
- 96f7cd659d79c7d1ff8f…4e51a6Never scannednever seen before
- 12f33c6a0f4ad07d50bf…7a7255Never scannednever seen before
- 1a7754d2644fd7f26b15…181e0cNever scannednever seen before
- c257f929cff0e4380bf0…cb9572Never scannednever seen before
- 2dcbc809a98f9c22ebe9…ead6d3Never scannednever seen before
- 17b6c1db8b113ca262cf…b88bc8Never 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.
- 3rule 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: Scanned file — b6d15f04c0ed7343f31f3ec5cc3aa5730ee8fd7c437d527203e267e67691f300
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Program Files\Adobe\Acrobat DC\Acrobat\Acrobat.exe" "C:\Users\<USER>\Desktop\manual.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: acroNGLLog.txt — C:\Users\<USER>\AppData\Local\Temp\acroNGLLog.txt
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: NGL — C:\Users\<USER>\AppData\Local\Temp\NGL\
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 52.123.250.182 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 23.51.25.137 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
Available reference checks returned no match, but at least one source was unavailable. This is not a clean result.
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.exeThe sample contacted an external IP address directly and no application domain was recorded. Direct-IP traffic also occurs in legitimate installers and infrastructure, so this is supporting context only and requires corroboration from host reputation and other runtime evidence.
Evidence52.123.250.182 · 23.51.25.137 · 135.232.92.137
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
- (unnamed file)
- Format
- Code signing
- Not applicable to this file type
- Size
- 38.3 KB
- Last analyzed
- Sep 24, 2026, 9:31 AM UTC
b6d15f04c0ed7343f31f3ec5cc3aa5730ee8fd7c437d527203e267e67691f300Safety & 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 this file safe, or is it malware?
What is this file?
How many antivirus engines detected this file?
I already downloaded and opened this file — what should I do?
How do I remove this file?
What is the SHA-256 hash of this file?
How up to date is this analysis of this file?
Community
Member reviews and reports for this exact file hash.