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

Static analysis result for SHA-256 b8bc4f09f6fe6a9b…

MALICIOUS

Office (OOXML) / .XLSX

84.0 KB Created: 2021-10-27 10:31:49 UTC Authoring application: Microsoft Excel 12.0000
MD5: 0f9a68a19b3575672f355e752f65131f SHA-1: a3199be8f0161cfe80f1f4ab306cde443de28253 SHA-256: b8bc4f09f6fe6a9b6601bc650b4b8a20df4aad870d8287a7a81c90594aeeb2fd
182 Risk Score

Malware Insights

MITRE ATT&CK
T1059.005 Visual Basic T1204.002 Malicious File T1059.001 PowerShell

The sample contains Excel 4.0 macros that utilize WinAPI functions like URLDownloadToFileA to download a file from one of the provided URLs. The reconstructed path 'C:\ProgramData\KrXQcMbPgZ' suggests the downloaded payload is intended to be executed from that location. The URLs themselves, while flagged as confirmed benign by the analysis, were part of the macro's download functionality, indicating a downloader pattern.

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/910251809556271117/912318007320145940/XOftdbhXmOZcuntfuck.mp4
    • https://cdn.discordapp.com/attachments/910251809556271117/912318020003692574/FqtFBvEOrukvcuntfuck.mp4
    • https://cdn.discordapp.com/attachments/910251809556271117/912318014416912415/XOwuRIcuntfuck.mp4

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
xlm_sheet_00.bin
0075b451e7e077bc86d74e441002a72c07dd132f02900a72e331a60eb99e0b5a
xlm-macrosheet OOXML XLM macro sheet: xl/macrosheets/sheet1.bin 5827 bytes