Office (OLE) / .XLS malware analysis — malicious · 555c9fab8b1c2180

MALICIOUS

Office (OLE) / .XLS

1.13 MB Created: 2006-09-16 00:00:00 Authoring application: Microsoft Excel

MD5: f69d18b27ddddb4274a97434c6a01ae2 SHA-1: 79a2cf394e8fe22341922a6490e9d58a87e2f748 SHA-256: 555c9fab8b1c2180ec0c140d7ef7a072d3848661e47051b4dda5de40a61465b7

68 Risk Score

Malware Insights

MITRE ATT&CK

T1204.002 Malicious File T1059.005 Visual Basic

The sample is an OLE2Link file that exploits CVE-2017-0199. It contains a URL moniker that points to a remote resource, indicating it's designed to download and execute a second-stage payload. The VBA project is present but contains no executable statements, suggesting the exploit is triggered by the OLE structure itself rather than macro code.

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.

Filename	Kind	Source	Size
`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.