Office (OOXML) / .XLSX malware analysis — malicious · 9b8baa739b7a7a3d

MALICIOUS

Office (OOXML) / .XLSX

24.5 KB Created: 2006-09-16 00:00:00 UTC Authoring application: Microsoft Excel 14.0300

MD5: 474f1ab38dbc8787b510d01526a832a7 SHA-1: 6d2b850f0a5817fa7648d2f59f57468701a3b598 SHA-256: 9b8baa739b7a7a3d57e9083bf628661cb550dae7255b0bf33db8b45128567e22

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, as indicated by the OOXML_XLM_MACROSHEET heuristic. The OOXML_XLM_BINARY_WINAPI_STRINGS heuristic reveals WinAPI calls such as URLDownloadToFileA and ShellExecuteA, suggesting the macro's intent is to download and execute a secondary payload. The presence of these WinAPI strings and the .exe path strongly indicates a downloader or droppper 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.

Filename	Kind	Source	Size
`xlm_sheet_00.bin` `99a6a52acb8f5c734f6d86faf89e0637a94ac99f953aa583d2658b47d2e1f9b9`	xlm-macrosheet	OOXML XLM macro sheet: xl/macrosheets/sheet1.bin	194023 bytes

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