Malicious PDF — malware analysis report

Static analysis result for SHA-256 4cd70de3e9041884…

MALICIOUS

PDF

1.95 MB
MD5: 34270e0584ac0aff3bf5f6625cac8a0a SHA-1: 39ea66172ce7f5416084c43fed3375f255fb37cb SHA-256: 4cd70de3e90418844e441fd7efab0b9896c5c8bc29c8d6b8166c17b6acad86b1
168 Risk Score

Malware Insights

MITRE ATT&CK
T1059.001 Command and Scripting Interpreter: PowerShell T1204.002 Malicious File: Malicious File

The PDF file contains XFA form elements with embedded JavaScript that triggers a heap spray exploit. This exploit is designed to execute arbitrary code, and the ML classifier strongly indicates maliciousness. The embedded JavaScript likely serves to download and execute a second-stage payload from the reconstructed URL 'http://dintarhafriza.no-ip.info:80/PuqaJL?pQI O=4&sQJo=151'.

Machine Learning

  • Nyx PDF Classifier malicious score 0.9897

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_off00001ad0.js
681520e69e97f863c80ae0e575c3c3b2b31abcfc34b55b078aae42e11c53768c
decompressed-pdf-stream PDF FlateDecoded stream at offset 0x1AD0 97296 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact contains 5 eval/decoder/string-building token(s).