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

Static analysis result for SHA-256 d865cf68b275cbb9…

MALICIOUS

Office (OOXML) / .XLSX

26.5 KB Created: 2006-09-16 00:00:00 UTC Authoring application: Microsoft Excel 14.0300
MD5: e033b63a8426cb6ba7d1327302df07cc SHA-1: 10fbd559ca4642335f813eb01f11fea47ba10414 SHA-256: d865cf68b275cbb99a8ebbd5e1e402a5b2efb2dbad199d7c481b01be59fbe1e8
182 Risk Score

Malware Insights

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

The sample is an Excel file containing Excel 4.0 macros. Heuristics indicate the macros contain WinAPI strings related to downloading and executing files, specifically referencing URLDownloadToFileA and ShellExecuteA. The macro reconstructs a URL, https://mmsu.com.ua/ds/4.gif, which is likely used to download a second-stage payload. The presence of these WinAPI calls and the reconstructed URL strongly suggests the file's purpose is to act as a downloader.

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 (1 URL) 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://mmsu.com.ua/ds/4.gif

Extracted artifacts 1

Files carved from inside the sample during analysis.

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

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