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

Static analysis result for SHA-256 62b2ce32d6e2eccc…

MALICIOUS

Office (OOXML) / .XLSX

26.3 KB Created: 2006-09-16 00:00:00 UTC Authoring application: Microsoft Excel 14.0300
MD5: 413a2758dbd5009a0733c5c80d13fbe6 SHA-1: 79e6275529e44beb3d454cc48ff40f2099c873ba SHA-256: 62b2ce32d6e2ecccdb5949b986fead0075311fe84da3cce695c6ef16b76e3941
242 Risk Score

Malware Insights

MITRE ATT&CK
T1059.005 Visual Basic T1105 Ingress Tool Transfer T1204.002 Malicious File

The file contains Excel 4.0 macros, identified by the OOXML_XLM_MACROSHEET heuristic. These macros utilize WinAPI functions like URLDownloadToFileA and ShellExecuteA, as indicated by OOXML_XLM_BINARY_WINAPI_STRINGS, to download a payload from the URLs https://grennancommunications.com/ and https://grennancommunications.com/ds/3.gif. The OOXML_XLM_REASSEMBLED_PAYLOAD and OOXML_XLM_CELL_ARRAY_URL heuristics confirm the reconstruction of these URLs from the macro content, suggesting an attempt to execute a malicious file.

Heuristics 5

  • 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.
  • XLM payload reassembled from CHAR()/split formulas critical OOXML_XLM_REASSEMBLED_PAYLOAD
    An Excel 4.0 macro sheet builds its payload inside the formula token stream by concatenating per-character CHAR() calls and string fragments, so no WinAPI name, shell command, or URL is ever contiguous in the .bin for a literal-bytes scan to find. Reassembling the formulas recovered download/execute API names, LOLBin commands (regsvr32/rundll32/mshta/wmic/powershell), or a payload URL — the de-obfuscated download-and-run kill chain.
  • URL reconstructed from XLM cell array (2 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://grennancommunications.com/
    • https://grennancommunications.com/ds/3.gif

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
xlm_sheet_00.bin
523137d3ab012777b42b7b668940ce7c88f6117e020ac374dbff84c9d4361266		 xlm-macrosheet OOXML XLM macro sheet: xl/macrosheets/sheet1.bin 200475 bytes

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