Malware Insights
The sample is an Excel file with a verdict of malicious. Static analysis detected XOR-encoded strings and a reference to the VirtualAlloc API, suggesting code execution and obfuscation techniques. The VBA project contains macros, but they are noted as having no executable statements, which is unusual for a malicious macro. The document body is heavily corrupted and unreadable. Given the limited readable content and the nature of the heuristics, the sample likely attempts to download and execute a second-stage payload, but the exact mechanism is obscured.
Heuristics 3
-
XOR-encoded strings (key 0xDE) critical SC_XOR_ENCODEDFound 5 Windows library/API name(s) XOR-encoded with single-byte key 0xDE: 'GetProcAddress', 'CreateProcessA', 'ExitProcess ', 'CreateFileA ', 'CreateFileW '
-
Reference to VirtualAlloc API medium SC_STR_VIRTUALALLOCReference to VirtualAlloc API
-
VBA project contains no executable statements low OLE_VBA_MACROSDocument contains a VBA project, but extracted modules only contain attributes/options/comments and no executable statements.
Extracted artifacts 1
Files carved from inside the sample during analysis.
| Filename | Kind | Source | Size |
|---|---|---|---|
macros.bas481031c20227961d1e7d207d0bb17c79a9001efbdb37ac509a4ff93acb047bf0 |
vba-macro | oletools.olevba.extract_macros (decoded VBA source) | 606 bytes |
Open this report in the interactive analyzer, or submit your own file for analysis.