Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 838bb771d05c0436…

MALICIOUS

RTF / .DOC

70.6 KB
MD5: 9c90d014b3fe6c06dc4bfccd05eeb09b SHA-1: 2535e0244a7212b5e67671051a2b6e2f9077b739 SHA-256: 838bb771d05c0436b9e37bc35ccdcf80d49b2b4d8aa78fa6627b331307fc6f73
100 Risk Score

Malware Insights

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

The RTF document contains embedded OLE objects, indicated by RTF_OBJDATA and RTF_OLE10NATIVE_STREAM heuristics. The RTF_OBJUPDATE heuristic at offset 0x1F75 suggests that these embedded objects are designed to be activated automatically upon opening the document. This technique is commonly used to deliver and execute malicious payloads, such as malware droppers or exploit code, by leveraging the OLE object activation mechanism.

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_off00001fb2.bin
2e69e237f53141fff3d0e8f4bddd415780b5743389ad9c1de18477feb810f993
rtf-objdata-decoded RTF \objdata at offset 0x1FB2 3658 bytes