Malicious RTF — malware analysis report

Static analysis result for SHA-256 582f283e1021cab7…

MALICIOUS

RTF

29.7 KB
MD5: 01f053f8ca4c1cb73588f3c0e380d553 SHA-1: c17c31bd86aadca0f74320f12c4b0f31cd83ee8e SHA-256: 582f283e1021cab7727f79c7cc6e759bae0f84f32b6af89f0108ba2dcb382b74
100 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment T1204.002 Malicious File T1027 Obfuscated Files or Information

The RTF file contains OLE object data and uses \objupdate to force activation, indicating a likely exploit. The embedded OLE object, decoded from the Ole10Native stream, is 4704 bytes and has high entropy, suggesting it's a packed or obfuscated payload. The presence of these indicators strongly suggests the file is designed to deliver a secondary malicious payload upon opening.

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_off0000209e.bin
46150c0efa7ae828b03cb6daee091c87bc6aa155286e1eba75b4b394182f98f8
rtf-objdata-decoded RTF \objdata at offset 0x209E 4704 bytes