Malicious RTF — malware analysis report

Static analysis result for SHA-256 9a4c952c9241a348…

MALICIOUS

RTF

139.9 KB Created: 2020-02-12 First seen: 2020-05-25
MD5: 50ef2beade37e48b130e9ca2d6f4eaf6 SHA-1: 31306e2fba0de9fb11a179ff431bf5e33905407b SHA-256: 9a4c952c9241a348bbbe54002d59f09c69338c3e901babc6963460ba46cf8be5
202 Risk Score

Malware Insights

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

The RTF file contains embedded OLE objects and uses \objupdate to force activation, indicating an attempt to exploit vulnerabilities. Specifically, the CVE-2017-8759 heuristic firing suggests exploitation of MSXML SAX OLE activation. The presence of shellcode API strings and a shellcode URL within an extracted artifact further supports the conclusion that this file is designed to download and execute a secondary payload. The document body content is heavily obfuscated and appears to be a lure, but the technical indicators are clear.

Heuristics 6

  • 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.
  • Suspicious extracted artifact critical 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.
  • \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
  • 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.mic In RTF body
    • http://bit.ly/2uLwQhLIn RTF body

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off0001e022.bin rtf-objdata-decoded RTF \objdata at offset 0x1E022 1438 bytes
SHA-256: 1d2589ad447e3aff33d65e6a3ea30927971daa10f37c48ae05b8681144a2e287
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Static shellcode analysis recovered URL(s): http://bit.ly/2uLwQhL 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: LoadLibraryA, GetProcAddress, URLDownloadToFileA, ExitProcess

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