Malicious RTF — malware analysis report

Static analysis result for SHA-256 ed8ed2adbca31740…

MALICIOUS

RTF

447.2 KB Created: 2018-12-12 16:35:00 Authoring application: Microsoft Word 11.0.5604 First seen: 2019-08-04
MD5: 91f0516e3c1810484d99fff59e2f1b2c SHA-1: 76ffca11d4c78ee4878434ca42b5c11e4add2d16 SHA-256: ed8ed2adbca317401430800ccffffcbdc567f9771d85845904c507353b6d9322
102 Risk Score

Malware Insights

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

The RTF document contains embedded OLE objects, with one specifically triggering an ".objupdate" command, indicating an attempt to execute embedded content. Heuristics also flagged suspicious shellcode candidate regions within an extracted OLE object. While the embedded URLs were confirmed benign, the overall structure and heuristic firings strongly suggest this file is designed to exploit a client vulnerability and likely download a secondary payload, consistent with a spearphishing attachment.

Heuristics 5

  • \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 2 \objdata section(s) — embedded OLE objects
  • Embedded OLE object medium RTF_OBJEMB
    RTF contains \objemb — embedded OLE object
  • 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.
  • Embedded URL info EMBEDDED_URL
    One or more URLs were extracted from the document. The URL itself is not a detection — see the per-URL labels for which channel (macro, JS, link annotation, document body, ...) reached each URL.
    URL http://schemas.microsoft.com/office/word/2003/wordml In RTF body
    • http://bit.ly/2LRWyVEIn RTF body

Extracted artifacts 2

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off000416c3.bin rtf-objdata-decoded RTF \objdata at offset 0x416C3 8899 bytes
SHA-256: 4c56eb00213a01c2c8e91cf83b8e7eec7152b51e5879dc114197f0cd017bbb26
objdata_01_off000576a0.bin rtf-objdata-decoded RTF \objdata at offset 0x576A0 12188 bytes
SHA-256: 0b66170dc882720d68e3c5ea5c1c72cf71041b79407e24a14b2d0e4744cda224
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Static shellcode analysis found candidate code region(s). Indicators: SC_GETPC_CALL, SC_PEB_ACCESS