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

Static analysis result for SHA-256 faf2ad5446a72ba2…

MALICIOUS

Office (OLE) / .XLS

222.5 KB Created: 2006-09-16 00:00:00 Authoring application: Microsoft Excel
MD5: 8db0fcd900e5d8423320c3c88cd6263c SHA-1: bce2addc21de9217f964a63e1e46392d7a7ca69b SHA-256: faf2ad5446a72ba2c4a9aca0600fa6bf24fce0e5930a5d550afb737157396b67
68 Risk Score

Malware Insights

MITRE ATT&CK
T1204.002 Malicious File T1059.005 Visual Basic

The sample is an OLE file that fired a critical heuristic for CVE-2017-0199, indicating it attempts to load remote content via a URL moniker. The extracted URL 'http://gf.to/mtjuLULto' is highly suspicious and likely serves as the initial download location for a secondary payload. Although the VBA project itself contained no executable statements, the OLE structure and the CVE firing strongly suggest a remote code execution attempt.

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