Malicious RTF — malware analysis report

Static analysis result for SHA-256 3fa5812b96d6cafa…

MALICIOUS

RTF

736.6 KB Created: 2020-06-09 12:34:00
MD5: 534c00447ba7a9a34de759fca82bba03 SHA-1: 27a832c87b0b3e305788bb0c650e967c872b5df1 SHA-256: 3fa5812b96d6cafadd11fef3cad5fd31413906b19172b3d0357fe751e94c98a9
282 Risk Score

Malware Insights

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

The RTF file contains multiple indicators of exploitation, specifically referencing CVE-2017-8570 and CVE-2017-8759, which are known to facilitate arbitrary code execution. The presence of OLE object data and composite monikers strongly suggests that the file is designed to exploit these vulnerabilities to drop and execute a secondary payload. The document body content appears to be garbled or malformed, providing no clear user-facing lure.

Heuristics 8

  • 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.
  • 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 4 \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/w

Extracted artifacts 4

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off000132c1.bin
69cacba5797d82e67ff87b2dc9a8be13a91217de8ecc8d0753578b20d06869d3		 rtf-objdata-decoded RTF \objdata at offset 0x132C1 221081 bytes
objdata_01_off00019a70.bin
fb118cbde7d9eaf00c6270f1300159b51fe9fa71eaf44aa04f579253840658f0		 rtf-objdata-decoded RTF \objdata at offset 0x19A70 221054 bytes
objdata_02_off00089f21.bin
51ef705eef602ac6eb91c2063c8f50d4e54b5e051b60429031d41133bc7df645		 rtf-objdata-decoded RTF \objdata at offset 0x89F21 2632 bytes
objdata_03_off0008b4c4.bin
e8d4fe950caed6dcfde26f4b616825bbe11b93458425974b7d075167f675abf7		 rtf-objdata-decoded RTF \objdata at offset 0x8B4C4 12297 bytes

Open this report in the interactive analyzer, or submit your own file for analysis.