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

Static analysis result for SHA-256 bc7355b19c98e039…

MALICIOUS

Office (OOXML) / .XLSX

24.5 KB Created: 2006-09-16 00:00:00 UTC Authoring application: Microsoft Excel 14.0300
MD5: b02064b410a7bee8e8607026a3305706 SHA-1: 433328f74257f99c2a8c1bb7423dc800150c6a29 SHA-256: bc7355b19c98e039be1bcb3f65136fe1007394480b593a71df70255595f75a28
120 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 presence of WinAPI and download strings, specifically mentioning URLDownloadToFileA, DownloadToFileA, ShellExecuteA, CreateDirectoryA, URLMon, and Kernel32. This suggests the macro is designed to download and execute a second-stage payload, likely an executable file, from a remote source. The specific strings extracted point to a downloader functionality.

Heuristics 2

  • 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.

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
xlm_sheet_00.bin
99a6a52acb8f5c734f6d86faf89e0637a94ac99f953aa583d2658b47d2e1f9b9
xlm-macrosheet OOXML XLM macro sheet: xl/macrosheets/sheet1.bin 194023 bytes