Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 fc503eccd63710ce…

MALICIOUS

RTF / .DOC

19.8 KB
MD5: e887d94ae7f350fcb2d8d14674e7c562 SHA-1: f850c3229ef521b503426935b100533f66b3918e SHA-256: fc503eccd63710ce53fa93550f00dd177d5243639ec359619978a87ea46ca46f
100 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment T1204.002 Malicious File T1059.001 PowerShell

The sample is an RTF document containing embedded OLE objects, as indicated by the RTF_OBJDATA and RTF_OLE10NATIVE_STREAM heuristics. The RTF_OBJUPDATE heuristic suggests that these objects are designed to be activated, likely to exploit a vulnerability within Microsoft Office. The document body is heavily obfuscated and does not provide clear textual lures. No scripts were extracted from this sample. The primary attack vector appears to be the exploitation of OLE object handling within the RTF format.

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_off00001be8.bin
5bc5e3b155617a7c4722a24b5fb5d9d0e110e4c3f0216b8c9e8557a66ed93f46
rtf-objdata-decoded RTF \objdata at offset 0x1BE8 3644 bytes