Malicious Office (OLE) / .XLSX — malware analysis report

Static analysis result for SHA-256 55ea07bbd700488f…

MALICIOUS

Office (OLE) / .XLSX

1.26 MB Created: 2006-09-16 00:00:00 Authoring application: Microsoft Excel
MD5: 120ea9ee19eb0add09beff0a8eb55bb0 SHA-1: 5687e15f91cfea31ffa82da06278a6239f1f1939 SHA-256: 55ea07bbd700488fd6330d289f210b2da119401a9e27009472d1afec2f6c6339
68 Risk Score

Malware Insights

MITRE ATT&CK
T1204.002 Malicious File T1059.005 Visual Basic

The sample leverages the CVE-2017-0199 vulnerability, which is a known method for remote code execution. The heuristic firing indicates that the OLE object contains a URL moniker pointing to 'https://st3.pro/s6zpy2l?&galleon=skinny&recess=calm&decimal=uptight&conifer=yielding&susan'. This URL is likely used to download and execute a secondary payload. Although VBA macros were present, they contained no executable statements, suggesting the exploit is directly within the OLE structure.

Heuristics 2

  • OLE2Link / URL Moniker → remote loader — CVE-2017-0199 critical CVE likely CVE_2017_0199
    Document contains an embedded OLE link object whose URL Moniker points to a remote URL. When the host file is opened, Office follows the link, downloads the URL, and processes the response based on its Content-Type (HTA -> mshta.exe, RTF → Word, etc.) — the documented CVE-2017-0199 primitive. The URL extension is not a reliable filter; servers can return different payloads to Office's user agent.
  • VBA project contains no executable statements low OLE_VBA_MACROS
    Document contains a VBA project, but extracted modules only contain attributes/options/comments and no executable statements.

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
macros.bas
7f506327609c082af1cd37dde23bc2c71a000f7d1ef530b6abb66775040a7673
vba-macro oletools.olevba.extract_macros (decoded VBA source) 1206 bytes