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

Static analysis result for SHA-256 977ee4ca17a45f9c…

MALICIOUS

Office (OLE) / .XLS

111.1 KB Created: 1996-12-17 01:32:42 Authoring application: Microsoft Excel
MD5: 2b6e5b0e1e8ac5f06109145308c4a289 SHA-1: 174f062c3f2719d1c4a42c76ed77cfaa378310a5 SHA-256: 977ee4ca17a45f9c742b6887e7987f61a212c75f2671c1cd3b4e3f94a51c4c03
120 Risk Score

Malware Insights

MITRE ATT&CK
T1059.003 Windows Command Shell

The sample is an XLS file exhibiting OLE slack anomalies and a suspicious cmd.exe invocation. The PEB access heuristic further suggests code execution. While no scripts were extracted, the presence of embedded URLs, some of which are unknown, indicates a potential download or redirection attempt. The primary attack pattern involves leveraging cmd.exe for execution, likely to fetch a secondary payload.

Heuristics 4

  • PEB access via FS segment (x86) high SC_PEB_ACCESS
    PEB access via FS segment (x86)
  • Suspicious cmd.exe invocation with execution flag high SC_STR_CMD
    Suspicious cmd.exe invocation with execution flag
  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 113,726 bytes but its declared streams total only 24,565 bytes — 89,161 bytes (78%) 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).
  • 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://www.pdf-repair.com
    • http://www.pdf-repair.com)/Producer(Advanced
    • http://www.pdf-repair.com)/ModDate(D:20100406171120+08
    • http://www.w3.org/1999/02/22-rdf-syntax-ns#
    • http://ns.adobe.com/pdf/1.3/
    • http://ns.adobe.com/xap/1.0/
    • http://ns.adobe.com/xap/1.0/mm/
    • http://purl.org/dc/elements/1.1/

Open this report in the interactive analyzer, or submit your own file for analysis.