Malicious RTF — malware analysis report

Static analysis result for SHA-256 38368101b46675d7…

MALICIOUS

RTF

327.5 KB First seen: 2021-07-07
MD5: 392d4112b74a45586d0f1744324fbeb4 SHA-1: 99af98dce8252b66ea01b610cf56a6c7eb54d5dd SHA-256: 38368101b46675d7db77442650634c6fac06e29338d2910cdca25f09a350bdd3
260 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution

The RTF file contains multiple indicators of exploitation, specifically related to CVE-2017-8570 and the use of composite monikers within OLE objects. This vulnerability is known to be used for dropping and executing script files, which is strongly suggested by the 'EXTRACTED_FILE_STATIC_TRIAGE' heuristic firing on shellcode command strings and extracted files. The embedded OLE objects and objdata sections are the likely vectors for this exploit.

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.
  • 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.
  • Suspicious extracted artifact high 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.
  • 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

Extracted artifacts 4

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off000007da.bin rtf-objdata-decoded RTF \objdata at offset 0x7DA 56429 bytes
SHA-256: 43dcf3ea7435a1ad067934479f2dbd123181479b6f44ff2f95cb8ca900c89e71
objdata_01_off00006f89.bin rtf-objdata-decoded RTF \objdata at offset 0x6F89 56402 bytes
SHA-256: d0bb441645731c1c176b720e0f776c9442a97f21fcd0fb516e43887fe5fbc710
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Static shellcode analysis recovered command string(s): WScript.Shell"")")
objdata_02_off00023a6e.bin rtf-objdata-decoded RTF \objdata at offset 0x23A6E 2632 bytes
SHA-256: a8e170497da15decc11753d202c99c86f7a7ffd2d52481e6b9c79a5403675379
objdata_03_off00025011.bin rtf-objdata-decoded RTF \objdata at offset 0x25011 12297 bytes
SHA-256: e8d4fe950caed6dcfde26f4b616825bbe11b93458425974b7d075167f675abf7