Malicious RTF — malware analysis report

Static analysis result for SHA-256 548af060c56ad191…

MALICIOUS

RTF

510.8 KB First seen: 2019-04-18
MD5: 4357f1d049b8b8d51b0233e8a8684552 SHA-1: 9e77f7f89fa268624f7a582c97237f8845606268 SHA-256: 548af060c56ad191f5db7c5aa10db84ce79bc81bd741678a6227e4b07c16941d
120 Risk Score

Malware Insights

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

The RTF file contains an embedded OLE object with OBJDATA and OBJUPDATE directives, strongly indicating an attempt to exploit a client-side vulnerability for code execution. The presence of a shellcode candidate region within the decoded OLE object further supports this. While the specific exploit is not detailed, the mechanism points to a malicious document delivered via spearphishing.

Heuristics 4

  • 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
  • Suspicious extracted artifact medium EXTRACTED_FILE_STATIC_TRIAGE
    One or more files extracted from inside this sample matched static suspicious-content checks such as script obfuscation, encoded payload blobs, packed data, or execution/download terms.

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off0000117f.bin rtf-objdata-decoded RTF \objdata at offset 0x117F 4145 bytes
SHA-256: b6878340d115db17c3ee06fe287544beeca868f6ecad15a7cc8434c1beadf204
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Static shellcode analysis found candidate code region(s). Indicators: SC_GETPC_CALL