Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 6fd1096080d1b5db…

MALICIOUS

RTF / .DOC

76.3 KB
MD5: 693f33fd0dbbbaca5cfc3f85bacf7324 SHA-1: d931b89ca416809a1b1c8c9d03bc743fe64eb89a SHA-256: 6fd1096080d1b5db1306ebe7a393b290fa19348b23c1c4085250218225e5de00
100 Risk Score

Malware Insights

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

The RTF document contains OLE object data and triggers an automatic update, indicating it's designed to exploit OLE object activation for code execution. The presence of `RTF_OBJAUTLINK` and `RTF_OBJUPDATE` heuristics strongly suggests this mechanism. The embedded OLE object, `objdata_00_off00000e21.bin`, is the primary artifact facilitating this exploit, likely serving as a dropper for further malicious activity.

Heuristics 3

  • 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 1 \objdata section(s) — embedded OLE objects

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00000e21.bin
7d20d9fe6eb83d7bf4394f700fb3c8e031fb3dbf07cdc0e3fb400d7574981ddc
rtf-objdata-decoded RTF \objdata at offset 0xE21 4253 bytes