Malicious PDF — malware analysis report

Static analysis result for SHA-256 9ef31083e071746a…

MALICIOUS

PDF

26.1 KB
MD5: 4b7af86a14672b21972931eae79afd1e SHA-1: 42cad34164a63dd84d29ef31e4c2f08300731377 SHA-256: 9ef31083e071746af1af49a6ceba64271d4b6a6e35aa01a237ebf19ca2048246
126 Risk Score

Malware Insights

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

This PDF document contains embedded JavaScript, indicated by the PDF_XFA_SCRIPT and PDF_EMBEDDED_SCRIPT_PAYLOAD heuristics. The script utilizes functions like unescape() and String.fromCharCode(), suggesting obfuscation to hide its true intent. 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. The document's structure and the presence of XFA forms further support this malicious behavior.

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