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

Static analysis result for SHA-256 b37d86a9013eb60d…

MALICIOUS

Office (OLE) / .XLS

673.0 KB Created: 2006-09-16 00:00:00 Authoring application: Microsoft Excel
MD5: 26b3be60b35becbc490d3415261a522e SHA-1: ca9a0114168e0b7317967b1f1000891c6b084694 SHA-256: b37d86a9013eb60ddb5cd39356493c5d7ab56d2b3b2e99213dee8c6b3eade908
68 Risk Score

Malware Insights

MITRE ATT&CK
T1204.002 Malicious File Execution: Malicious File T1059.005 Command and Scripting Interpreter: Visual Basic

The sample is an OLE2Link file that exploits CVE-2017-0199. This vulnerability allows the file to act as a remote loader, downloading and executing a secondary payload from a specified URL. The extracted URL, http://030064535307030064535307030064535307030064535307@030064535307/httpsdeveloper.box.comguidesbox-aiai-tutorialsprerequisites.php, is indicative of this behavior. Although VBA macros were present, they contained no executable statements, suggesting the primary malicious functionality relies on the OLE vulnerability.

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