Is Ad.pdf safe?
No antivirus engine detected the new PDF, but one sandbox produced uncorroborated mappings for credential access, process injection, and file deletion.
All 75 antivirus engines returned without a detection, including 17 tier-1 engines, and the completed sandbox issued a clean result. However, that run also generated possible T1003, T1055, and T1485 mappings, so the newly observed PDF warrants caution until those conflicting signals are independently reproduced.
1fb0b9e98397d91099…00e2bdea14f2b2Recommended 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 returned without a detection, including 17 tier-1 engines, and the completed sandbox issued a clean result. However, that run also generated possible T1003, T1055, and T1485 mappings, so the newly observed PDF warrants caution until those conflicting signals are independently reproduced.
The strongest reassuring evidence is that 0 of 75 engines flagged the PDF, including no detections from 17 tier-1 engines. One completed sandbox also produced a clean verdict, no contacted hosts, no persistence indicators, and no dropped-file hashes. Against that, its telemetry was mapped to credential access, process injection, and file deletion techniques, including a heuristic reference to LSASS. Those mappings are not independently corroborated by engine labels, malicious children, network activity, YARA rules, or external intelligence, and the process evidence does not establish attribution to the document. Because the file is newly observed with only one submission, the conflict cannot yet be resolved with high confidence.
What We Detected
None of 75 antivirus engines flagged the PDF, including 17 tier-1 engines. External intelligence returned no MalwareBazaar, CIRCL, or YARAify match, and no related prior-file decisions or user reports were available.
Threat Behavior
One completed sandbox issued a clean result and recorded no network contacts, persistence indicators, or dropped-file hashes. However, its telemetry was mapped to T1003, T1055, and T1485, and a synthesized heuristic referenced possible LSASS access. These signals could indicate credential access and process injection, but the saved evidence does not prove that the PDF initiated them; Adobe Acrobat and supporting processes were also active during the run. No complete contacted-host reputation result was saved, though the run listed no contacted domains, IPs, or URLs.
What To Do Now
Keep endpoint protection enabled and avoid opening the document on a sensitive system until its source is verified. If the file is expected, confirm it through a trusted out-of-band channel and consider opening it only in a fully patched, isolated document environment.
Where this verdict could be wrong3 caveats
- The clean 0/75 engine result weighs against malware, although the file was first observed today and may not yet have mature reputation.
- The single completed sandbox recorded a clean verdict and no dropped hashes, while synthesized technique mappings still suggest possible LSASS access and process injection.
- contactedHosts=null, so no completed host-reputation cross-check is available; however, the sandbox recorded no contacted domains, IPs, or URLs.
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 detected the file
- 17 tier-1 engines reported no detection
- The completed sandbox issued a clean verdict
- No dropped-file hashes or persistence indicators were recorded
- No YARAify, MalwareBazaar, or CIRCL hit was found
- Newly observed file with only one recorded submission
- Sandbox mapping to T1003 credential access
- Sandbox mapping to T1055 process injection
- Sandbox mapping to T1485 data destruction
- Synthesized heuristic referenced possible LSASS access
- No complete contacted-host reputation cross-check was saved
Do not open the PDF on a sensitive device until its sender and purpose are verified. Keep security software enabled, use a fully patched PDF reader, and isolate the document if further inspection is necessary.
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
- 15MITRE 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: 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
Ad.pdf
1fb0b9e98397d91099c1b50cd6aa65b8fefdd54b1413ff44e000e2bdea14f2b2
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Program Files\Adobe\Acrobat DC\Acrobat\Acrobat.exe" "C:\Users\<USER>\Desktop\Ad.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
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.
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\SessionInfo\1\ApplicationViewManagement\W32:000000000003009C\VirtualDesktop
- C:\Users\<USER>\AppData\Local\Temp\acroNGLLog.txt
- C:\Users\<USER>\AppData\Local\Temp\NGL\
- C:\Users\<USER>\AppData\Local\Temp\Tmp625.tmp
- C:\Users\<USER>\AppData\Local\Temp\Tmp76E.tmp
- C:\Users\<USER>\AppData\Local\Temp\A9ehokt7_3i7j5q_4ps.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_7c5d63bf1dd50dfGOL.71811ISM_pmeT_lacoL_ataDppA_onurB_sresU_:C
- Global\AdobeCrashProcessorLocalLowLock
- \Sessions\1\BaseNamedObjects\{100184D2-BDC3-477a-B8D3-65548B67914C}_6724
- \Sessions\1\BaseNamedObjects\Local\{100184D2-BDC3-477a-B8D3-65548B67914C}_6800
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: Ad.pdf — 1fb0b9e98397d91099c1b50cd6aa65b8fefdd54b1413ff44e000e2bdea14f2b2
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Program Files\Adobe\Acrobat DC\Acrobat\Acrobat.exe" "C:\Users\<USER>\Desktop\Ad.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
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
- Ad.pdf
- Format
- Code signing
- Not applicable to this file type
- Size
- 728.0 KB
- Last analyzed
- Sep 30, 2026, 8:39 AM UTC
1fb0b9e98397d91099c1b50cd6aa65b8fefdd54b1413ff44e000e2bdea14f2b2Safety & 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 Ad.pdf safe, or is it malware?
What is Ad.pdf?
How many antivirus engines detected Ad.pdf?
What should I do if I already opened Ad.pdf?
How do I remove Ad.pdf?
What is the SHA-256 hash of Ad.pdf?
How up to date is this analysis of Ad.pdf?
Community
Member reviews and reports for this exact file hash.