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

Static analysis result for SHA-256 14059c7d504e0649…

MALICIOUS

Office (OOXML) / .XLSX

63.6 KB Created: 2021-10-27 10:31:49 UTC Authoring application: Microsoft Excel 12.0000
MD5: 43db5539caa1ef7f4df3aa6c2e24c0f4 SHA-1: a1d952756446e767c92a77073c0948b46191fcaa SHA-256: 14059c7d504e064902e75c12fb3291f4b9dd348bca8bc1ab5f9285241e861270
182 Risk Score

Malware Insights

MITRE ATT&CK
T1059.005 Visual Basic T1203 Exploitation for Client Execution

The sample contains Excel 4.0 macros which are used to execute a command via `wmic` to launch `mshta` and download a file from one of the provided URLs. This indicates the file is designed to download and execute a second-stage payload, likely a malicious executable or script. The specific command executed is `wmic process call create 'mshta C:\ProgramData\excel.rtf'`, which attempts to download and run content from a remote source.

Heuristics 4

  • Excel 4.0 macro sheet (1 sheet(s)) critical OOXML_XLM_MACROSHEET
    Spreadsheet contains an Excel 4.0 (XLM) macro sheet — XLM was a major Office malware vector during 2020-2022 and evaded many VBA-focused controls before Microsoft tightened XLM defaults. Even legitimate XLM use is rare in modern workbooks. The macro sheet is stored as XLSB/BIFF12 binary content, which many XML-only OOXML scanners miss.
  • XLM payload reassembled from CHAR()/split formulas critical OOXML_XLM_REASSEMBLED_PAYLOAD
    An Excel 4.0 macro sheet builds its payload inside the formula token stream by concatenating per-character CHAR() calls and string fragments, so no WinAPI name, shell command, or URL is ever contiguous in the .bin for a literal-bytes scan to find. Reassembling the formulas recovered download/execute API names, LOLBin commands (regsvr32/rundll32/mshta/wmic/powershell), or a payload URL — the de-obfuscated download-and-run kill chain.
  • URL reconstructed from XLM cell array (3 URLs) critical OOXML_XLM_CELL_ARRAY_URL
    Excel 4.0 macro sheet stages its payload URL across individual numeric cells (one ASCII charcode per cell) or inside an embedded HTA that uses VBScript Chr()/&-concat obfuscation. The reconstructed URL is invisible to literal-bytes URL extraction because it is never contiguous in the workbook stream. URLs were recovered by walking the BIFF12 record stream of every worksheet and macrosheet part and decoding RK/inline-string cells in both row-major and column-major order.
  • 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 https://cdn.discordapp.com/attachments/906970546426765386/907252733155901500/InfrbLHV.wav
    • https://cdn.discordapp.com/attachments/906978504971792388/907257678856863854/CJvKgZ.wav
    • https://cdn.discordapp.com/attachments/906973832164827169/907255643210141716/KttheSDMNjPtN.wav

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
xlm_sheet_00.bin
fc145751608b5cc692e900bfdf51e6e60237c2250d25d8bcf11db144ec486fcd		 xlm-macrosheet OOXML XLM macro sheet: xl/macrosheets/sheet1.bin 56061 bytes

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