Is MVP _game_260815_092646.pdf safe?
PDF shows sandbox evidence of LSASS access and process injection despite zero AV detections.
No antivirus engine flagged the file, yet sandbox telemetry recorded credential-dumping and process-injection activity. The sample is brand-new and rare, leaving no historical context to resolve the conflicting signals.
15a9391b541e570378…5ccdb23790694cRecommended 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.
No antivirus engine flagged the file, yet sandbox telemetry recorded credential-dumping and process-injection activity. The sample is brand-new and rare, leaving no historical context to resolve the conflicting signals.
Zero engine detections across 75 scanners would normally indicate safety, but the sandbox recorded three offensive MITRE techniques including LSASS access. The file is only hours old with a single submission, so prevalence cannot offset the behavioural red flags. Contacted-host reputation data is missing, preventing a no complete contacted-host reputation result was available static signatures and high-severity runtime behaviour places the sample in mixed-signals territory.
What We Detected
75 of 75 engines returned clean. Sandbox execution, however, captured LSASS memory reads (T1003), process injection (T1055), and data-wiping attempts (T1485). Two heuristic rules fired on this evidence.
Threat Behavior
The observed techniques match credential-stealing and defensive-evasion patterns. No malicious child files or known-bad network destinations were confirmed, but the contacted-hosts check was not completed.
What To Do Now
Do not open the PDF on production systems. Keep endpoint protection enabled and submit the sample to a controlled analysis environment for further behavioural inspection.
Where this verdict could be wrong1 caveat
- Sandbox executed the file inside Adobe Acrobat DC, suggesting the PDF may have been opened by a legitimate reader rather than a malicious loader.
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 from 75 engines including 17 tier-1 scanners
- No malicious dropped children
- Sandbox observed LSASS access and process injection
- File is brand new with no reputation history
- Contacted-host reputation data unavailable
Treat the PDF as potentially malicious until a complete host-reputation check and deeper behavioural analysis can be performed.
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
Partial1 runtime contact was observed without a completed reputation cross-check.
YARA
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
- 15spawned processes
- 1network 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: 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: Listed running processes; both legitimate software and malware may do this.
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
MVP _game_260815_092646.pdf
15a9391b541e570378b6ff49b3f6f195609a37c049551f0d675ccdb23790694c
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
C:\Windows\system32\DllHost.exe /Processid:{133EAC4F-5891-4D04-BADA-D84870380A80}
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Program Files\Adobe\Acrobat DC\Acrobat\Acrobat.exe" "C:\Users\<USER>\Desktop\MVP _game_260815_092646.pdf"
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
TmpF2CC.tmp
C:\Users\<USER>\AppData\Local\Temp\TmpF2CC.tmp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
8.8.8.8
Contact observed during runtime.
06Isolated runtime analysis
6 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.
- 8.8.8.8
- C:\Users\<USER>\AppData\Local\Temp\acroNGLLog.txt
- C:\Users\<USER>\AppData\Local\Temp\TmpF2CC.tmp
- C:\Users\<USER>\AppData\Local\Temp\TmpF5CA.tmp
- C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp
- 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:\ProgramData\Microsoft\Windows\WER\Temp\WER431A.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER578D.tmp
- Global\MSILOG_3ab1b5581dd2cc7GOL.58301ISM_pmeT_lacoL_ataDppA_onurB_sresU_:C
- Local\SessionImmersiveColorMutex
- Global\AdobeCrashProcessorLocalLowLock
- Local\WERReportingForProcess4112
- Global\d604b9fa-a20a-4457-b478-e7a27047a3a6
Files this sample writes at runtime
This file drops 10 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
- ad27039abac3252c3b39…37ede5Never scannednever seen before
- c9faf1c86c1c777a5154…9ffedaNever scannednever seen before
- 81ff65efc4487853bdb4…7c8e06Never scannednever seen before
- 1a620538802be325d6be…d4819fNever scannednever seen before
- 44fc80440f536e4877f0…f55705Never scannednever seen before
- e3b0c44298fc1c149afb…52b855Never scannednever seen before
- a5c6d4dbae668479ccb9…11631bNever 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: MVP _game_260815_092646.pdf — 15a9391b541e570378b6ff49b3f6f195609a37c049551f0d675ccdb23790694c
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — C:\Windows\system32\DllHost.exe /Processid:{133EAC4F-5891-4D04-BADA-D84870380A80}
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Program Files\Adobe\Acrobat DC\Acrobat\Acrobat.exe" "C:\Users\<USER>\Desktop\MVP _game_260815_092646.pdf"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: acroNGLLog.txt — C:\Users\<USER>\AppData\Local\Temp\acroNGLLog.txt
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: TmpF2CC.tmp — C:\Users\<USER>\AppData\Local\Temp\TmpF2CC.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 8.8.8.8 — Contact observed during runtime.
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\system32\DllHost.exe /Processid:{133EAC4F-5891-4D04-BADA-D84870380A80}Sandbox 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
- MVP _game_260815_092646.pdf
- Format
- Code signing
- Not applicable to this file type
- Size
- 1.3 MB
- Last analyzed
- Aug 15, 2026, 8:21 AM UTC
15a9391b541e570378b6ff49b3f6f195609a37c049551f0d675ccdb23790694cSafety & 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 MVP _game_260815_092646.pdf safe, or is it malware?
What is MVP _game_260815_092646.pdf?
How many antivirus engines detected MVP _game_260815_092646.pdf?
I already downloaded and opened MVP _game_260815_092646.pdf — what should I do?
How do I remove MVP _game_260815_092646.pdf?
What is the SHA-256 hash of MVP _game_260815_092646.pdf?
How up to date is this analysis of MVP _game_260815_092646.pdf?
Community
Member reviews and reports for this exact file hash.