Is OLVM_ca9110ad70744670bdda21ffaf6c4009.-RFP.pdf safe?
Single low-trust engine flags PDF while sandbox shows credential-dumping and process-injection techniques.
One low-trust engine labels the PDF as phishing-related, yet 74 engines stay silent. Sandbox logs LSASS access and process injection, but no tier-1 consensus or malicious child files exist.
66249124493210f73c…23b11cea6e656eRecommended 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.
One low-trust engine labels the PDF as phishing-related, yet 74 engines stay silent. Sandbox logs LSASS access and process injection, but no tier-1 consensus or malicious child files exist.
The file is a newly submitted PDF that triggered three synthetic heuristics mapping to credential dumping, process injection and direct-IP traffic. Only McAfeeD flagged it, and that engine sits in the low-trust tier. No tier-1 engine agreed, no external-intel sources returned hits, and the sandbox did not issue a malicious verdict. The combination of rare prevalence, offensive MITRE techniques and absent corroboration leaves the sample in mixed-signal territory.
What We Detected
One low-trust engine (McAfeeD) reported Trojan:PDF/Phishing.RLW. Sandbox execution recorded LSASS access (T1003), process injection (T1055) and data destruction (T1485) alongside direct-IP contact to 162.159.36.2.
Threat Behavior
The observed techniques align with credential-theft and injection patterns, yet the sandbox returned no malicious verdict and no malicious dropped children were found. No tier-1 engine corroborated the single low-trust detection.
What To Do Now
Do not open the PDF on production systems. Re-scan with updated engines and monitor for follow-up submissions of the same hash. Keep endpoint protection enabled.
Where this verdict could be wrong1 caveat
- sandboxVerdicts empty and hasMaliciousSandboxVerdict=false despite MITRE mappings; sandbox may have recorded benign Acrobat activity
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 74/75 engines silent
- no tier-1 detections
- no malicious dropped children
- rare_new prevalence
- sandbox observed LSASS access
- direct-IP contact without domain
Treat the PDF as suspicious; avoid execution until additional engine coverage or sandbox consensus appears.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete1 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
Complete3 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
- 32filesystem & 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
OLVM_ca9110ad70744670bdda21ffaf6c4009.-RFP.pdf
66249124493210f73c373028b07ee18be78464aa98422af8c123b11cea6e656e
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
C:\Windows\System32\svchost.exe -k LocalSystemNetworkRestricted -p -s StorSvc
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\DllHost.exe /Processid:{133EAC4F-5891-4D04-BADA-D84870380A80}
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
Tmp22F4.tmp
C:\Users\<USER>\AppData\Local\Temp\Tmp22F4.tmp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
162.159.36.2
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.
- 162.159.36.2
- C:\Users\<USER>\AppData\Local\Temp\acroNGLLog.txt
- C:\Users\<USER>\AppData\Local\Temp\Tmp22F4.tmp
- C:\Users\<USER>\AppData\Local\Temp\Tmp248B.tmp
- C:\Users\<USER>\AppData\Local\Temp\A9dbacep_1gwtq1t_4p4.tmp
- C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.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:\ProgramData\Microsoft\Windows\WER\Temp\WER4154.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER5A5C.tmp
- Global\_MSIExecute
- Global\MSILOG_9284b18f1dd2ad5GOL.81731ISM_pmeT_lacoL_ataDppA_onurB_sresU_:C
- Local\SessionImmersiveColorMutex
- Local\WERReportingForProcess4104
- Global\cd621854-4696-42ac-947e-fc40832f4ddd
Files this sample writes at runtime
This file drops 2 children at runtime. None are currently flagged malicious in our cache.
- eacad3e01b8b0a44ac03…df796dNever scannednever seen before
- 513fb5d3b4195ab59af2…64de2eNever 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
- 1 / 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
1 of 75 antivirus engines flagged the file, including McAfeeD.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 1 time from 1 source.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: OLVM_ca9110ad70744670bdda21ffaf6c4009.-RFP.pdf — 66249124493210f73c373028b07ee18be78464aa98422af8c123b11cea6e656e
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — C:\Windows\System32\svchost.exe -k LocalSystemNetworkRestricted -p -s StorSvc
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\DllHost.exe /Processid:{133EAC4F-5891-4D04-BADA-D84870380A80}
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: acroNGLLog.txt — C:\Users\<USER>\AppData\Local\Temp\acroNGLLog.txt
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: Tmp22F4.tmp — C:\Users\<USER>\AppData\Local\Temp\Tmp22F4.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 162.159.36.2 — 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\svchost.exe -k LocalSystemNetworkRestricted -p -s StorSvcSandbox 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.
Evidence162.159.36.2
1 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. 1 antivirus detection make that low prevalence materially relevant, but rarity alone is not proof of malware.
Fingerprint and provenance
- File name
- OLVM_ca9110ad70744670bdda21ffaf6c4009.-RFP.pdf
- Format
- Code signing
- Not applicable to this file type
- Size
- 139.1 KB
- Last analyzed
- Aug 12, 2026, 8:57 PM UTC
66249124493210f73c373028b07ee18be78464aa98422af8c123b11cea6e656eSafety & 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 OLVM_ca9110ad70744670bdda21ffaf6c4009.-RFP.pdf safe, or is it malware?
What is OLVM_ca9110ad70744670bdda21ffaf6c4009.-RFP.pdf?
How many antivirus engines detected OLVM_ca9110ad70744670bdda21ffaf6c4009.-RFP.pdf?
What should I do if I already opened OLVM_ca9110ad70744670bdda21ffaf6c4009.-RFP.pdf?
How do I remove OLVM_ca9110ad70744670bdda21ffaf6c4009.-RFP.pdf?
What is the SHA-256 hash of OLVM_ca9110ad70744670bdda21ffaf6c4009.-RFP.pdf?
How up to date is this analysis of OLVM_ca9110ad70744670bdda21ffaf6c4009.-RFP.pdf?
Community
Member reviews and reports for this exact file hash.