Malicious RTF — malware analysis report

Static analysis result for SHA-256 ccbe2c2363442b15…

MALICIOUS

RTF

14.1 KB First seen: 2020-02-04
MD5: b56e897721afdd0e14a98163c5ed813c SHA-1: d05dbb1e870938d33c5a265642cc0230693910fe SHA-256: ccbe2c2363442b153aec5ec8894beb275f4daabe5ce65ce48ad05eaed9340fee
100 Risk Score

Malware Insights

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

The RTF document contains embedded OLE object data, indicated by RTF_OBJDATA and RTF_OLE10NATIVE_STREAM heuristics. The RTF_OBJUPDATE heuristic suggests that the embedded object is designed to be activated automatically, likely leading to the execution of a malicious payload. No specific family could be identified, and no further IOCs were extracted.

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 1 \objdata section(s) — embedded OLE objects

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00000802.bin rtf-objdata-decoded RTF \objdata at offset 0x802 4135 bytes
SHA-256: 76c62c581a82826fa13a2dfd4ffb11d2e073d2e73c800151a0d4a3932d87ea96