Malicious PDF — malware analysis report

Static analysis result for SHA-256 abbc35f77cbf3104…

MALICIOUS

PDF

68.0 KB Created: 2010-09-20 10:36:57 +08:00 Authoring application: pdfFactory Pro www.fineprint.cn (via pdfFactory Pro 3.21 (Windows XP Professional Chinese))
MD5: 4bd4faf138ed2b67fe680c28b2384b0e SHA-1: e59dc35bde39e2d1a364f4213ea7c6898cbb41d8 SHA-256: abbc35f77cbf31043980c1fd1fb4c2867ffea43a01a5df4a040518f46dd264c8
62 Risk Score

Malware Insights

MITRE ATT&CK
T1566.002 Spearphishing Attachment

The PDF file exhibits characteristics of a malicious document, specifically the presence of an embedded PDF with suspicious static findings. The 'POLYGLOT_CHILD_PDF_STATIC_TRIAGE' heuristic indicates that the embedded PDF has internal issues that are often associated with malicious content. The 'PDF_IMAGE_ONLY_LURE' heuristic suggests that the PDF might be using images to trick the user into interacting with it, while the 'EMBEDDED_URL' heuristic points to the presence of URLs within the document, which could be used for further exploitation or redirection. The benign nature of the extracted URLs suggests they are likely part of the PDF's legitimate structure rather than malicious C2 infrastructure.

Heuristics 3

  • Secondary embedded PDF body has suspicious static findings critical POLYGLOT_CHILD_PDF_STATIC_TRIAGE
    A valid PDF body was found at a nonzero offset inside another container and its carved contents matched PDF exploit or lure heuristics. This catches polyglots where the top-level magic routes to ZIP/OLE while a PDF reader or downstream parser opens the hidden PDF payload.
  • 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.
  • 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 3

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objstm_0017_00.bin
c515a5551a72a8497045fc7510d95c5a1a4edc56f02c0e8a1e04fb3285830168		 pdf-objstm-decoded PDF /ObjStm 17 0 obj (inflated) 1038 bytes
polyglot_child_pdf_off0000eefe.pdf
4d39f53fcb65d79db653af94f09a8b4e942e4ce41d8113b15dcb3628152a9227		 polyglot-child-pdf Secondary PDF body inside pdf container at offset 0xEEFE 8419 bytes
polyglot_child_pdf_off0000f7f4.pdf
4b16dada1ca3275de53ef776759c2486baa73e7c85f2f3490d9ca38a9466d91f		 polyglot-child-pdf Secondary PDF body inside pdf container at offset 0xF7F4 6125 bytes

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