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

Static analysis result for SHA-256 4174dee56585f38d…

MALICIOUS

Office (OLE) / .XLS

320.5 KB Created: 2006-09-16 00:00:00 Authoring application: Microsoft Excel
MD5: c399357023c4282829c7c9d321f8520e SHA-1: 95b9c09c09b898924d933b511c98ba35317b56a7 SHA-256: 4174dee56585f38df00e48a5c0f2f6aa4d03db9e5b6759d2825ed55b253e4b9a
68 Risk Score

Malware Insights

MITRE ATT&CK
T1204 Malicious Link T1204.001 Malicious Link: Malicious Link T1059 Command and Scripting Interpreter T1059.005 Command and Scripting Interpreter: Visual Basic

The sample is an OLE2Link file that exploits CVE-2017-0199 via a URL moniker to load a remote resource. The embedded URL 'http://strms.ly/PjcM' is highly suspicious and likely serves as a downloader for a secondary payload. Although VBA macros were present, they contained no executable statements, indicating the exploit is likely delivered through the OLE object itself.

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.