Malicious PDF — malware analysis report

Static analysis result for SHA-256 3ab653275d6f0fba…

MALICIOUS

PDF

23.6 KB
MD5: ecca4e0625ebc009c80741dcb3407efa SHA-1: 8d783f8906af394e1542406cf626e27e1e7e1a3a SHA-256: 3ab653275d6f0fbac4293648d513eccd947a72360152612d3c250782e989e0ca
60 Risk Score

Malware Insights

MITRE ATT&CK
T1059.001 PowerShell

The PDF file was flagged as malicious by an ML classifier with high confidence. Static analysis revealed embedded JavaScript streams, including one that was deobfuscated. The presence of JavaScript actions and embedded JS streams, along with the ML classification, strongly suggests the document is a malicious loader. The deobfuscated JavaScript is likely responsible for downloading and executing a second-stage payload, although its exact functionality could not be fully determined due to obfuscation.

Machine Learning

  • Nyx PDF Classifier malicious score 0.9994

Heuristics 6

  • 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.
  • 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)
  • PDF paints image(s) but contains no text operators info PDF_IMAGE_ONLY_LURE
    PDF has 1 image XObject(s) and the content stream contains no text-emitting operators (BT/ET, Tj, TJ, ', ") in either raw bytes or decompressed streams — this is the screenshot-as-PDF pattern used to bypass text-based scanners and to deliver instructions purely through rendered pixels. It is informational unless paired with invisible links or risky URI context.
  • 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/xap/1.0/
    • http://purl.org/dc/elements/1.1/
    • http://ns.adobe.com/xap/1.0/mm/
    • http://ns.adobe.com/pdf/1.3/

Extracted artifacts 2

Files carved from inside the sample during analysis.

FilenameKindSourceSize
javascript_obj0099_000.js
f2db292095531069fb308e8299e5dd7ebf22eacb18f675631ffddd18e8d8246d		 pdf-javascript-stream PDF /JS object 99 at offset 0x548D 8537 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact contains 2 eval/decoder/string-building token(s). Carved artifact contains 9 long base64-like blob(s).
deobfuscated.js
9fecdb08f3eb6cf94f9bd5c2cea89b0e5e8b2c64305cfdea3c335f6a3bbb3e8e		 deobfuscated-js PDF JavaScript deobfuscation pass 40315 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact contains 4 eval/decoder/string-building token(s). Carved artifact contains 18 long base64-like blob(s).

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