Malicious RTF — malware analysis report

Static analysis result for SHA-256 25d719ac61230ec6…

MALICIOUS

RTF

1.12 MB Created: 2019-07-29 First seen: 2020-02-04
MD5: 8a294cf9b4995325c8d51f3a64f09ad9 SHA-1: 5cd4bc0f97747169e33aac2d4510b6a46fd206a5 SHA-256: 25d719ac61230ec6dcd6e2191a004475dd370ff939138f59d8306b220f1fa2a3
262 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution T1566.001 Spearphishing Attachment

The RTF file contains embedded OLE objects with excessive hex data, strongly indicating a hidden payload. The critical finding of CVE-2017-8759 suggests this file is designed to exploit that vulnerability for client execution. The presence of VBA auto-execution terms further supports the likelihood of a malicious macro-driven payload being dropped.

Heuristics 8

  • CVE-2017-8759 — MSXML SAX OLE activation critical CVE likely CVE_2017_8759
    RTF contains a hex-encoded OLE1 object for Msxml2.SAXXMLReader.6.0 followed by an embedded OLE compound document, and the document requests OLE activation. This matches the RTF staging shape used for CVE-2017-8759 SOAP/WSDL parser code injection.
  • Composite Moniker in RTF OLE object high CVE related RTF_COMPOSITE_MONIKER_RELATED
    RTF contains Composite Moniker CLSID in OLE object context, but no nearby scriptlet/SCT payload was confirmed. Treat as related moniker attack-surface evidence rather than proof of CVE-2017-8570 exploitation.
  • \objupdate forces OLE activation high RTF_OBJUPDATE
    RTF contains \objupdate — forces automatic OLE object instantiation when the document is opened, bypassing user interaction. Almost exclusively seen in Equation Editor exploit documents.
  • Large hex data blocks in OLE object high RTF_EXCESSIVE_HEX
    RTF contains ~1110KB of hex-encoded data inside \objdata sections — may hide a payload
  • Suspicious extracted artifact high 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.
  • OLE object data medium RTF_OBJDATA
    RTF contains 2 \objdata section(s) — embedded OLE objects
  • Embedded OLE object medium RTF_OBJEMB
    RTF contains \objemb — embedded OLE object
  • 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://schemas.microsoft.com/office/word/2003/wordml In RTF body

Extracted artifacts 2

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off000028f2.bin rtf-objdata-decoded RTF \objdata at offset 0x28F2 270382 bytes
SHA-256: 64cb684488289e13f81f58e186160f23dd36580f4d9026a4e1fff621803ab673
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved macro source contains an auto-exec entry point and execution/download terms.
objdata_01_off0008d249.bin rtf-objdata-decoded RTF \objdata at offset 0x8D249 270382 bytes
SHA-256: 99b78c708f6b0347b028f8c14928dae77a628b7fc31138929f27dbad3e8990ba
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved macro source contains an auto-exec entry point and execution/download terms.