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

Static analysis result for SHA-256 b30a2fc5b2c52046…

MALICIOUS

Office (OOXML) / .XLSX

71.4 KB Created: 2021-10-27 10:31:49 UTC Authoring application: Microsoft Excel 12.0000
MD5: 171d7bf6a58d05196de20d7827760ada SHA-1: 267efb3e719d077d75b0c0744b142818b80bc446 SHA-256: b30a2fc5b2c5204630385ae6ae07c95dd72eeab0daffe9fe4daccdeda4bbdb95
182 Risk Score

Malware Insights

MITRE ATT&CK
T1059.005 Visual Basic T1204.002 Malicious File T1105 Ingress Tool Transfer

The file contains Excel 4.0 macros that utilize WinAPI functions such as URLDownloadToFileA. These macros reconstruct and attempt to download payloads from three distinct URLs. Although the URLs themselves are currently flagged as benign, the presence of macro-based download functionality indicates a malicious intent to fetch and execute a second-stage payload. The macro sheet also contains strings related to error reporting to Microsoft, which is a common tactic to mask malicious activity.

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.
  • Binary XLM macro sheet with WinAPI/download strings critical OOXML_XLM_BINARY_WINAPI_STRINGS
    Excel 4.0 macro sheet is stored as BIFF12/XLSB binary data and contains Win32 download or process-execution API strings such as URLDownloadToFileA, ShellExecuteA, or CreateDirectoryA. These strings are high-signal in XLM macro sheets and catch payload-download macros that XML-formula scanners cannot parse.
  • 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/911249881849536584/912356063758675998/GjEdowscAmeMpshekniggagook.flac
    • https://cdn.discordapp.com/attachments/911249881849536584/912356058922614854/CVjrWfYwLXUpshekniggagook.flac
    • https://cdn.discordapp.com/attachments/911249881849536584/912356067688714250/cvVactCffEgjaSvpshekniggagook.flac

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
xlm_sheet_00.bin
976cfd503b751067e3ac573b984572e297ff374919ae7a278351d7996da24640
xlm-macrosheet OOXML XLM macro sheet: xl/macrosheets/sheet1.bin 4807 bytes