Malicious VBScript analysis – 7997bfe7ec26

Ctrl + scroll to zoom · drag to pan

Get an AI-generated breakdown of this malware's behaviour, IOCs and recommendations.

AI analysis is available with Essential.

Unlock with Essential

File

Type

Microsoft Office Document

Size

2.74 MB · 2,744,832 B

First seen

2026-07-16 07:02 · 3 months ago

Last seen

2026-07-16 07:02 · 3 months ago

Last analysis

2026-07-17 17:43 · 3 months ago

Hashes

MD5 60efa74b894ca64dbb57cb20495aa834 Sha1 8f6485ca31d5464bf443ecd03560deb24a12934b Sha256 7997bfe7ec26d2ed24ab7fa1fb2a3542762876910d33284273f76e20928f1d72 Sha384 72c3ffd66beac328b7a588f2fe193aa9559aeb23953e01aa324547b18b6b0b3853073489ce5dda53f654351e8b215778 Sha512 a13e4c7b087c97a667c42cb83f74e125470e24c91253a08cfc55dbe998af6543a6ec522f212392ebbe36075e8e8db9e4209d7109fdf2d9ed46f5eaaff46a4ae9 SSDeep 6144:w/uBKyYPGn/84e15Xg1lIkGuDQMi2cSa2AnlPpyj3iaM1YdOOtup19IJVNABDEQo:Bu8dM1Y5tYDQo49fiZXZ849f0 TLSH DAC539B629D1DA05D6781432CE7B955C0CE02EDBDE84A9173E1FF30F377812162D8A9A

8 malicious · 23 files

VBS60efa74b894ca64dbb57cb20495aa834

BINRoot Entry

BINCompObj

BINWorkbook

BINSummaryInformation

BINDocumentSummaryInformation

BIN_VBA_PROJECT_CUR

BINPROJECT

BINPROJECTwm

BINVBA

BINdir

VBAMódulo1

VBS[Stored VBA]

VBS[PCode]

VBS[Decompiled VBA]

VBS[Full Diff]

VBS[Partial Diff]

VBS_VBA_PROJECT

BINMsoDataStore

STICH beta Structural Threat Infection Chain Hash

A content-independent fingerprint of the infection method: successive formats, internal objects and MITRE techniques from the initial file to each final payload.

STICH Path = the fingerprint (canonical chain with techniques) STICH Shape = structure only Only determinant branches produce STICH Paths.

4 / 4

Path ole:doc~T1059.005~T1564.007>bin

Shape ole:doc>bin

malicious 2 nodes

Path ole:doc~T1059.005~T1564.007>ole:vba~T1059.005~T1564.007

Shape ole:doc>ole:vba

malicious 2 nodes

	Module Name0
	Módulo1	VBA Stomping ATT&CK T1564.007 Malicious Malicious Document VBA Macro
PCode Decompiled VBA Stored VBA Partial Diff. Full Diff. Missing P-Code: The Office document under analysis has been identified as having undergone VBA Purging techniques, as the P-Code block within the document is currently inaccessible. As a result, the decompilation of the code was not possible, leaving only the stored code available in textual format for analysis. VBA Purging essentially involves the elimination of the PerformanceCache section from the module streams. To fully erase any traces of the P-Code section, the MODULEOFFSET between the two sections is adjusted to 0 by altering the _VBA_PROJECT stream, and all SRP streams that also house PerformanceCache data are removed. Following the removal of the compiled code, antivirus engines and Yara rules, which depend on precise string matches, are rendered ineffective. This allows macros to bypass them effortlessly, owing to the compressed format of the remaining source code.