Malicious RTF — malware analysis report

Static analysis result for SHA-256 b1addd1dc0ecd57d…

MALICIOUS

RTF

343.8 KB Authoring application: Riched20 6.3.9600 First seen: 2021-09-24
MD5: 192e7a8e67e9f7f007a1f9ab68358230 SHA-1: 5a6d66e41cbbc6c926e45d50198532ee3a2a777c SHA-256: b1addd1dc0ecd57da6622b61faf13cfb4c336a7a92f703e83d28b9e6b9797b10
220 Risk Score

Malware Insights

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

This RTF document was flagged as malicious. Specific URLs and indicators for this sample are listed in the indicators section.

Heuristics 6

  • 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.
  • 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.
  • Automatically linked OLE object high RTF_OBJAUTLINK
    RTF contains \objautlink — an automatically linked OLE object surface that can be updated or activated when Word opens the document.
  • \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.
  • 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

Extracted artifacts 3

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off000013a6.bin rtf-objdata-decoded RTF \objdata at offset 0x13A6 75732 bytes
SHA-256: f4f97d3daedbfea27b71dfa078d30d4e15db2f1eed0ffef99c4d07ecb4b99be6
objdata_01_off00027b99.bin rtf-objdata-decoded RTF \objdata at offset 0x27B99 2632 bytes
SHA-256: f4c761490fd63fc4aa791746a9a2b588dafd9e2c764f57f0c85377b99ef07062
objdata_02_off0002913c.bin rtf-objdata-decoded RTF \objdata at offset 0x2913C 12297 bytes
SHA-256: 44deae4627fee3c44f54d5bd10477ec2e17f4c08135f08e2417832e36d10d037