Malicious RTF — malware analysis report

Static analysis result for SHA-256 52bb459e808ca4ba…

MALICIOUS

RTF

152.7 KB Created: 2019-01-20 14:19:00 First seen: 2019-12-09
MD5: a3d73590a4d381c9cb214c2780725fce SHA-1: ea0f4a75243d630a5504fb41d0d9c270cf1d0ff9 SHA-256: 52bb459e808ca4ba702f8a35447e8a0eb26253fe0c407004d45231ab34794669
202 Risk Score

Malware Insights

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

The RTF file contains multiple OLE objects and triggers heuristics for Equation Editor and OLE activation, specifically indicating exploitation of CVE-2017-8759. This vulnerability allows for arbitrary code execution when the OLE object is activated, likely leading to the download and execution of a secondary payload. The presence of shellcode API strings in an extracted artifact further supports this conclusion.

Heuristics 6

  • 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
  • CVE-2017-8759 — MSXML SAX OLE activation critical CVE likely CVE_2017_8759
    RTF contains a hex-encoded OLE1 object for Msxml2.SAXXMLReader.6.0 followed by an embedded OLE compound document, and the document requests OLE activation. This matches the RTF staging shape used for CVE-2017-8759 SOAP/WSDL parser code injection.
  • \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 3 \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.
  • 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 3

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00017fd8.bin rtf-objdata-decoded RTF \objdata at offset 0x17FD8 8592 bytes
SHA-256: 67ff0449c56810ed91342d38f4bcc93b13e25946a55d6fed92fc2708e3e82c64
objdata_01_off0001c3a8.bin rtf-objdata-decoded RTF \objdata at offset 0x1C3A8 6841 bytes
SHA-256: 4ae82c1a309daeb1f275c17cac194a77ad74999b4c0ff1a8f16ca57c4f14dcfb
objdata_02_off0001fcc8.bin rtf-objdata-decoded RTF \objdata at offset 0x1FCC8 12923 bytes
SHA-256: 194c58e36596f842229a30e52fcf1b348a8170f59d766107e10bbbc3fbe59ff6
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Static shellcode analysis found candidate code region(s). Indicators: SC_STR_LOADLIBRARY, SC_STR_URLDOWNLOAD, SC_PEB_ACCESS Static shellcode analysis recovered API/import strings: LoadLibraryW, GetProcAddress, URLDownloadToFileW, ExitProcess

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