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

Static analysis result for SHA-256 f35fdf3708e0904d…

MALICIOUS

Office (OLE) / .XLS

848.0 KB Created: 2006-09-16 00:00:00 Authoring application: Microsoft Excel
MD5: af853beeedbea2739c7497214f057b20 SHA-1: 8c69d67906e70c066aaa94e625db5eda0b35f117 SHA-256: f35fdf3708e0904da7671de8285a32d88c513900cbcdd38fa3c519fcd694fdf3
68 Risk Score

Malware Insights

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

The file is an Excel spreadsheet that exploits CVE-2017-0199 via a URL moniker to download and execute a remote payload from the URL https://rdt.li/SJBo4C?&management=exclusive&mortise=painstaking&gold=sour&mailbox=busy&lead=sticky&witness=irate&wood=Early&hen=scary&bower. Although VBA macros were extracted, they contained no executable statements, indicating the exploit is likely embedded within the OLE structure itself.

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