Malicious PDF — malware analysis report

Static analysis result for SHA-256 b3abccf616a33e2c…

MALICIOUS

PDF

25.2 KB Created: 2011-72-51 03:25:00 Authoring application: String.fromCharCode
MD5: 3de3bc656d0dbf99cbdb3d747d05aa7b SHA-1: 498db1f725eddb212a79d1c9efb9e44589f7dc61 SHA-256: b3abccf616a33e2cc37430d62789a9383575ac1542e896b6621c8af235986614
64 Risk Score

Malware Insights

MITRE ATT&CK
T1059.001 PowerShell

The PDF file contains embedded JavaScript within its metadata, as indicated by the 'PDF_METADATA_EVAL_STAGER' heuristic. This JavaScript is likely used to decode and execute a malicious payload. The presence of 'String.fromCharCode' further suggests obfuscation techniques commonly used in document-based malware delivery. No specific family could be identified, and the primary IOC is the embedded JavaScript file.

Heuristics 4

  • 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.

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
javascript_obj0001_000.js
1cc46075ddf9991f1201b118e6162b0a61986d9391ae0e9a2af7be061240407d
pdf-javascript-stream PDF /JS object 1 at offset 0xA 479 bytes