Malicious RTF — malware analysis report

Static analysis result for SHA-256 b56d5c3e60c20fab…

MALICIOUS

RTF

14.2 KB First seen: 2019-05-16
MD5: d0653ac4ce0caaa3fd474b3fe7185a22 SHA-1: 29228a6b63768eeeac82e2936f1a310f98791f4d SHA-256: b56d5c3e60c20fab0794e88a61c081d2a2ef6d7cb730d7456fbfeb3a149e43f3
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_off00000801.bin rtf-objdata-decoded RTF \objdata at offset 0x801 4156 bytes
SHA-256: 5506a8566f477032a9ca37ee03f85a75d1b039baef9f08b9d8f61214254cdf12