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

Static analysis result for SHA-256 8087bbe34f6bd622…

MALICIOUS

Office (OLE) / .XLS

848.0 KB Created: 2006-09-16 00:00:00 Authoring application: Microsoft Excel
MD5: 0a3e3fee911e89820e0f428e31f8e0ac SHA-1: 0000692437d8054df2c2ded80c4c35f6de07a6a0 SHA-256: 8087bbe34f6bd622a82115c7653470d15ec77183b5cb82e1996fb170b1ace01f
68 Risk Score

Malware Insights

MITRE ATT&CK
T1204.002 Malicious File Execution: Malicious File T1059.005 Command and Scripting Interpreter: Visual Basic

The sample is an OLE2 file that triggers a critical heuristic for CVE-2017-0199, indicating it's a remote loader. The heuristic also extracted a URL, 'https://jfm.com.co/k3l?&alloy=handsome&convection=panicky&acid=giddy&position=absorbing&regular=orange&database=cuddly&squid', which is likely used to download and execute a second-stage payload. Although VBA macros were present, they contained no executable statements, suggesting the exploit is directly embedded within the OLE structure.

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