Malicious PDF — malware analysis report

Static analysis result for SHA-256 56488296f5bca6ac…

MALICIOUS

PDF

556.7 KB Created: 2010-03-30 17:05:37 +08:00 Authoring application: PScript5.dll Version 5.2 (via Acrobat Distiller 6.0.1 (Windows))
MD5: 41144c5a0d226e38599f234a9c2a6ad8 SHA-1: ccd6066ad3d9791f413da72b63d5a9b867b1d124 SHA-256: 56488296f5bca6ac8a4de57b2998e6bdf2f67eaa035a5bbc5d6a2405854939ce
158 Risk Score

Malware Insights

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

The PDF file contains embedded JavaScript with multiple obfuscation techniques, including `eval()` and `unescape()`. This script is likely designed to exploit vulnerabilities within the PDF reader to download and execute a second-stage payload. The presence of a secondary embedded PDF with similar suspicious findings further supports this assessment. No specific family could be identified due to the heavy obfuscation.

Heuristics 7

  • Secondary embedded PDF body has suspicious static findings critical POLYGLOT_CHILD_PDF_STATIC_TRIAGE
    A valid PDF body was found at a nonzero offset inside another container and its carved contents matched PDF exploit or lure heuristics. This catches polyglots where the top-level magic routes to ZIP/OLE while a PDF reader or downstream parser opens the hidden PDF payload.
  • eval() call high PDF_EVAL
    eval() found — commonly used for obfuscated exploit execution (matched inside decoded stream)
  • unescape() call high PDF_UNESCAPE
    unescape() found — often used to decode shellcode in PDF JS exploits (matched inside decoded stream)
  • JavaScript action low PDF_JAVASCRIPT
    PDF contains a /JavaScript action. Generic JavaScript is common in benign forms; specific dangerous APIs are scored by separate rules.
  • Embedded JS stream low PDF_JS
    PDF references a /JS stream. Generic JavaScript is common in benign forms; specific dangerous APIs are scored by separate 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://www.w3.org/1999/02/22-rdf-syntax-ns#
    • http://ns.adobe.com/iX/1.0/
    • http://ns.adobe.com/pdf/1.3/
    • http://ns.adobe.com/xap/1.0/
    • http://ns.adobe.com/xap/1.0/mm/
    • http://purl.org/dc/elements/1.1/

Extracted artifacts 2

Files carved from inside the sample during analysis.

FilenameKindSourceSize
javascript_obj0014_000.js
f88a00e927e26df17805ed162ce7be240b356db723ca38aa13d59e510c6f437e
pdf-javascript-stream PDF /JS object 14 at offset 0x2CC 4691 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact contains 16 eval/decoder/string-building token(s).
polyglot_child_pdf_off00089aa9.pdf
5d1a7bab96c6cdecbfa015528b426866f21073a9a631dc8106479c86fd3208cf
polyglot-child-pdf Secondary PDF body inside pdf container at offset 0x89AA9 6177 bytes