PDF malware analysis — malicious · c6b2b46c147ff57c

MALICIOUS

PDF

11.2 KB Authoring application: Scribus 1.4.5.1 (via Scribus PDF Library 1.5.3.1)

MD5: 111d84f846709f4a2552140378d655f7 SHA-1: 738f8b6f8242a406150c5b2e3a5522e63b63e23f SHA-256: c6b2b46c147ff57c22ac5ec93be22fbf9efd5a7846bd7563f251ff1e50cb316b

176 Risk Score

Malware Insights

MITRE ATT&CK

T1059.001 PowerShell T1027 Obfuscated Files or Information T1566.002 Spearphishing with Malicious Attachment

The PDF file contains embedded JavaScript, indicated by multiple heuristic firings including PDF_JAVASCRIPT, PDF_JS, PDF_EVAL, PDF_UNESCAPE, and PDF_METADATA_EVAL_STAGER. The ML classifier strongly flags this PDF as malicious. The embedded JavaScript streams, named javascript_obj0013_001.js and javascript_obj0013_002.js, are likely responsible for deobfuscating and executing a malicious payload, a common technique for PDF-based malware delivery.

Machine Learning

Nyx PDF Classifier malicious score 1.0000

Heuristics 7

eval() call high PDF_EVAL

eval() found — commonly used for obfuscated exploit execution
unescape() call high PDF_UNESCAPE

unescape() found — often used to decode shellcode in PDF JS exploits
PDF metadata JavaScript eval stager high PDF_METADATA_EVAL_STAGER

PDF JavaScript reads document metadata fields such as title, subject, or producer, decodes character data with parseInt/String.fromCharCode style helpers, and evals the recovered stage. This is a high-signal exploit-kit staging pattern.
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.
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.

Extracted artifacts 2

Files carved from inside the sample during analysis.

Filename	Kind	Source	Size
`javascript_obj0013_001.js` `04ccd1141cd68cf10bc29b156096d4aca87bcdec1dbe2436454107409447ed8d`	pdf-javascript-stream	PDF /JS object 13 at offset 0x38B	9958 bytes
Detection ClamAV: No threats found Obfuscation or payload: likely Carved artifact contains 6 eval/decoder/string-building token(s). Carved artifact contains 4 long base64-like blob(s).
`javascript_obj0013_002.js` `5d144a9e6c3254596d7cd45ec95017fd8602f2054e241940e43b5218f4a9f0da`	pdf-javascript-stream	PDF /JS object 13 at offset 0x3AD	10492 bytes
Detection ClamAV: No threats found Obfuscation or payload: likely Carved artifact contains 6 eval/decoder/string-building token(s). Carved artifact contains 4 long base64-like blob(s).

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