Malicious RTF — malware analysis report

Static analysis result for SHA-256 522197653fe54536…

MALICIOUS

RTF

1.20 MB First seen: 2019-12-09
MD5: d1a2b3e3f926b8aed16ac294c802432d SHA-1: 2c8814071565f7e79de6a8d1e2b276ed0f13945c SHA-256: 522197653fe54536745620baf58aabf227087a756dc6c6f4d50e787bac53c5bb
222 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution

The RTF file contains multiple OLE objects and exhibits characteristics of CVE-2017-8570, specifically the use of a composite moniker. This vulnerability is known to be used for dropping and executing script files, likely SCT files, which would then proceed to download and run a second-stage payload. The presence of large amounts of hex-encoded data within OLE objects further suggests the embedding of malicious content.

Heuristics 7

  • 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.
  • \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 ~1073KB of hex-encoded data inside \objdata sections — may hide a payload
  • OLE object data medium RTF_OBJDATA
    RTF contains 7 \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.openxmlformats.org/drawingml/2006/main In RTF body

Extracted artifacts 7

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00000025.bin rtf-objdata-decoded RTF \objdata at offset 0x25 205 bytes
SHA-256: 75a725fc96463ea024899f12597b26031b1a5d84ddd2de407d47914073b3db59
objdata_01_off000001ea.bin rtf-objdata-decoded RTF \objdata at offset 0x1EA 536779 bytes
SHA-256: 433c87bb062b6a540d8147dd1feb1f935d957e20e4cab362220d768d36835bd5
objdata_02_off001134e8.bin rtf-objdata-decoded RTF \objdata at offset 0x1134E8 1068 bytes
SHA-256: 2b28d78ceb2a564ae30f2b6865926b068f3f920a373c2e3fc4cb865091eddd89
objdata_03_off00113d73.bin rtf-objdata-decoded RTF \objdata at offset 0x113D73 62668 bytes
SHA-256: 634ac6bbb761f67d8cc8aaeaf4adb5e9fbe1c975a7d5bbd90da116c2a84783d0
objdata_04_off0013273d.bin rtf-objdata-decoded RTF \objdata at offset 0x13273D 369 bytes
SHA-256: 3c0b4878e98d51d984a06b9ba36e54869ecd67e41f335730fced4ca28976d877
objdata_05_off00132a53.bin rtf-objdata-decoded RTF \objdata at offset 0x132A53 890 bytes
SHA-256: 21dcdf875b1972c61c0e8c2c2123f9a95c8f29fb4a2cf8bf52511b328881de8e
objdata_06_off001331ae.bin rtf-objdata-decoded RTF \objdata at offset 0x1331AE 2633 bytes
SHA-256: 27c6d10cfe7974ebf40c1200cc005f9878cc37b7d49ece9cbc396d700c38918a

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