Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 be6975be76320ea5…

MALICIOUS

RTF / .DOC

9.2 KB First seen: 2022-04-21
MD5: f1fd6ca909cb2d9aab0dc9fa034f765e SHA-1: c771fcd4998c7dff9fe846d26a34005560e3dfb8 SHA-256: be6975be76320ea55c692d7c4bf0aeb466928db5c874ceb1e50feffc97bffd30
139 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment T1204.002 Malicious File

The sample is an RTF document that contains OLE object data, which is automatically linked and updated. This indicates the document is designed to exploit OLE activation mechanisms to trigger embedded malicious content. While no specific script was extracted, the heuristic firings strongly suggest a malicious OLE object is embedded, likely intended to download and execute a secondary payload or lead the user to a phishing site. The document body is heavily obfuscated and unreadable, providing no further clues.

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

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off0000106e.bin
38e28de50f9ae8ca5e74ad2f04c51cd34362ad7914b447bbf5360b0436d66760
rtf-objdata-decoded RTF \objdata at offset 0x106E 1593 bytes