Malicious RTF — malware analysis report

Static analysis result for SHA-256 c450af1f8eccf8b3…

MALICIOUS

RTF

311.6 KB First seen: 2018-05-18
MD5: eb1cb683a5e6c6f0021b96df93bd87f3 SHA-1: 3dbeebcd048a835d6d0894f9fd144c28f989c5c5 SHA-256: c450af1f8eccf8b30e1fccef89f4d45c5aacad8ba05c76d739124719113f04ad
100 Risk Score

Malware Insights

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

The RTF file contains embedded OLE objects and uses the \objupdate directive, indicating an attempt to trigger the execution of embedded content. The document body, though partially garbled, contains references to 'Pomfe.co' and appears to be a lure for a scam or phishing attempt. The embedded OLE object is likely a secondary payload designed to be executed upon activation.

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_off0000022d.bin rtf-objdata-decoded RTF \objdata at offset 0x22D 41620 bytes
SHA-256: ecae9867c42db3faf59e696c414b87af004e70e8b0e5586a6e3abc6c40823b0f