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

Static analysis result for SHA-256 d4819f6ce1e7c5ed…

MALICIOUS

Office (OLE) / .XLS

305.5 KB Created: 2006-09-16 00:00:00 Authoring application: Microsoft Excel
MD5: 3f6b0fddaa94e07440a3890afc3dc99c SHA-1: 2c963eb3944bc4be5892e6ef95283e2b8b9bcaf1 SHA-256: d4819f6ce1e7c5ed703e11e3ae98ebfb04abe95ac2a221bcc43696de923bdbb2
68 Risk Score

Malware Insights

MITRE ATT&CK
T1204.002 Malicious File: User Execution T1059.005 PowerShell T1071.001 Web Protocols: HTTP

The sample exploits CVE-2017-0199 via a URL moniker to download a remote payload from the URL 'https://st3.pro/YjzNwpD?&slope=needy&robert=grotesque&crest=fragile&agreemen'. Although VBA macros were present, they contained no executable statements, indicating the exploit is likely embedded within the OLE structure itself. The file is an Excel spreadsheet, but the document body content is heavily corrupted and unreadable.

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