Malicious RTF — malware analysis report

Static analysis result for SHA-256 fed68f883596c874…

MALICIOUS

RTF

18.9 KB First seen: 2018-07-14
MD5: 48e9021cb801fefb655b6b16acd4fffb SHA-1: 6acba4695e4102158df0b08c00b37cc0e1610278 SHA-256: fed68f883596c87453e7fe846d1b29356fcfadf2e9d733a478cdd7fe3d80c330
100 Risk Score

Malware Insights

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

The RTF file contains OLE object data and an \objupdate directive, indicating an attempt to exploit a vulnerability related to OLE object activation. The high entropy of the decoded OLE object suggests it contains executable code. This pattern is commonly used to achieve arbitrary code execution upon opening the document, often as part of a spearphishing campaign to deliver further malware.

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_off000014be.bin rtf-objdata-decoded RTF \objdata at offset 0x14BE 4668 bytes
SHA-256: ac9d55eaa7bc530298d146ec679370f6e02567125b706f2fc9db1a7128619eb8