Malicious PDF — malware analysis report

Static analysis result for SHA-256 cdc64e3a8139771a…

MALICIOUS

PDF

44.0 KB Created: 2006-10-03 13:54:05 -05:00 Authoring application: OmniForm Premium (via APJavaScript 2.2.1 Windows SPDF_1112 Oct 3 2005)
MD5: 736ad11dcbaded4a05922349bba4da95 SHA-1: 8fcea48920300292fda0409a1492ba26dc75d8e6 SHA-256: cdc64e3a8139771a567efb2da76177e49ec4da574e678a71ee982564d40a9136
82 Risk Score

Malware Insights

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

The PDF file contains embedded JavaScript, indicated by multiple heuristic firings including 'PDF_JAVASCRIPT' and 'PDF_JS'. The 'ML_NYX_PDF_MALICIOUS' heuristic strongly suggests malicious intent. The embedded JavaScript stream, 'stream_006_off0000a5f5.js', is the primary indicator of the attack. While the exact script functionality is not detailed, its presence within a PDF and the high ML score point towards an attempt to exploit vulnerabilities or deliver a payload.

Machine Learning

  • Nyx PDF Classifier malicious score 0.9970

Heuristics 6

  • 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.
  • 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.
  • XFA form low PDF_XFA
    PDF uses XML Forms Architecture — can contain script logic
  • AcroForm button with action trigger low PDF_ACROFORM_BUTTON
    PDF contains a /Btn form field together with a SubmitForm/URI/Launch/JS trigger — this is the building block of fake 'Download' or 'Open' button overlays used in PDF phishing lures
  • 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/pdfx/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 3

Files carved from inside the sample during analysis.

FilenameKindSourceSize
stream_006_off0000a5f5.js
d1dfd457a2fdd3cec4091f689f39b85b35666aa5599ef3a8d5f9a80d1e2ce105
decompressed-pdf-stream PDF FlateDecoded stream at offset 0xA5F5 1042 bytes
font_00_type1_off0000aaa3.bin
c6bf78478c9c4dd5b3b86554d34c78f847f70af4118f9ff083c1fccf0e8e932b
pdf-font-stream PDF embedded font (type1) at offset 0xAAA3 97 bytes
font_01_type1_off0000ad32.bin
b749644b3e758e7335900ab2e7499eaa64b3a946849f1f8a0948287bdd96763d
pdf-font-stream PDF embedded font (type1) at offset 0xAD32 144 bytes