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

Static analysis result for SHA-256 499e6d50f4a3f8df…

MALICIOUS

Office (OLE) / .XLSX

197.0 KB
MD5: 6ea4ab8eafb39e09b2e4617bc83425ac SHA-1: 48b6ff0545c595f7cf59ff5ea842937605a0bdac SHA-256: 499e6d50f4a3f8dfde549cf2da0f74be5ee696454c9c933988ac6b7bd5572ed5
140 Risk Score

Malware Insights

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

The file is an encrypted Office document containing an embedded Equation Editor OLE object. Heuristics indicate exploitation of CVE-2018-0798 via an anomalous Equation Editor native stream, which is a known method for delivering malicious payloads. No document body or scripts were extractable due to encryption, but the presence of the exploit carrier strongly suggests a client-side execution attack.

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.
  • CVE-2018-0798 — anomalous Equation Editor native stream high CVE likely CVE_2018_0798_EQUATION_NATIVE_ANOMALY
    Default-encrypted OOXML contains embedded Equation Editor data with anomalous native stream bytes consistent with a CVE-2018-0798-style exploit. This is treated as likely CVE evidence because the Equation object is malformed and payload-like.
  • 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.
  • 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.