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

Static analysis result for SHA-256 b3509baca2fcda3d…

MALICIOUS

Office (OLE) / .XLS

99.0 KB Created: 2006-09-16 00:00:00 Authoring application: Microsoft Excel
MD5: 84e0531cc0e1451ddc565a3c7b035f51 SHA-1: 630569cc3d8eda4d316acf973db854ecc099b23a SHA-256: b3509baca2fcda3d133086681eac9d68c8504df1c2ae62cc15ef32d360218e61
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 and execute a remote payload from the URL 'https://u4u.kids/SEiLXo?&pickax=wicked&chub=slow&level=noisy&food=placid&wine=sulky&doorpost=sleepy&decrease=internal&june=bewildered&somewhere=cool&sack'. Although VBA macros were present, 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