Is oBTRJYTOL.pdf safe?
PDF triggered sandbox heuristics for process injection and LSASS access, yet zero antivirus engines flagged it.
The file produced no engine detections across 75 scanners, but sandbox evidence mapped to credential-dumping and process-injection techniques. Coverage is medium and no external-intel corroboration exists, leaving the sample in mixed-signal territory.
0a429e78ac4d4c949c…99d7d124bad137Recommended 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 file produced no engine detections across 75 scanners, but sandbox evidence mapped to credential-dumping and process-injection techniques. Coverage is medium and no external-intel corroboration exists, leaving the sample in mixed-signal territory.
Zero malicious detections from 75 reporting engines, including 17 tier-1 engines, rules out a straightforward malware verdict. However, the sandbox recorded LSASS access and process-injection activity that legitimate PDF readers do not perform. The absence of a malicious sandbox verdict and the lack of dropped malicious children or external-intel hits prevent a malicious classification. Medium prevalence and an 18-day age provide limited historical context. The combination of strong behavioural red flags against clean engine results places the file in the suspicious band.
What We Detected
61 of 75 engines returned clean results; none labelled the PDF malicious or suspicious. Sandbox execution recorded MITRE techniques T1003 (OS Credential Dumping), T1055 (Process Injection) and T1485 (Data Encrypted for Impact) plus direct LSASS memory access.
Threat Behavior
The observed process activity matches credential-stealing tooling patterns, yet the sandbox itself did not issue a malicious verdict and no malicious child files were dropped. No domains, IPs or URLs were contacted, and external intelligence sources returned no hits.
What To Do Now
Do not open the PDF on production systems. If analysis is required, run it in an isolated virtual machine with current endpoint protection enabled. Consider requesting a re-scan after additional sandbox coverage or community feedback becomes available.
Where this verdict could be wrong1 caveat
- Sandbox verdicts array is empty and hasMaliciousSandboxVerdict=false despite the MITRE mappings.
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 scanners
- No dropped malicious children
- No external intelligence hits
- Sandbox mapped activity to credential-dumping and process-injection techniques
- Single submitter, medium prevalence, 18-day history
Treat the PDF as untrusted; keep endpoint protection enabled and avoid execution outside a controlled analysis environment.
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
- 10MITRE ATT&CK techniques
- 13spawned processes
- 0network contacts
- 30filesystem & 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.
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
oBTRJYTOL.pdf
0a429e78ac4d4c949c11e31a33eb7c3c7b450d4c6b9c428be899d7d124bad137
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Program Files\Adobe\Acrobat DC\Acrobat\Acrobat.exe" "C:\Users\<USER>\Desktop\oBTRJYTOL.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
ReaderMessages
C:\Users\<USER>\AppData\LocalLow\Adobe\Acrobat\DC\ReaderMessages
04Isolated runtime analysis - Written fileObserved
SOPHIA.json
C:\Users\<USER>\AppData\Local\Adobe\Acrobat\DC\SOPHIA\Acrobat\SOPHIA.json
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\LocalLow\Adobe\Acrobat\DC\ReaderMessages
- C:\Users\<USER>\AppData\Local\Adobe\Acrobat\DC\SOPHIA\Acrobat\SOPHIA.json
- C:\Users\<USER>\AppData\Roaming\Adobe\Acrobat\DC\Security\ES_session_store
- C:\Users\<USER>\AppData\Roaming\Adobe\Acrobat\DC\Security\ES_session_storei
- C:\Users\<USER>\AppData\Local\Adobe\Acrobat\DC\SOPHIA\Acrobat\Files\TESTING
- C:\Users\<USER>\AppData\Local\Adobe\Acrobat\DC\SOPHIA\Acrobat\Files\DC_FirstMile_Home_View_Surface
- C:\Users\<USER>\AppData\LocalLow\Adobe\CRLogs\AdobeCRCommon\Logs\CC_Acrobat_23.008.20533_0.db-journal
- C:\Users\<USER>\AppData\LocalLow\Adobe\CRLogs\AdobeCRCommon\Logs\CRCommon.db-journal
- C:\Users\<USER>\AppData\Local\Adobe\Acrobat\DC\SOPHIA\Acrobat\Files\DC_Reader_Upsell_Cards
- C:\Users\<USER>\AppData\Local\Adobe\Acrobat\DC\SharedDataEvents-journal
- Global\MSILOG_508de98e1dd2d72GOL.19b11ISM_pmeT_lacoL_ataDppA_onurB_sresU_:C
- Global\AdobeCrashProcessorLocalLowLock
- \Sessions\1\BaseNamedObjects\{100184D2-BDC3-477a-B8D3-65548B67914C}_6348
- \Sessions\1\BaseNamedObjects\Local\{100184D2-BDC3-477a-B8D3-65548B67914C}_6332
- \Sessions\1\BaseNamedObjects\Local\Acrobat Instance Mutex
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
- a779a261df447a4c298c…b1b86dNever scannednever seen before
- ad27039abac3252c3b39…37ede5Never 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: oBTRJYTOL.pdf — 0a429e78ac4d4c949c11e31a33eb7c3c7b450d4c6b9c428be899d7d124bad137
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Program Files\Adobe\Acrobat DC\Acrobat\Acrobat.exe" "C:\Users\<USER>\Desktop\oBTRJYTOL.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: ReaderMessages — C:\Users\<USER>\AppData\LocalLow\Adobe\Acrobat\DC\ReaderMessages
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: SOPHIA.json — C:\Users\<USER>\AppData\Local\Adobe\Acrobat\DC\SOPHIA\Acrobat\SOPHIA.json
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
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- oBTRJYTOL.pdf
- Format
- Code signing
- Not applicable to this file type
- Size
- 411.6 KB
- Last analyzed
- Sep 3, 2026, 5:57 AM UTC
0a429e78ac4d4c949c11e31a33eb7c3c7b450d4c6b9c428be899d7d124bad137Safety & 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 oBTRJYTOL.pdf safe, or is it malware?
What is oBTRJYTOL.pdf?
How many antivirus engines detected oBTRJYTOL.pdf?
I already downloaded and opened oBTRJYTOL.pdf — what should I do?
How do I remove oBTRJYTOL.pdf?
What is the SHA-256 hash of oBTRJYTOL.pdf?
How up to date is this analysis of oBTRJYTOL.pdf?
Community
Member reviews and reports for this exact file hash.