Malicious RTF — malware analysis report

Static analysis result for SHA-256 06253dba4ac17a04…

MALICIOUS

RTF

452.3 KB Created: 2018-08-17 15:43:00 First seen: 2019-05-10
MD5: ececedd388e9d99530089b3865d84c74 SHA-1: dfc287e72eb2abe0747d9a887e50cfc102cd1838 SHA-256: 06253dba4ac17a04a5e948b397fd991431ca8cd006117af0022ce9d5aef8363f
122 Risk Score

Malware Insights

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

The RTF file contains multiple OLE objects with embedded data, and the ".objupdate" directive indicates an attempt to trigger OLE activation. This strongly suggests the file is designed to exploit vulnerabilities related to OLE object handling for client-side execution. The presence of a benign URL does not detract from the malicious indicators.

Heuristics 5

  • Composite Moniker in RTF OLE object high CVE related RTF_COMPOSITE_MONIKER_RELATED
    RTF contains Composite Moniker CLSID in OLE object context, but no nearby scriptlet/SCT payload was confirmed. Treat as related moniker attack-surface evidence rather than proof of CVE-2017-8570 exploitation.
  • \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 5 \objdata section(s) — embedded OLE objects
  • Embedded OLE object medium RTF_OBJEMB
    RTF contains \objemb — embedded OLE object
  • 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

Extracted artifacts 5

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off000039f4.bin rtf-objdata-decoded RTF \objdata at offset 0x39F4 31291 bytes
SHA-256: 7ac73dd89967379a3705f6a3bffd82bf2a0ee82b7f109e8d85073fa257557a4c
objdata_01_off00018688.bin rtf-objdata-decoded RTF \objdata at offset 0x18688 31291 bytes
SHA-256: 47013feee1cdcff149bd9f82f02d0e9346d60b4d9db33894a2841d4a7ec68f5c
objdata_02_off0002d31e.bin rtf-objdata-decoded RTF \objdata at offset 0x2D31E 31291 bytes
SHA-256: 46892d2da75faad4a9abd9a21447c756bfc79ea87b291b8ab242aa6ac2e2fe4d
objdata_03_off00041fb4.bin rtf-objdata-decoded RTF \objdata at offset 0x41FB4 31291 bytes
SHA-256: e7e43133f1a40f39dfcd4640799b79bc51ba7737b41f610f44efdccd9874110b
objdata_04_off00056c4a.bin rtf-objdata-decoded RTF \objdata at offset 0x56C4A 31291 bytes
SHA-256: fecfd815720f28468fb31e2f70c1a87e25c5cdd9cfb55fe96c494526407edfce

Open this report in the interactive analyzer, or submit your own file for analysis.