Malicious Office (OOXML) — malware analysis report

Static analysis result for SHA-256 18aedd88894ebcc4…

MALICIOUS

Office (OOXML)

67.9 KB Created: 2012-10-19 22:33:57 UTC Authoring application: Microsoft Excel 12.0000
MD5: 9da387d1f466296a4cd5848df8b35d61 SHA-1: 3fb9d84bf04f0fe0a7713589004c262087310dc3 SHA-256: 18aedd88894ebcc41578f720f0abd649ded2b289a52d8268d7cc210b0094d96c
208 Risk Score

Malware Insights

MITRE ATT&CK
T1059.005 Visual Basic T1204.002 Malicious File T1059 Command and Scripting Interpreter

The sample is an Excel document containing a Workbook_Open VBA macro. This macro utilizes CreateObject to write a file to the user's ALLUSERSPROFILE directory and appears to be designed to download and execute a second-stage payload. The use of Environ() and CreateObject indicates a malicious intent to interact with the file system and execute arbitrary code.

Heuristics 6

  • LOLBin reference in VBA critical OLE_VBA_LOLBIN
    LOLBin reference in VBA
  • Workbook_Open macro high OLE_VBA_WBOPEN
    Workbook_Open macro
  • CreateObject call high OLE_VBA_CREATEOBJ
    CreateObject call
  • VBA p-code auto-exec with execution tokens high OLE_VBA_PCODE_AUTOEXEC_EXEC
    Compiled 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_VBA
    Document contains a VBA project — VBA macros present
  • Environ() call (env variable access) low OLE_VBA_ENVIRON
    Environ() call (env variable access)

Extracted artifacts 2

Files carved from inside the sample during analysis.

FilenameKindSourceSize
macros.bas
b74b124ee7ca189df327101980fac891d25c9754768ed51a76525da015c8c4f5
vba-macro oletools.olevba.extract_macros (decoded VBA source from OOXML) 3726 bytes
vbaProject_00.bin
e24af6606c489f8af0e7f51b7bb928773958bb41a29d9242831cc3688b3c16dc
vba-project OOXML VBA project: xl/vbaProject.bin 16896 bytes