Office (OLE) / .XLSX malware analysis — malicious · 455df529c35ffb54

MALICIOUS

Office (OLE) / .XLSX

848.0 KB Created: 2006-09-16 00:00:00 Authoring application: Microsoft Excel

MD5: 8b2d3878528d15f4b8308c6b6d2be5e1 SHA-1: 79d4f7e459d85505c7e96ccf154a611099d48c4f SHA-256: 455df529c35ffb5442fa7278f6758982122b5c9a59fae87314c7cbde29e89e99

68 Risk Score

Malware Insights

MITRE ATT&CK

T1204.002 Malicious File T1059.005 Visual Basic

The sample is an Excel file that exploits CVE-2017-0199 via an OLE2Link object. This exploit is known to download and execute a remote payload from a provided URL. The extracted URL, https://rdt.li/GbdrNq?&reception=alcoholic&mantle=ignorant&observation=annoying&chipmunk=orange&anthony=ablaze&trailer=cooperative&keystone=furtive&astrology, is highly suspicious and likely serves as the initial download source for a second-stage payload. No VBA macros were found to be executable, but the exploit itself is sufficient for malicious 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.

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.