Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 6599a145f5a720ca…

MALICIOUS

RTF / .DOC

103.7 KB
MD5: bd5c87df0f1b2062fe8f3f5529c8145d SHA-1: 194dce412fdbf6b7f893abdce9d1b4a6dd7f48fb SHA-256: 6599a145f5a720caffb33fae82696065404d7bdc2ed16b2df9cae5c3174b603e
100 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment T1203 Exploitation for Client Execution

The RTF document contains OLE object data with an \objupdate directive, indicating an attempt to automatically activate embedded objects. This is a common technique for exploiting vulnerabilities or delivering secondary payloads. The decoded OLE object stream, named 'objdata_00_off000004b2.bin', is the primary indicator of malicious activity. No document body or script content was available for further analysis.

Heuristics 3

  • 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

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off000004b2.bin
e379ed48205e4d1715c19a3df305be57fdcac17656c878323d78de736239f1a0
rtf-objdata-decoded RTF \objdata at offset 0x4B2 3671 bytes