Is Rfq_Project_Agreement_2026 (2).pdf safe?
PDF triggered sandbox heuristics for credential access and process injection but zero engines flagged it.
No antivirus engine detected malice, yet the sandbox recorded LSASS reads, process injection and direct-IP traffic. The file is rare and newly submitted, leaving the evidence in conflict.
abeb8f9b9e7fcd4f6a…bc6b2ebceb3352Recommended 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 detected malice, yet the sandbox recorded LSASS reads, process injection and direct-IP traffic. The file is rare and newly submitted, leaving the evidence in conflict.
Zero detections across 75 engines, including 16 tier-1, normally points to clean. However, the sandbox captured three offensive MITRE techniques and direct-IP contact, and the file is only two days old with a single submission. No external-intel corroboration exists and the contacted-host reputation check was not completed. The combination of strong static clean signals and behavioural red flags produces a borderline mixed-signal case.
What We Detected
75 engines scanned the PDF; none returned a malicious or suspicious result. Sandbox execution logged LSASS access (T1003), process injection (T1055) and data-destruction attempts (T1485), plus a direct connection to IP 162.159.36.2.
Threat Behavior
The observed techniques match credential-dumping and injection patterns, yet no dropped child was flagged malicious and no engine family consensus emerged. External intelligence sources returned no hits.
What To Do Now
Do not open the document on a production system. Re-scan after additional engine coverage or sandbox runs become available; keep endpoint protection enabled.
Where this verdict could be wrong1 caveat
- Sandbox recorded LSASS access and process injection, yet no engine labelled the file malicious and hasMaliciousSandboxVerdict remains false.
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 16 tier-1
- No malicious children or external-intel hits
- Sandbox observed LSASS access and process injection
- Direct-IP contact with no domain recorded
- File is rare and only two days old
Treat as suspicious; avoid execution until further sandbox or engine results clarify the conflicting signals.
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
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
- 14MITRE ATT&CK techniques
- 14spawned processes
- 1network 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: 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
Rfq_Project_Agreement_2026 (2).pdf
abeb8f9b9e7fcd4f6a633aba6729bd2d1b1b948e9865325a4abc6b2ebceb3352
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Program Files\Adobe\Acrobat DC\Acrobat\Acrobat.exe" "C:\Users\<USER>\Desktop\Rfq_Project_Agreement_2026 _2_.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
Download-1.tmp
C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.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:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
- C:\Users\<USER>\AppData\Local\Adobe\Acrobat\DC\SOPHIA\Reader\SOPHIA.json
- C:\Users\<USER>\AppData\Local\Adobe\Acrobat\DC\SOPHIA\Reader\Files\TESTING
- Local\07D45698
- 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\Adobe\Acrobat\DC\SOPHIA\Reader\Files\DC_READER_LAUNCH_CARD
- C:\Users\<USER>\AppData\Local\Adobe\Acrobat\DC\SOPHIA\Reader\Files\ACROBAT_READER_MASTER_SURFACEID
- Local\SessionImmersiveColorMutex
- Global\_MSIExecute
- Global\MSILOG_8b0189bf1dd34f8GOL.34531ISM_pmeT_lacoL_ataDppA_onurB_sresU_:C
- \Sessions\1\BaseNamedObjects\{100184D2-BDC3-477a-B8D3-65548B67914C}_7144
- \Sessions\1\BaseNamedObjects\Local\{100184D2-BDC3-477a-B8D3-65548B67914C}_6552
Files this sample writes at runtime
This file drops 7 children at runtime. None are currently flagged malicious in our cache.
- eacad3e01b8b0a44ac03…df796dNever scannednever seen before
- ad27039abac3252c3b39…37ede5Never scannednever seen before
- 5a5af0098196929f92e2…f143dfNever scannednever seen before
- 81ff65efc4487853bdb4…7c8e06Never scannednever seen before
- d3c351eec6bcc81c45b6…cba0f8Never scannednever seen before
- 2e85af572223d686d4b8…0b860dNever scannednever seen before
- e3b0c44298fc1c149afb…52b855Never 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: Rfq_Project_Agreement_2026 (2).pdf — abeb8f9b9e7fcd4f6a633aba6729bd2d1b1b948e9865325a4abc6b2ebceb3352
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Program Files\Adobe\Acrobat DC\Acrobat\Acrobat.exe" "C:\Users\<USER>\Desktop\Rfq_Project_Agreement_2026 _2_.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: Download-1.tmp — C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.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\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.
Evidence162.159.36.2
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
- Rfq_Project_Agreement_2026 (2).pdf
- Format
- Code signing
- Not applicable to this file type
- Size
- 218.1 KB
- Last analyzed
- Aug 27, 2026, 9:39 PM UTC
abeb8f9b9e7fcd4f6a633aba6729bd2d1b1b948e9865325a4abc6b2ebceb3352Safety & 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 Rfq_Project_Agreement_2026 (2).pdf safe, or is it malware?
What is Rfq_Project_Agreement_2026 (2).pdf?
How many antivirus engines detected Rfq_Project_Agreement_2026 (2).pdf?
I already downloaded and opened Rfq_Project_Agreement_2026 (2).pdf — what should I do?
How do I remove Rfq_Project_Agreement_2026 (2).pdf?
What is the SHA-256 hash of Rfq_Project_Agreement_2026 (2).pdf?
How up to date is this analysis of Rfq_Project_Agreement_2026 (2).pdf?
Community
Member reviews and reports for this exact file hash.