Malicious PDF — malware analysis report

Static analysis result for SHA-256 9468a4f17a2f7c3e…

MALICIOUS

PDF

26.2 KB
MD5: 10c93ad152e9d65540599bea4399cc55 SHA-1: 7519d61c0cc24c827e03307069fd6dcd05ba9687 SHA-256: 9468a4f17a2f7c3e775f9237184acca964a57f707fa533d7514060583af184f7
156 Risk Score

Malware Insights

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

This PDF document contains an XFA form with embedded JavaScript, flagged by multiple high-severity heuristics including PDF_XFA_SCRIPT and ML_NYX_PDF_MALICIOUS. The script utilizes functions like unescape() and String.fromCharCode(), indicating obfuscation and potential exploit delivery. The embedded file artifact further suggests a multi-stage attack. The primary attack vector appears to be leveraging XFA form vulnerabilities to execute malicious code.

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

Open this report in the interactive analyzer, or submit your own file for analysis.