Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 a00cd0bbb6988a01…

MALICIOUS

RTF / .DOC

1.11 MB Created: 2023-01-23 21:10:00 First seen: 2023-01-24
MD5: bb16645d4831c9a32eb93c853f79d5c3 SHA-1: cf69ad7c4cfb31f358f0f79cd8bbaf7855e807f8 SHA-256: a00cd0bbb6988a01d2e59775ad46314a1065070bc0f20e3d45ec57191cdc1350
310 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment T1204.002 User Execution: Malicious File T1059.003 Windows Command Shell T1204.001 User Execution: Malicious Link

The file is an RTF document exhibiting multiple critical heuristics related to CVE-2017-8570 and CVE-2017-8759, indicating exploitation of vulnerabilities to execute embedded content. The document body presents itself as a financial transfer advice, a common lure for advance-fee scams. The presence of embedded OLE objects and extracted artifacts suggests these are likely payloads or scripts intended for execution, potentially downloading further malicious content.

Heuristics 10

  • Composite Moniker — CVE-2017-8570 (drops SCT script) critical CVE related CVE_2017_8570
    RTF \objdata decodes to OLE data containing the Composite Moniker — CVE-2017-8570 (drops SCT script) CLSID — the vulnerable control/moniker is embedded directly in the document's object stream, the delivery shape of this exploit. RTF objects auto-render when Word opens the file.
  • 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.
  • Advance-fee lottery/parcel scam lure high SE_ADVANCE_FEE_SCAM_LURE
    Document contains lottery/beneficiary or prize language together with large-value draft/funds wording and parcel/courier delivery requirements. This is a classic advance-fee fraud document shape.
  • OLE object data medium RTF_OBJDATA
    RTF contains 3 \objdata section(s) — embedded OLE objects
  • Embedded OLE object medium RTF_OBJEMB
    RTF contains \objemb — embedded OLE object
  • Suspicious extracted artifact medium 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.
  • Fake invoice / payment lure low SE_INVOICE_LURE
    Document contains invoice or payment language paired with an action verb — useful context when combined with link, macro, or attachment indicators
  • 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

Extracted artifacts 3

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off000dc1b0.bin
6b2272659b4e3873e12c621231722c5e2dd5ad93592e439daceb5583321c8120
rtf-objdata-decoded RTF \objdata at offset 0xDC1B0 34283 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact contains 1 shell/COM execution token(s).
objdata_01_off000ed8da.bin
24fedef2d4fe5e3d6666fae2543850c54134511ad6be8583d5aa0438ef699c5d
rtf-objdata-decoded RTF \objdata at offset 0xED8DA 2632 bytes
objdata_02_off000eee7d.bin
142dc43284d9abe994719f8fb67bc4c04bfc3f07528a1a66b0bad7e552ee8e78
rtf-objdata-decoded RTF \objdata at offset 0xEEE7D 12297 bytes