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

Static analysis result for SHA-256 be8e26740538a54b…

MALICIOUS

Office (OLE) / .XLSX

1.21 MB
MD5: 62076932340efcbb9318f7310e4685b0 SHA-1: cd9c1249133284bf7311dee81f61f77f565f24c8 SHA-256: be8e26740538a54b9fd6f9a1be079d91f59224885e78c832840dee42250dab77
140 Risk Score

Malware Insights

MITRE ATT&CK
T1204.002 Malicious File: User Execution: Malicious File T1559.001 Component Object Model Hijacking

The sample is an OOXML file encrypted with a default password, indicating an attempt to hide its malicious contents. High-severity heuristics indicate the presence of an Equation Editor OLE object, a known carrier for exploits. The 'OLE_EQUATION_OLE10NATIVE_PAYLOAD_ANOMALY' heuristic specifically points to a malformed Ole10Native stream within the Equation Editor object, strongly suggesting it's designed to deliver a second-stage payload.

Heuristics 4

  • Equation Editor OLE object high CVE related OLE_EQUATION_EDITOR
    Default-encrypted OOXML embedded OLE object xl/embeddings/oleObject1.bin contains the Equation Editor CLSID, the legacy component exploited by CVE-2017-11882, CVE-2018-0802, and CVE-2018-0798.
  • Default-encrypted OOXML exploit carrier layout high OOXML_ENCRYPTED_EXPLOIT_CARRIER_SHAPE
    Default-password encrypted OOXML package contains embedded OLE object parts and additional activation/decoy parts. This layout is common in malicious Excel exploit delivery and requires inspecting the decrypted package.
  • Equation Editor object carries payload-like Ole10Native stream high OLE_EQUATION_OLE10NATIVE_PAYLOAD_ANOMALY
    Default-encrypted OOXML embedded OLE object declares the Equation Editor CLSID but stores a large high-entropy Ole10Native stream with malformed package sizing. This is exploit-shaped Equation/OLE payload evidence.
  • Office OOXML encrypted with default VelvetSweatshop password medium OFFICE_DEFAULT_PASSWORD_ENCRYPTED_OOXML
    OLE EncryptedPackage decrypts with Excel's built-in VelvetSweatshop password. Office opens this transparently, and malware uses it to hide OOXML exploit parts from scanners that only inspect the outer OLE container.