Malicious PDF — malware analysis report

Static analysis result for SHA-256 e725c35acef58cfb…

MALICIOUS

PDF

43.1 KB
MD5: 8468676ced79aedd0328d5eddb87bb0e SHA-1: d7d41b00e6db0f49ef93cdc82a6a5d74688252e4 SHA-256: e725c35acef58cfbb761cc944703eaa879fc7b4b6cdd69bc3f5d68ab6e7d1ebc
138 Risk Score

Malware Insights

MITRE ATT&CK
T1059.001 PowerShell T1204.002 Malicious File: User Execution: Malicious File

The PDF file contains XFA form elements with embedded JavaScript, triggering a heap spray exploit. This script is designed to deobfuscate and execute a payload from a remote URL. The reconstructed URL is "http://diwylahhalazralan.bounceeme.net:80/eHYnG?dcQ H=12&zWsL=12551", indicating a likely download and execution of a second-stage malicious artifact. The presence of XFA heap spray and embedded script points to a malicious document designed for initial payload delivery.

Heuristics 6

  • XFA form contains risky executable script high CVE related PDF_XFA_SCRIPT
    PDF embeds an XFA form whose script block contains exploit, submission/launch, or shell-execution primitives. Ordinary LiveCycle print/update scripts are left as generic XFA/JS signals unless stronger behavior is present.
  • XFA JavaScript heap-spray exploit code critical PDF_XFA_HEAP_SPRAY
    PDF contains XFA script content with heap-spray or shellcode-like JavaScript markers such as large encoded word sequences, util.pack, large arrays, or spray variable names. This is a weaponised Adobe Reader exploit pattern, not a normal interactive form.
  • Embedded script payload in PDF stream medium PDF_EMBEDDED_SCRIPT_PAYLOAD
    PDF stream bytes contain an HTML/XFA <script> tag without accompanying Windows shell-execution primitives — common in accessible XFA forms but worth surfacing for analyst review.
  • XFA form low PDF_XFA
    PDF uses XML Forms Architecture — can contain script logic
  • String.fromCharCode low PDF_FROMCHARCODE
    String.fromCharCode found — used to construct payload strings dynamically. Common in benign JavaScript libraries for codepoint manipulation, so this alone is informational; weaponised use is also caught by the dedicated fromCharCode-stage and exploit-shape rules. (matched inside decoded stream)
  • Suspicious extracted artifact info EXTRACTED_FILE_STATIC_TRIAGE
    One or more files extracted from inside this sample matched static suspicious-content checks such as script obfuscation, encoded payload blobs, packed data, or execution/download terms.

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
stream_000_off00000bfd.js
5427ab1011ef927197185237a48076b7974886ae246c530ee2c0bf69760a583d
decompressed-pdf-stream PDF FlateDecoded stream at offset 0xBFD 449256 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact contains 5 eval/decoder/string-building token(s).