Is Contract+Portal.pdf safe?
No antivirus engine detected the PDF, but one sandbox produced uncorroborated credential-access and process-injection mappings that warrant cautious handling.
The PDF received no detections from 75 antivirus engines, and the completed sandbox did not issue a malicious runtime finding. However, saved telemetry mapped activity to credential access, process injection, and data destruction, while the contacted IP received no completed reputation check; avoid opening it until its source is verified.
7184349a8f1c34243e…2e0797cadaeaa1Recommended 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 PDF received no detections from 75 antivirus engines, and the completed sandbox did not issue a malicious runtime finding. However, saved telemetry mapped activity to credential access, process injection, and data destruction, while the contacted IP received no completed reputation check; avoid opening it until its source is verified.
Static scanning found no detection across 75 engines, including all 17 tier-1 participants. One completed sandbox did not issue a malicious finding and recorded no dropped payload hashes or persistence indicators. Nevertheless, its telemetry mapped activity to T1003, T1055, and T1485, including possible LSASS access, which is not expected from an ordinary PDF. Those mappings are not independently corroborated and may reflect Adobe Acrobat or environmental activity rather than the document itself. The observed IP contact was not covered by a saved host-reputation check, leaving an important uncertainty.
What We Detected
None of 75 antivirus engines flagged the PDF, and all 17 tier-1 engines that participated returned no detection. Research feeds supplied no matching YARA rules or known malware record.
Threat Behavior
One completed sandbox run did not produce a malicious finding, dropped payload, or persistence indicator. However, saved telemetry mapped activity to credential access (T1003), process injection (T1055), and data destruction (T1485), including possible LSASS interaction. The limited evidence does not prove that the PDF caused these actions; Adobe Acrobat and surrounding system processes were active during the run. The run also recorded contact with 162.159.36.2, but no complete host-reputation result is available.
What To Do Now
Verify the document through a trusted, independent channel before opening it. Keep endpoint protection enabled, use an updated PDF reader with scripting restricted where practical, and request a fresh copy if the sender or business context cannot be confirmed.
Where this verdict could be wrong3 caveats
- All 75 engines were non-detecting, including 17 tier-1 engines, which weighs strongly against a known malicious document.
- The sole sandbox labeled the run clean, and no dropped file hashes or persistence indicators were recorded.
- The offensive mappings may reflect Adobe Acrobat or surrounding system activity rather than actions caused by the PDF; the available trace does not establish attribution.
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 reported a detection.
- All 17 tier-1 engines reported no detection.
- behaviour.hasMaliciousSandboxVerdict=false.
- No dropped file hashes or persistence indicators were recorded.
- YARAify returned zero rules and MalwareBazaar returned no hit.
- Sandbox telemetry mapped possible credential access through T1003.
- Sandbox telemetry mapped possible process injection through T1055.
- T1485 was present among the offensive runtime mappings.
- The observed IP 162.159.36.2 lacks a completed host-reputation cross-check.
- The file was first submitted only one day ago.
Do not open the document until its sender and purpose are independently verified. Keep security protection enabled and, if needed, inspect a fresh copy in a controlled 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
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
- 13spawned 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: 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
Contract+Portal.pdf
7184349a8f1c34243edd93ad73d4bb4decc9cfabee68a27d882e0797cadaeaa1
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Program Files\Adobe\Acrobat DC\Acrobat\Acrobat.exe" "C:\Users\<USER>\Desktop\Contract Portal.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
Tmp356.tmp
C:\Users\<USER>\AppData\Local\Temp\Tmp356.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\Tmp356.tmp
- C:\Users\<USER>\AppData\Local\Temp\Tmp480.tmp
- C:\Users\<USER>\AppData\Local\Temp\A92yq4ux_gkg3zw_2ro.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
- Global\_MSIExecute
- Global\MSILOG_3c7d6cd51dd4f81GOL.ca411ISM_pmeT_lacoL_ataDppA_onurB_sresU_:C
- Global\AdobeCrashProcessorLocalLowLock
- \Sessions\1\BaseNamedObjects\{100184D2-BDC3-477a-B8D3-65548B67914C}_6616
- \Sessions\1\BaseNamedObjects\Local\{100184D2-BDC3-477a-B8D3-65548B67914C}_6816
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
- 8sources 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 9 times from 8 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: Contract+Portal.pdf — 7184349a8f1c34243edd93ad73d4bb4decc9cfabee68a27d882e0797cadaeaa1
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Program Files\Adobe\Acrobat DC\Acrobat\Acrobat.exe" "C:\Users\<USER>\Desktop\Contract Portal.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: Tmp356.tmp — C:\Users\<USER>\AppData\Local\Temp\Tmp356.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
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- Contract+Portal.pdf
- Format
- Code signing
- Not applicable to this file type
- Size
- 20.3 KB
- Last analyzed
- Sep 29, 2026, 11:50 PM UTC
7184349a8f1c34243edd93ad73d4bb4decc9cfabee68a27d882e0797cadaeaa1Safety & 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 Contract+Portal.pdf safe, or is it malware?
What is Contract+Portal.pdf?
How many antivirus engines detected Contract+Portal.pdf?
What should I do if I already opened Contract+Portal.pdf?
How do I remove Contract+Portal.pdf?
What is the SHA-256 hash of Contract+Portal.pdf?
How up to date is this analysis of Contract+Portal.pdf?
Community
Member reviews and reports for this exact file hash.