Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 4db55b2df58083e7…

MALICIOUS

RTF / .DOC

1011.6 KB
MD5: 4d6c7b93c085f50060e99dba63ef5e27 SHA-1: f67de698fd8eb036b8e83211880d1c449fe6f7e2 SHA-256: 4db55b2df58083e75c9471d2b79e1f9edf9491f423313b4e125349fed3507227
140 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 embedded OLE objects with excessive hex-encoded data, a common technique for hiding malicious payloads. The document body explicitly instructs the user to 'Enable editing' and mentions financial statements, acting as a lure. The presence of OLE object data and the enable editing lure strongly suggest the document is designed to download and execute a secondary payload.

Heuristics 5

  • \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.
  • Large hex data blocks in OLE object high RTF_EXCESSIVE_HEX
    RTF contains ~1012KB of hex-encoded data inside \objdata sections — may hide a payload
  • OLE object data medium RTF_OBJDATA
    RTF contains 1 \objdata section(s) — embedded OLE objects
  • Embedded OLE object medium RTF_OBJEMB
    RTF contains \objemb — embedded OLE object
  • 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_off000057bb.bin
6e7cce682e8b1134e9bfff784284e7329fc03292c4056fd32b3946ce710a9913
rtf-objdata-decoded RTF \objdata at offset 0x57BB 4208 bytes