Malicious PDF — malware analysis report

Static analysis result for SHA-256 91c163019c87e48a…

MALICIOUS

PDF

14.9 KB Created: 2009-11-15 19:41:70 Authoring application: PDF Library 4.3.9 (via PDF Library 3.9.7)
MD5: d9a278ad5c214cc689d690557539bdce SHA-1: 4e8a7da6dab9140f16712e0905020fb348534733 SHA-256: 91c163019c87e48a4b4959855a9e690fbeb33912263967e60d70f29a52b4138f
166 Risk Score

Malware Insights

MITRE ATT&CK
T1059.001 PowerShell T1204.002 Malicious File

The PDF was flagged by multiple heuristics, including a critical ClamAV detection identifying it as 'Pdf.Dropper.Agent-1828835'. An extracted artifact was also detected by ClamAV as 'Win.Trojan.Agent-36166'. The presence of embedded JavaScript, indicated by the 'PDF_JAVASCRIPT' and 'PDF_JS' heuristics, strongly suggests that the PDF is designed to execute malicious code, likely to download and run a second-stage payload.

Machine Learning

  • Nyx PDF Classifier malicious score 0.9999

Heuristics 4

  • ClamAV: Pdf.Dropper.Agent-1828835 critical CLAMAV_DETECTION
    ClamAV detected this file as malware: Pdf.Dropper.Agent-1828835
  • ClamAV detection on extracted artifact critical EXTRACTED_FILE_CLAMAV
    ClamAV flagged at least one file extracted from inside this sample. Even when the wrapping document carries no AV detection of its own, a hit on the carved artifact is a strong indicator the sample is a delivery vehicle.
  • 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.

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
javascript_obj0007_000.js
124fa5a49c09e3c87a35d0cfbf88ba0ac6b8163c55debd40b307b372d5b68a8d		 pdf-javascript-stream PDF /JS object 7 at offset 0x1A5 83622 bytes
Detection
ClamAV: Win.Trojan.Agent-36166
Obfuscation or payload: unlikely

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