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

Static analysis result for SHA-256 4f805c416478dc31…

MALICIOUS

Office (OOXML) / .XLSX

26.3 KB Created: 2006-09-16 00:00:00 UTC Authoring application: Microsoft Excel 14.0300
MD5: 3261a70fc80f2e0f85f7aba8bb74f562 SHA-1: dc76b3acbfc7f564c86b9d970479094d367f4c86 SHA-256: 4f805c416478dc310e6fc6041ba233e5bef96808e0f46868fdcb0cb182df5952
182 Risk Score

Malware Insights

MITRE ATT&CK
T1059.005 Service Execution: Visual Basic T1204.002 Malicious File: User Execution: Malicious File T1059.001 Command and Scripting Interpreter: PowerShell T1059.003 Command and Scripting Interpreter: Windows Command Shell

The sample contains Excel 4.0 macros, which are known to be used for malicious purposes. The macros contain strings indicative of downloading and executing files, such as URLDownloadToFileA and ShellExecuteA. The reconstructed URL http://jdsofttech.com/ds/3.gif is likely used to fetch a second-stage payload. The use of these WinAPI functions within the macro sheet strongly suggests a downloader or droppper functionality.

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 http://jdsofttech.com/ds/3.gif

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
xlm_sheet_00.bin
353cb9e320e769bd0172c949754a12b71aae8fc508fdcdd3a2c593938b07a06a
xlm-macrosheet OOXML XLM macro sheet: xl/macrosheets/sheet1.bin 200427 bytes