PDF malware analysis — malicious · 8f3266eeb6b9a232

MALICIOUS

PDF

23.6 KB

MD5: 2881d82e2b5507d0687cd4c2f85f0378 SHA-1: 66abc426c49a6a2cf983e7019ac180fe68dda449 SHA-256: 8f3266eeb6b9a232081b6bfe09160a964d6c577fed129c316db706a6b7e0da8e

60 Risk Score

Malware Insights

MITRE ATT&CK

T1059.001 PowerShell T1566.001 Spearphishing Attachment

The PDF file was flagged as malicious by an ML classifier with high confidence. Heuristics indicate the presence of embedded JavaScript, specifically noting the use of String.fromCharCode and a deobfuscated JavaScript stream. While no specific URLs were extracted and the document body was unreadable, the presence of these JavaScript artifacts strongly suggests an attempt to download and execute a secondary payload, a common technique for malware delivery. The techniques T1059.001 (PowerShell) and T1566.001 (Spearphishing Attachment) are relevant due to the nature of embedded scripts in documents.

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.

Filename	Kind	Source	Size
`javascript_obj0099_000.js` `5c0c06d4d1ef2d4815a93aab84502fa9b63ae8151a0a47aed9bd9bb932ece686`	pdf-javascript-stream	PDF /JS object 99 at offset 0x548D	8621 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` `edfab9a63d612b7782079266e7e1d9cb02dcdb89ec8f898d7b5f5190acf4bd3c`	deobfuscated-js	PDF JavaScript deobfuscation pass	40883 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.