Malicious PDF — malware analysis report

Static analysis result for SHA-256 6ce3e69d73f0d59b…

MALICIOUS

PDF

5.4 KB Created: 2004-05-02 19:56:00 Authoring application: e
MD5: c561d0e800b113a51f73cd9ee1278cad SHA-1: 603add7abd2741872eccc52317b8ef91833a06d1 SHA-256: 6ce3e69d73f0d59b04aa411dcde03acb9a81c3fb0c89f089e5e12b35de2ece6a
122 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution T1059.007 JavaScript

The sample is a PDF file that contains an embedded JavaScript payload, identified by the 'PDF_EMBEDDED_SCRIPT_PAYLOAD' heuristic. The 'CVE_2010_0188' heuristic indicates that the file exploits a known vulnerability in Adobe Reader related to XFA forms. The embedded JavaScript is likely responsible for downloading and executing a secondary malicious payload, as suggested by the 'ML_NYX_PDF_MALICIOUS' classifier and the presence of an extracted JavaScript file. The benign URLs found are related to XFA specifications and do not appear to be malicious.

Machine Learning

  • Nyx PDF Classifier malicious score 1.0000

Heuristics 8

  • Adobe Reader LibTIFF XFA image exploit — CVE-2010-0188 critical CVE likely CVE_2010_0188
    PDF contains the CVE-2010-0188 exploit template: XFA JavaScript heap-spray setup, a generated TIFF image payload, and assignment of that TIFF data to an XFA image field rawValue to trigger Adobe Reader's LibTIFF parser.
  • Embedded file low PDF_EMBEDDED
    PDF embeds a file attachment — could carry an executable or another weaponised document as a nested payload
  • XFA form low PDF_XFA
    PDF uses XML Forms Architecture — can contain script logic
  • Embedded script payload in PDF stream low PDF_EMBEDDED_SCRIPT_PAYLOAD
    PDF stream bytes contain an HTML/XFA <script> tag without accompanying Windows shell-execution primitives — common in accessible XFA forms but worth surfacing for analyst review.
  • Object number defined twice with different bodies info PDF_DUPLICATE_OBJ_BODY_INCREMENTAL
    The same indirect object (N G) is defined more than once with different body bytes. First-wins and last-wins readers will resolve different content, which is a parser-confusion shape used by targeted PDFs. Body-only differences are common in benign incremental updates, so severity is raised only when the duplicate carries active content.
  • PDF differential parser failed info PDF_DIFFERENTIAL_PARSE_FAILED
    The cross-check parser (pdfminer.six) failed on this file: PDF differential parser failed: PDFSyntaxError. Static heuristics still ran and any of their findings above are valid; only the differential cross-check signal is missing.
  • 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.
  • 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/xdp/
    • http://www.xfa.org/schema/xfa-template/2.5/
    • http://www.xfa.org/schema/xfa-data/1.0/

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
stream_003_off0000034f.js
79f62368bdbf7ded6adbfe486aaee557cdddb0c6943d4dfb5512e8bc5f748890
decompressed-pdf-stream PDF FlateDecoded stream at offset 0x34F 61803 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact contains 1 long base64-like blob(s).