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

Static analysis result for SHA-256 84991ff0c0b97029…

MALICIOUS

Office (OLE) / .XLSX

1.43 MB Created: 2006-09-16 00:00:00 Authoring application: Microsoft Excel
MD5: d82cece208a51e441397e48be2fd2140 SHA-1: 8d4b287eb3671750fe9d96b66a9d052c632bbd18 SHA-256: 84991ff0c0b97029a9ad9243cf9e46fa744552ea92ac0405961753f5f570d82e
88 Risk Score

Malware Insights

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

The critical heuristic firing for CVE-2017-0199 indicates that the OLE2Link object is being used to load a remote resource. The extracted URL, 'https://wegivebestthingswithbetterfuturenowarnupthingstodowithbestpeoples.busienss@links.dansarindustries.com/xAlUEj', is likely the location of the second-stage payload. Although VBA macros were detected, they contained no executable statements, suggesting the exploit is directly embedded within the OLE structure.

Heuristics 3

  • 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.
  • NOP-equivalent sled detected medium SC_NOP_EQUIV_SLED
    Long run of 0x61 bytes
  • 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