Malicious RTF — malware analysis report

Static analysis result for SHA-256 253d732012dd416d…

MALICIOUS

RTF

498.2 KB First seen: 2024-06-06
MD5: da2543ed3a6567896c950bfeb597814b SHA-1: 2421686c3e7bfff7544f0c911bc0310dee19c763 SHA-256: 253d732012dd416def18ed352ede88272a0ed42d2e1d3ca27ad9b3c4bcb59af0
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 file containing an embedded OLE object, which is a known method for delivering malicious content. The document body provides a lure to enable editing, a common technique to bypass security measures and execute embedded payloads. The presence of OLE object data and the instruction to enable editing strongly suggest a dropper or exploit delivery mechanism.

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_off00015ea0.bin
bb8231a373a80baca8140cbfa3cdeeaae5096b875e2214efdf262cab32f8a6a4
rtf-objdata-decoded RTF \objdata at offset 0x15EA0 1926 bytes