Malicious PDF — malware analysis report

Static analysis result for SHA-256 dcee5472a773a5c4…

MALICIOUS

PDF

24.3 KB
MD5: da07a0b65219863da77642914683e4ab SHA-1: f2b31e64b9ba3e1d6a2e6219a350280be7b372f8 SHA-256: dcee5472a773a5c46db44eae2543ec88d72ad585c609c92b1d767460398200b8
156 Risk Score

Malware Insights

MITRE ATT&CK
T1059.001 JavaScript/JScript T1204.002 Malicious File

The PDF file contains embedded JavaScript, indicated by the PDF_EMBEDDED_SCRIPT_PAYLOAD and PDF_XFA_SCRIPT heuristics. The script utilizes unescape() and String.fromCharCode, suggesting obfuscation to hide its malicious intent. The ML classifier strongly flags this PDF as malicious. The primary goal appears to be the execution of this script, which likely leads to the download and execution of a secondary payload, as evidenced by the embedded file artifact.

Machine Learning

  • Nyx PDF Classifier malicious score 1.0000

Heuristics 8

  • 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.
  • 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
c4ad1758af02c949cf8b09b6e9935f2af291744d59011043bae588cd30f66bd3
pdf-embedded-file PDF EmbeddedFile object 8 at offset 0xD1 24117 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact contains 2 eval/decoder/string-building token(s).