Malicious RTF — malware analysis report

Static analysis result for SHA-256 e302311eb0dab92a…

MALICIOUS

RTF

30.2 KB Created: 1999-10-15 11:09:00 First seen: 2021-06-17
MD5: e99c5eab852a5680335b2d6c8691416a SHA-1: 88b76e7285ca2b91ef590cb9a34ae80744b461c6 SHA-256: e302311eb0dab92af57156eb51e1c3995e050fa6ae1395f1361acc7bab9d73af
160 Risk Score

Malware Insights

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

The RTF file contains OLE object data that exploits CVE-2017-8570 via a composite moniker. This vulnerability is known to drop and execute a script, which is a common initial step for malware. The document body appears to be a legitimate contract amendment, suggesting a lure to entice the user to open the malicious RTF file.

Heuristics 4

  • 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.
  • OLE object data medium RTF_OBJDATA
    RTF contains 1 \objdata section(s) — embedded OLE objects

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off000017be.bin rtf-objdata-decoded RTF \objdata at offset 0x17BE 4146 bytes
SHA-256: a2f97a2d69a894e25a387b92b6e568a8b3262fe373ee3e76c44a86dec03eaa4f