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

Static analysis result for SHA-256 d2af85871cfc03c3…

MALICIOUS

Office (OLE) / .XLS

312.0 KB Created: 2006-09-16 00:00:00 Authoring application: Microsoft Excel
MD5: 58fefde9c951db5f9ecd94161c6b4bb9 SHA-1: 0b658f9de8f7d559c0db55459a39cb37cea4f2b3 SHA-256: d2af85871cfc03c3a435561bb9854e21bc97eab8a5aa6c388892c6cd5a5d4397
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, a known vulnerability for remote code execution. The heuristic firing indicates that the file attempts to load a remote resource from the URL 'https://exi.link/FGtdpw'. Although VBA macros were present, they contained no executable statements, suggesting the primary malicious functionality is delivered via 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