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

Static analysis result for SHA-256 ba5a4f1c0c776fe8…

MALICIOUS

Office (OLE) / .XLSX

1.26 MB
MD5: 223285beeace1bb1bcc37794539cbbb6 SHA-1: afc352e31765c1e0d150f3d3509ba671545207df SHA-256: ba5a4f1c0c776fe8d9cf8a8f82d66536d46da0f6b624baa395c1896fef2d49bf
140 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution T1559.001 Component Object Model Hijacking

The file is an encrypted OOXML document that contains embedded OLE objects, specifically identified as Microsoft Equation Editor. The presence of an 'Equation Editor OLE object' and an 'Ole10Native payload anomaly' strongly indicates the exploitation of a vulnerability within the Equation Editor component. This is a common technique for delivering second-stage malware. No specific family could be identified from the available heuristics.

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.