Malicious Office (OOXML) — malware analysis report

Static analysis result for SHA-256 afe50c43da2a5543…

MALICIOUS

Office (OOXML)

14.6 KB Created: 1996-10-14 23:33:28 UTC Authoring application: Microsoft Excel 15.0300 First seen: 2019-11-20
MD5: a919ea21f58d34d700fc053e683d257d SHA-1: 5a2c465547ec21f0c50580218c111afd5870d748 SHA-256: afe50c43da2a5543c2d05b08ad7c9af106ea7455330cce2f8b1f9c32117d5a62
140 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment T1203 Exploitation for Client Execution

The sample is an Office document containing an embedded OLE object, specifically an Equation Editor object. Heuristics indicate this object exploits CVE-2018-0798 and contains suspicious shellcode. The document also contains a lure to enable editing and macros, a common tactic for macro-based malware droppers. The embedded OLE object is the primary indicator of malicious activity, likely serving as a dropper for a second-stage payload.

Heuristics 5

  • Equation Editor OLE object high CVE related OLE_EQUATION_EDITOR
    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
    Embedded Equation Editor OLE data contains anomalous native stream bytes consistent with a CVE-2018-0798-style Equation Editor exploit. This is treated as likely CVE evidence because the Equation object is malformed and payload-like, but it does not match the exact public matrix-overflow byte signature.
  • Embedded OLE object medium OOXML_OLE_OBJECT
    Document contains an embedded OLE object
  • Macro/content-enable lure medium SE_ENABLE_LURE
    Document instructs the user to enable macros or editing — a common technique used by malware droppers to bypass Office macro security settings
  • Suspicious extracted artifact medium EXTRACTED_FILE_STATIC_TRIAGE
    One or more files extracted from inside this sample matched static suspicious-content checks such as script obfuscation, encoded payload blobs, packed data, or execution/download terms.

Extracted artifacts 2

Files carved from inside the sample during analysis.

FilenameKindSourceSize
ooxml_oleobject_00.bin ooxml-ole-object OOXML embedded OLE part: xl/embeddings/oleObject1.bin 3584 bytes
SHA-256: 247f7f8c7b69f8d6e29a33d4d47449b1526cea97da80cdd00a4c194c6096192a
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Static shellcode analysis found candidate code region(s). Indicators: SC_GETPC_CALL
ooxml_oleobject_00_ole10native_00.bin ole-package OOXML xl/embeddings/oleObject1.bin Ole10Native stream: OLe10naTive 1504 bytes
SHA-256: 16241655fd72f26fc48dd6d308f90d5fb8711b452b010750cb6884eed243cb6a
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Static shellcode analysis found candidate code region(s). Indicators: SC_GETPC_CALL