Malicious RTF — malware analysis report

Static analysis result for SHA-256 263f6d102bd67cdb…

MALICIOUS

RTF

516.2 KB First seen: 2024-06-13
MD5: 118072abaca518e6ece93908a9fee1f4 SHA-1: b1983c6c49c904a4d5e1f2fbba90bf2510da544b SHA-256: 263f6d102bd67cdbc4617b0db0ee891fb53d73128b9c88d0558b10c7527e6b46
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 RTF document contains OLE object data and an \objupdate directive, indicating it is designed to embed and activate OLE objects. The 'SE_ENABLE_LURE' heuristic confirms the document instructs the user to enable editing and macros, a common tactic for malware droppers. The content discusses financial audits to appear legitimate, masking the malicious intent.

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_off00016e0b.bin
99102cc2cc13c0ec4e5cb77760fc16eac059e57593d838f791f59e1f60315a28
rtf-objdata-decoded RTF \objdata at offset 0x16E0B 1841 bytes