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

Static analysis result for SHA-256 c8504c89b33bff22…

MALICIOUS

Office (OLE) / .XLSX

1.15 MB Created: 2006-09-16 00:00:00 Authoring application: Microsoft Excel
MD5: 9e7dfc9a5bc4bd16d7c376e795b2be5a SHA-1: 5213242cc7e29dbd7ae6de1c765d0cc2c68dd1b3 SHA-256: c8504c89b33bff22b826d1c74f5fd52d237e01a94935aad7f5b3b783aa21e669
68 Risk Score

Malware Insights

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

The critical heuristic firing indicates exploitation of CVE-2017-0199 via an OLE2Link object, which is designed to load remote content. The extracted URL, https://sorkale.me/PEXMyP, is highly suspicious and likely serves as the source for a second-stage payload. Although the VBA project contains source code, it does not appear to contain executable statements, suggesting the exploit relies on the OLE object itself rather than embedded VBA code for initial execution.

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

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