Malicious PDF — malware analysis report

Static analysis result for SHA-256 af95ac73888848fe…

MALICIOUS

PDF

9.5 KB
MD5: 66ac43f05d8530a7f27cad0cb714a264 SHA-1: dfe0ab114b4a7d0a18a7b4a2dd21920d3756b322 SHA-256: af95ac73888848fe95e929ec4dc66415800a9fa991bac5b2db01109c5fcd2603
126 Risk Score

Malware Insights

MITRE ATT&CK
T1059.007 Scripting: JavaScript T1204.002 Malicious File: User Execution: Malicious JavaScript

The PDF file contains high-severity heuristics indicating the presence of risky executable scripts within an XFA form, along with an embedded script payload. The deobfuscated JavaScript, extracted as 'deobfuscated.js', is likely responsible for executing the malicious payload. The presence of 'eval()' and 'String.fromCharCode()' further suggests code execution and obfuscation techniques. The overall purpose appears to be the delivery of a secondary malicious payload via the embedded script.

Heuristics 7

  • 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 (matched inside decoded stream)
  • 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. (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 2

Files carved from inside the sample during analysis.

FilenameKindSourceSize
embedded_file_obj0041.bin
af787deb2f6b689d4b4fab712ae789d15c855cdae2f5e44472eb2fe2c31a5a65
pdf-embedded-file PDF EmbeddedFile object 41 at offset 0x52 1163 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact contains 2 eval/decoder/string-building token(s).
deobfuscated.js
8057bd48d2e04dad9a448c33711dbc3964fbc2deaf2fb57a4f3faa6a23cb5a1f
deobfuscated-js PDF JavaScript deobfuscation pass 1946 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact contains 2 eval/decoder/string-building token(s).