Malicious RTF — malware analysis report

Static analysis result for SHA-256 22062b6bcda194e3…

MALICIOUS

RTF

350.9 KB Created: 2018-04-05 10:32:00 First seen: 2019-01-20
MD5: f5919f70371520645f4765bcc385bef4 SHA-1: c2939256a7483145cf4dbd58262c80d71472cf67 SHA-256: 22062b6bcda194e3734285fed6b2de341c694c52a8f60c9f389f880cefab7644
282 Risk Score

Malware Insights

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

The RTF file contains an embedded OLE object that exploits the Equation Editor vulnerability (CVE-2017-11882). This exploit is designed to execute a secondary payload, indicated by the presence of shellcode candidate regions and a suspicious URL. The document body, discussing Hajj pilgrimage, is a lure to trick the user into opening the malicious content.

Heuristics 8

  • Equation Editor CLSID critical CVE likely RTF_EQUATION_EDITOR
    Equation Editor OLE CLSID found inside an OLE object — exploited by CVE-2017-11882 / CVE-2018-0802 / CVE-2018-0798
  • Equation Editor OLE1 native payload — CVE-2017-11882 related critical CVE related CVE_2017_11882_RELATED
    RTF decodes to an OLE1 Equation.3 embedded object whose native data is large and payload-like, and \objupdate requests automatic activation. This is the delivery shape used by Equation Editor RCE documents such as CVE-2017-11882/CVE-2018-0802, but the malformed MTEF record needed for exact attribution was not recovered.
  • ClamAV: Rtf.Dropper.Agent-7084627-0 critical CLAMAV_DETECTION
    ClamAV detected this file as malware: Rtf.Dropper.Agent-7084627-0
  • \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://www.google.com.d-dns.co/includes/686a0ea5/-1/1219/02237f8b/final.hta In RTF body
    • http://schemas.microsoft.com/office/word/2003/wordmlIn RTF body

Extracted artifacts 2

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00052ef4.bin rtf-objdata-decoded RTF \objdata at offset 0x52EF4 9781 bytes
SHA-256: 8d641fba45c37e38fe7a8aaa9fb69cf12d4f858bd2a40626db30d1edc4d049a9
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Static shellcode analysis found candidate code region(s). Indicators: SC_GETPC_CALL, NOP sled
objdata_01_off00052f07.bin rtf-objdata-decoded RTF \objdata at offset 0x52F07 35 bytes
SHA-256: e0f28ce3138172e7f0d29be00b7cfbd17d822420ce29f7663ca1be8ad04df92d

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