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

Static analysis result for SHA-256 e962f2bab8a328a8…

MALICIOUS

Office (OLE) / .XLS

848.0 KB Created: 2006-09-16 00:00:00 Authoring application: Microsoft Excel
MD5: e7d6ba07646e91330d71f3a1196a20e0 SHA-1: 4d9bb802929f645879e4d4bb0ca2bd7b6d90fcc5 SHA-256: e962f2bab8a328a8e3891a9a07d57736d4198a0ac98c76204b0ee0558e116dfa
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, a known vulnerability for remote code execution. The heuristic indicates that the OLE stream contains a URL moniker pointing to 'https://rdt.li/1JVeT9?&demur=lean&venom=good&angora=fast&epee=tightfisted&pocket=obscene&methodology=enthusiastic&flintlock=flippant&pilot=moaning&company', which is likely used to download and execute a second-stage payload. No VBA macros were found to be executable, but the exploit itself is sufficient for malicious activity.

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