Malicious Office (OLE) — malware analysis report

Static analysis result for SHA-256 8423a8bd26afc773…

MALICIOUS

Office (OLE)

104.0 KB Created: 1996-12-17 01:32:42 Authoring application: Microsoft Excel First seen: 2019-05-31
MD5: cbf3b34e16b6973c9b64c853fe00119a SHA-1: fb5e1831e8365d1de74eaf9783c04531232a42b0 SHA-256: 8423a8bd26afc773c477bc18e43e2a032d8bb4813e26c59de872646a654a486a
280 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment T1105 Ingress Tool Transfer

The file is an Excel document with a high slack anomaly, indicating potential obfuscation or embedded content. Crucially, it contains an embedded PE executable, flagged by ClamAV as Win.Trojan.Agent-1266464. The presence of ShellExecute and LoadLibrary API calls further suggests the execution of this embedded payload. The document body contains what appears to be a list of names and financial data in Chinese, likely a lure to disguise the malicious intent.

Heuristics 5

  • Embedded PE executable critical OLE_EMBEDDED_EXE
    MZ/PE header found inside document — possible embedded executable
  • Reference to ShellExecute API high SC_STR_SHELLEXEC
    Reference to ShellExecute API
  • Reference to LoadLibrary API high SC_STR_LOADLIBRARY
    Reference to LoadLibrary API
  • Reference to GetProcAddress API high SC_STR_GETPROCADDRESS
    Reference to GetProcAddress API
  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 106,496 bytes but its declared streams total only 34,657 bytes — 71,839 bytes (67%) live in unallocated sector slack. This is the canonical hiding place for pre-macro-era Office exploit payloads (XOR-encoded shellcode reached via a parser pointer-corruption bug in the document structure).

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
embedded_office_00008e00.exe embedded-pe Office MZ+PE at offset 0x8E00 70144 bytes
SHA-256: 15e4f091971edf19ae2026ee3226ce3e6144fe981e10427106a03288f98e8dcc
Detection
ClamAV: Win.Trojan.Agent-1266464
Obfuscation or payload: unlikely