Is dhl-awb63874309 .pdf safe?
Four independent tier-1 detections identify phishing or downloader content, while runtime evidence maps possible credential access, process injection, and destructive activity.
Seven of 75 engines flagged this delivery-themed PDF, including four independent tier-1 votes associated with phishing and downloader labels. A completed sandbox did not issue a malware verdict, but its evidence mapped T1003, T1055, and T1485, making the document unsafe to open or interact with.
bf7bf44d3e2c4e4afc…90edb89f5cfa8aRecommended next actions
Before opening
Do not open it. Delete this file from the device, then empty the Recycle Bin or Trash.
If you already opened it
Close it. If it opened links, requested credentials, or triggered unexpected behavior, disconnect from the internet and run a full device scan.
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.
Seven of 75 engines flagged this delivery-themed PDF, including four independent tier-1 votes associated with phishing and downloader labels. A completed sandbox did not issue a malware verdict, but its evidence mapped T1003, T1055, and T1485, making the document unsafe to open or interact with.
The strongest evidence is the combination of 7/75 detections and four independent tier-1 malicious votes. Multiple engines characterize the PDF as phishing content, while DrWeb identifies downloader behavior; however, there is no strong consensus on a named family. Runtime evidence maps credential access, process injection, and data destruction techniques, including reported interaction with LSASS. The single sandbox verdict was clean and no inspected child was confirmed harmful, which creates meaningful uncertainty around the behavioral mapping. Even so, those counter-signals do not outweigh the independent tier-1 detections and offensive indicators in a recently observed, auto-action PDF.
What We Detected
Seven of 75 antivirus engines flagged the PDF. Four independent tier-1 votes contributed to the result: Avast and AVG reported MalwareX-style PDF phishing, Avira and F-Secure reported PDF.Agent phishing, and DrWeb reported a PDF downloader; shared vendor technology means the displayed names exceed the independent-vote count.
Threat Behavior
The completed sandbox evidence mapped T1003 credential access, T1055 process injection, and T1485 data destruction. A heuristic also cited possible access to lsass.exe, which is a serious credential-theft indicator. The sandbox itself returned a clean verdict, and none of 10 inspected children was confirmed harmful, although all child verdicts remained unknown. The two listed domains had no cached malicious or suspicious reputation hits, but the observed IP address was not included in that cross-check, so complete host-reputation coverage is unavailable.
What To Do Now
Do not open the PDF, click embedded links, or enable document actions. Quarantine or delete it, keep endpoint protection enabled, and verify any purported shipment notice through the carrier's official website entered manually rather than through the document.
Where this verdict could be wrong4 caveats
- behaviour.hasMaliciousSandboxVerdict=false: the single completed sandbox run returned a clean result despite the mapped offensive techniques.
- droppedChildren inspected 10 files and hasMaliciousChild=false, although all 10 child verdicts remained unknown.
- 12 tier-1 engines reported no detection, including BitDefender, ESET-NOD32, Kaspersky, Microsoft, and Fortinet.
- contactedHosts found no cached malicious or suspicious hits for the two inspected domains, but it did not cover the observed IP address.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- behaviour.hasMaliciousSandboxVerdict=false
- droppedChildren.hasMaliciousChild=false across 10 inspected children
- 12 tier-1 engines reported no detection
- No cached malicious or suspicious result for the two inspected domains
- externalIntel.circl.hit=false
- 7/75 antivirus detections
- Four independent tier-1 malicious votes
- Phishing labels from Avast, AVG, Avira, and F-Secure
- Downloader label from DrWeb
- Offensive mappings T1003, T1055, and T1485
- Possible lsass.exe access reported by MalwareTips.Synth.CredentialDumper
Quarantine or delete the PDF and verify the claimed shipment independently through the carrier's official site. If it was opened, keep protection enabled and run a full endpoint scan, especially if any link or prompt was used.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete7 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial2 of 3 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete2 signature or behavior rules matched.
External intel
PartialIndependent reference checks were attempted but are incomplete.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 18MITRE ATT&CK techniques
- 15spawned processes
- 3network 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: 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: Listed running processes; both legitimate software and malware may do this.
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.
Threat context
How downloaders work
This file is a delivery vehicle. On its own it can look small and harmless, but its job is to quietly pull down and install the REAL payload — often a stealer, ransomware, or bot — from a server the attacker controls.
Bottom line:Because the dangerous part arrives later, early scans can look cleaner than the threat really is.
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
dhl-awb63874309 .pdf
bf7bf44d3e2c4e4afce59b97cab5a65fc0d418108692b4617690edb89f5cfa8a
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
C:\Windows\System32\mobsync.exe -Embedding
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Program Files\Adobe\Acrobat DC\Acrobat\Acrobat.exe" "C:\Users\<USER>\Desktop\dhl-awb63874309 .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
NGL
C:\Users\<USER>\AppData\Local\Temp\NGL\
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
acroipm2.adobe.com
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
atm.teams.mira.tm.svc.cloud.microsoft
Contact observed during runtime.
07Isolated runtime analysis - +1 more recorded observation in Analyst mode
7 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.
- acroipm2.adobe.com
- atm.teams.mira.tm.svc.cloud.microsoft
- 8.8.8.8
- HKEY_CURRENT_USER\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\SyncMgr\StartAtLogin
- HKEY_CURRENT_USER\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\SyncMgr\HandlerInstances\{750FDF10-2A26-11D1-A3EA-080036587F03}\SyncTime
- HKEY_CURRENT_USER\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\SyncMgr\HandlerInstances\{750FDF10-2A26-11D1-A3EA-080036587F03}\Enabled
- HKEY_CURRENT_USER\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\SyncMgr\HandlerInstances\{750FDF10-2A26-11D1-A3EA-080036587F03}\Connected
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SystemProtectedUserData\S-1-5-21-4005801669-2598574594-602355426-1001\AnyoneRead\ScaleFactors\ScaleFactors
- Software\Adobe\Acrobat Reader\DC\ExitSection\bLastExitNormal
- C:\Users\<USER>\AppData\Local\Temp\acroNGLLog.txt
- C:\Users\<USER>\AppData\Local\Temp\NGL\
- C:\Users\<USER>\AppData\Local\Temp\TmpF5F8.tmp
- C:\Users\<USER>\AppData\Local\Temp\A9uze2ki_17f9qfs_2n4.tmp
- C:\Users\<USER>\AppData\Local\Temp\A98wir7b_17f9qft_2n4.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:\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\SyncServiceThread
- Global\_MSIExecute
- Global\MSILOG_a6c9479e1dd5281GOL.90801ISM_pmeT_lacoL_ataDppA_onurB_sresU_:C
- Local\SessionImmersiveColorMutex
- Global\AdobeCrashProcessorLocalLowLock
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
- 06df2e7785eab362dc22…c5d529Never scannednever seen before
- 81ff65efc4487853bdb4…7c8e06Never scannednever seen before
- 16470ad82f92317f0966…1f08e3Never scannednever seen before
- 3cbce1708489017616cf…e5a7efNever scannednever seen before
- e710361afc0b8e87e9d1…785228Never 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.
- 2rule hits recorded
- 7 / 75engines flagged
- 5sources 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
7 of 75 antivirus engines flagged the file, including Avast and AVG.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 5 times from 5 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: dhl-awb63874309 .pdf — bf7bf44d3e2c4e4afce59b97cab5a65fc0d418108692b4617690edb89f5cfa8a
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — C:\Windows\System32\mobsync.exe -Embedding
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Program Files\Adobe\Acrobat DC\Acrobat\Acrobat.exe" "C:\Users\<USER>\Desktop\dhl-awb63874309 .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: NGL — C:\Users\<USER>\AppData\Local\Temp\NGL\
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: acroipm2.adobe.com — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: atm.teams.mira.tm.svc.cloud.microsoft — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: downloader
Available reference checks returned no match, but at least one source was unavailable. This is not a clean result.
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
7 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
- dhl-awb63874309 .pdf
- Format
- Code signing
- Not applicable to this file type
- Size
- 77.6 KB
- Last analyzed
- Oct 4, 2026, 5:22 AM UTC
bf7bf44d3e2c4e4afce59b97cab5a65fc0d418108692b4617690edb89f5cfa8aSafety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file is dangerous. Treat it as harmful and remove it.
- Recovery step 01
Don't open this file. Delete this file from the device, then empty the Recycle Bin or Trash.
- Recovery step 02
If you already opened it, disconnect from the internet and start with a full antivirus scan or Microsoft Defender Offline scan. If compromise is suspected or the problem persists, use a reputable second-opinion scanner and follow incident-recovery or clean-reinstall guidance.
- Recovery step 03
From a different, clean device, change the passwords on your important accounts (email and banking first) and turn on two-factor authentication.
- Recovery step 04
Get a fresh copy from the original trusted source and verify its exact hash when possible.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is dhl-awb63874309 .pdf a virus?
What is dhl-awb63874309 .pdf?
How many antivirus engines detected dhl-awb63874309 .pdf?
What should I do if I already opened dhl-awb63874309 .pdf?
How do I remove dhl-awb63874309 .pdf?
What kind of malware is dhl-awb63874309 .pdf?
What is the SHA-256 hash of dhl-awb63874309 .pdf?
How up to date is this analysis of dhl-awb63874309 .pdf?
Community
Member reviews and reports for this exact file hash.