Malicious RTF — malware analysis report

Static analysis result for SHA-256 0c048b73924edd5e…

MALICIOUS

RTF

14.2 KB First seen: 2019-04-18
MD5: 322cb2da6b6883b81bb12b8609601ac3 SHA-1: 2e1314465ea7d7a26bfd7d88802d1ad0b80b07fd SHA-256: 0c048b73924edd5e8d0183e3576726e802fd7b0b89dd0b04dab3f44d8ac2b957
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_off00000800.bin rtf-objdata-decoded RTF \objdata at offset 0x800 4138 bytes
SHA-256: 194e754a2dac61f69a7842d31718534335b7e1feea8cdf727547f6646fb4f2b9