Malicious PDF — malware analysis report

Static analysis result for SHA-256 1c75f321b01ca3d0…

MALICIOUS

PDF

30.8 KB
MD5: 0525130034aa087b7eee4590f170a652 SHA-1: bf77ab67adfea397f6ef9b00e776bbe52401eae4 SHA-256: 1c75f321b01ca3d0842c0093e9cc274a76b5f6736f7fe6180cb629f8540ef12a
196 Risk Score

Malware Insights

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

The PDF contains high-severity heuristics indicating embedded and XFA-based executable scripts, including eval() and unescape() calls, typical of JavaScript exploitation. An embedded file was also detected. The ML classifier strongly flagged this PDF as malicious. The primary attack vector appears to be leveraging XFA form scripts to execute malicious code, likely leading to a second-stage payload download or execution.

Machine Learning

  • Nyx PDF Classifier malicious score 1.0000

Heuristics 9

  • 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.
  • eval() call high PDF_EVAL
    eval() found — commonly used for obfuscated exploit execution
  • unescape() call high PDF_UNESCAPE
    unescape() found — often used to decode shellcode in PDF JS exploits
  • 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.
  • Embedded file low PDF_EMBEDDED
    PDF embeds a file attachment — could carry an executable or another weaponised document as a nested payload
  • 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.
  • 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.
  • Embedded URL info EMBEDDED_URL
    One or more URLs were extracted from the document. The URL itself is not a detection — see the per-URL labels for which channel (macro, JS, link annotation, document body, ...) reached each URL.
    URL http://ns.adobe.com/xdp/
    • http://www.xfa.org/schema/xfa-template/2.5/
    • http://www.xfa.org/schema/xfa-data/1.0/

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
embedded_file_obj0008.bin
90bb7453f964e07ca7afce3da1fd36f932089b0f135bac7b8781d13efcc55a75
pdf-embedded-file PDF EmbeddedFile object 8 at offset 0xC6 30830 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact contains 4 eval/decoder/string-building token(s).