Malicious RTF — malware analysis report

Static analysis result for SHA-256 78c4b05bd6b78968…

MALICIOUS

RTF

618.2 KB First seen: 2024-07-02
MD5: 8f0ce9f8a543b36e93a8a5c32e4612e5 SHA-1: 9f39b3dec9ee18ea1cb337d013fe7b3e65defabd SHA-256: 78c4b05bd6b78968d24e4d83072453f91c7596d04123e413fefc4a03be8fd4bb
80 Risk Score

Malware Insights

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

The sample is an RTF document that contains OLE object data and an instruction to enable editing, which is a common lure for macro-based malware delivery. The heuristic SE_ENABLE_LURE explicitly indicates that the document instructs the user to enable macros or editing, a technique used by malware droppers. The RTF_OBJUPDATE heuristic further suggests that the embedded OLE object is designed to be activated, likely to execute a malicious payload.

Heuristics 3

  • \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
  • 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_off0002bd3b.bin
3b904337bdc04dc354b382d34d03055accb8f1c01c4004cf2e17c20e56ef7e94
rtf-objdata-decoded RTF \objdata at offset 0x2BD3B 1988 bytes