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

Static analysis result for SHA-256 8a1fbda779334255…

MALICIOUS

Office (OLE) / .XLSX

1.46 MB Created: 2006-09-16 00:00:00 Authoring application: Microsoft Excel
MD5: 0c37ce3722d5c40f455a85337c2755a0 SHA-1: 7d103a5ac1acc8b50a1a94330d012c42360ce9d2 SHA-256: 8a1fbda779334255e8bd64158f0fa7cb7e203921f8701e60f1c8ab7a8c2f1a54
68 Risk Score

Malware Insights

MITRE ATT&CK
T1204.002 Malicious File: User Execution T1059.005 PowerShell T1059.001 PowerShell T1059.003 Windows Command Shell T1059.004 Python

The critical heuristic firing indicates exploitation of CVE-2017-0199 via an OLE2Link object, which is designed to download and execute a remote payload from the provided URL. The VBA project, while not containing directly executable statements, is part of the exploit chain. The sample is therefore acting as a loader for a secondary malicious payload.

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.
    URL https://st3.pro/s6zpy2l?&anatomy=rustic&buffet=resonant&copyright=imaginary&snail
  • 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