Malicious Office (OLE) — malware analysis report

Static analysis result for SHA-256 90af3419fde34080…

MALICIOUS

Office (OLE)

90.2 KB Created: 2018-11-05 10:02:00 Authoring application: Microsoft Office Word First seen: 2019-08-04
MD5: 011733c7ef6781ad083d207488e6b8a5 SHA-1: e541abaacf7d86d23fa0da3a5f046a973663e6f7 SHA-256: 90af3419fde34080e8c642ddb8f24b8ce07b7c76088e09cc31b6594666c2bd00
122 Risk Score

Malware Insights

MITRE ATT&CK
T1059.001 PowerShell T1566.001 Spearphishing Attachment

The document contains a PowerShell command that decodes and executes a Base64 encoded string. This script is designed to download and execute a second-stage payload. The presence of the PowerShell command and the OLE slack anomaly suggest a malicious document, likely delivered as a spearphishing attachment.

Heuristics 4

  • Reference to PowerShell high SC_STR_POWERSHELL
    Reference to PowerShell
  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 92,416 bytes but its declared streams total only 47,756 bytes — 44,660 bytes (48%) 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).
  • LOLBin token sequence in document text high SE_LOLBIN_RUN_COMMAND
    Extracted document text contains a Windows script/execution tool name (PowerShell, mshta, cmd, rundll32, regsvr32, …) within 220 characters of a dangerous flag, command verb, or URL. This is a visible 'run this' instruction in HTML/PDF/RTF lure bodies, or — in macro-laden Office files — the macro's own string-pool entries appearing adjacent in extracted text.
  • Embedded URL info EMBEDDED_URL
    One or more URLs were extracted from the document. The URL itself is not a detection — see the per-URL labels for which channel (macro, JS, link annotation, document body, ...) reached each URL.
    URL http://schemas.openxmlformats.org/drawingml/2006/main In document text (OLE body)