Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 b561883be6932ea3…

MALICIOUS

RTF / .DOC

16.8 KB First seen: 2022-08-25
MD5: 995f4b5c4c071b41420b5515fb2d4641 SHA-1: fe0f86067044cc7fa31a3703e96fbe2dd0561872 SHA-256: b561883be6932ea3ce072e3536a3165dda08b318b02d039eb6561e152076f020
120 Risk Score

Malware Insights

MITRE ATT&CK
T1204 Malicious File Execution T1204.002 User Execution: Malicious File T1566 Phishing T1566.001 Spearphishing Attachment T1059.005 Visual Basic

The RTF document contains OLE object data and uses \objupdate to force OLE activation, indicating an attempt to execute embedded content. The document body explicitly prompts the user to 'enable editing to view in readable format', a common social engineering tactic to bypass macro security. No scripts were extracted, but the heuristics strongly suggest a macro-based or OLE-based execution lure.

Heuristics 4

  • Ole10Native stream in RTF OLE object high CVE related RTF_OLE10NATIVE_STREAM
    RTF contains an embedded OLE object with an Ole10Native stream. This is a strong payload-container signal and is related to Word/OLE exploit delivery, but it is not specific enough on its own to assign a CVE.
  • \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
  • Macro/content-enable lure medium SE_ENABLE_LURE
    Document instructs the user to enable macros or editing — a common technique used by malware droppers to bypass Office macro security settings

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00000e7c.bin
81a9828228b8f1cbc6465207a9fd9bf64a5e0f3c5301c1dc07307eefa9f0b374
rtf-objdata-decoded RTF \objdata at offset 0xE7C 4271 bytes