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

Static analysis result for SHA-256 99bcf22fcdc3a2d8…

MALICIOUS

Office (OLE) / .XLS

1.24 MB Created: 2006-09-16 00:00:00 Authoring application: Microsoft Excel
MD5: 22bcf4b4d0fe8f062dda892fcc44f627 SHA-1: dc2188ee9a5db06b0c00db9e0d1cba02767a1d41 SHA-256: 99bcf22fcdc3a2d89e38f756e9f3d897fcba0bbb50f57a20885569262c0b3c38
68 Risk Score

Malware Insights

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

The sample is an OLE file that exploits CVE-2017-0199 via a URL moniker to download a remote payload from the URL 'https://dggfrjgjggjhgjhgjgffhfdhgfjfjfjgfgfjfjffjkjguhccvcbvcgfgcgfcfgcgfc.doc@cpbr.link/hiQl7B'. Although the VBA project itself contains no executable statements, the exploit mechanism is clearly indicated by the heuristic firing. The file's purpose is to act as a loader for malicious content hosted at the specified URL.

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

Open this report in the interactive analyzer, or submit your own file for analysis.