Malicious PDF — malware analysis report

Static analysis result for SHA-256 938f1dc76045704c…

MALICIOUS

PDF

56.0 KB Created: 2009-07-11 08:11:56 Authoring application: Scribus 1.3.3.13 (via Scribus PDF Library 1.3.3.13)
MD5: baaacb665cf88f70d78d46c3e21ebf14 SHA-1: cd983d0d207cb848e511dbf0f63866600bb0cc60 SHA-256: 938f1dc76045704c9ca7c54eb6569ea689cb096ab2916598f8c41faf4b6c7b4b
108 Risk Score

Malware Insights

MITRE ATT&CK
T1059.001 PowerShell

The PDF file was flagged by multiple heuristics, including ML classifiers and ClamAV, indicating malicious content. Specifically, the presence of embedded JavaScript streams (PDF_JAVASCRIPT, PDF_JS) suggests an attempt to execute code. The ML_NYX_PDF_MALICIOUS score of 0.96 further supports this. While the document body is largely unreadable and contains no explicit lures, the embedded JavaScript is the primary indicator of malicious intent, likely to download and execute a secondary payload.

Machine Learning

  • Nyx PDF Classifier malicious score 0.9633

Heuristics 5

  • ClamAV: Heuristics.PDF.ObfuscatedNameObject critical CLAMAV_DETECTION
    ClamAV detected this file as malware: Heuristics.PDF.ObfuscatedNameObject
  • 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.
  • PDF paints image(s) but contains no text operators info PDF_IMAGE_ONLY_LURE
    PDF has 2 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.
  • 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://ns.adobe.com/xap/1.0/
    • http://www.w3.org/1999/02/22-rdf-syntax-ns#
    • http://purl.org/dc/elements/1.1/
    • http://ns.adobe.com/photoshop/1.0/
    • http://ns.adobe.com/xap/1.0/mm/
    • http://ns.adobe.com/tiff/1.0/
    • http://ns.adobe.com/exif/1.0/

Extracted artifacts 3

Files carved from inside the sample during analysis.

FilenameKindSourceSize
javascript_obj0034_000.js
ee87ac1ef5686c0eeabdbcc24bff6f44f5a2b1659f621cec90e716bcb32ef9f9		 pdf-javascript-stream PDF /JS object 34 at offset 0xAFBD 44132 bytes
javascript_obj0035_001.js
284dfb44946c9d2db90ac198fbeed45d2bff0a565a305d4ae0ad611ca3d1e8c1		 pdf-javascript-stream PDF /JS object 35 at offset 0xD8AE 265 bytes
javascript_obj0036_002.js
9afcd2111e7cd4d16e4f552d78c877e6284d25e5a389e74d45a9125232f66630		 pdf-javascript-stream PDF /JS object 36 at offset 0xD9CA 214 bytes

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