Deep Malware Analysis of 33f7f4879fe3cb6018f45f5c84e6c90f | md5: 33f7f4879fe3cb6018f45f5c84e6c90f | Office Document | VBA Stomping | ATT&CK T1564.007 | Malicious | Malicious Document | Blacklist VBA | SOS: 0.67 | DeObfuscated | VBScript | T1059.005 | Obfuscated | T1027 | COM Behavior Trace | SOS: 0.76 | SOS: 0.75 | WScript.Shell | microsoft.xmlhttp | Shell.Application | adodb.stream | T1105

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

250.37 KB · 250,368 B

First seen

2026-10-25 14:30 · 32 minutes ago

Last seen

2026-10-25 14:30 · 32 minutes ago

Last analysis

2026-10-25 14:30 · 32 minutes ago

Hashes

MD5 33f7f4879fe3cb6018f45f5c84e6c90f Sha1 2adf75439f7556d4b96ba0e6eee8fb9694dc9f52 Sha256 a6645dbb2c35b9658ef4964438bf77f68f4656cf24561a69da8b62be8bed1917 Sha384 74bba80df6223b37e1ba772369abd8926a0309b283557183e492a82ec1ab596aa0247a54f770d3dba08f2314af38312b Sha512 7fc0b4e0ddfc294eb9f2017bdf302528dbb06bd6b35202f92a0a4915febc8036ff06d7f9d167db74cbbec1bd2a470113f7ef6b0c28c08bf560b6d65a2047e3b7 SSDeep 6144:axEtjPOtioVjDGUU1qfDlavx+W2QnALrQsHBGilkW8a+TJJp/vC7zoVmzV4ZeTYD:wkskWOlCAImZYMl TLSH D434AD53B1569DC2D54C83F86E9787EA2F22EF09DA566FCB2150BF0EBB702434C16225

17 malicious · 29 files

OFF33f7f4879fe3cb6018f45f5c84e6c90f

BINRoot Entry

BINCompObj

BINWorkbook

BINSummaryInformation

BINDocumentSummaryInformation

BIN_VBA_PROJECT_CUR

BINPROJECT

BINPROJECTwm

BINVBA

BINdir

VBAModule1

VBS[Stored VBA]

VBS[Stored VBA].deobfuscated.vbs

VBA[PCode]

VBS[Decompiled VBA]

VBS[Decompiled VBA].deobfuscated.vbs

VBA[Full Diff]

VBA[Partial Diff]

BIN__SRP_0

BIN__SRP_1

BIN__SRP_2

BIN__SRP_3

VBAThisWorkbook

VBS[Stored VBA]

VBS[Stored VBA].deobfuscated.vbs

VBA[PCode]

VBS[Decompiled VBA]

VBS[Decompiled VBA].deobfuscated.vbs

VBS[Full Diff]

VBS[Partial Diff]

BIN_VBA_PROJECT

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.

5 / 5

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

Shape ole:doc>bin

malicious 2 nodes

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

Shape ole:doc>ole:vba

malicious 2 nodes

Trace COM ordonnée UNKNWOWNmalicious

line 4huhuhuhuhuhuhuhuhuhuhu

Trace COM ordonnée UNKNWOWNmalicious

line 2huhuhuhuhuhuhuhuhuhuhu

Full artefact values (URLs, paths, registry keys, scripts…) are available with Essential.

Unlock with Essential

	Module Name0
	Module1	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.
	ThisWorkbook	VBA Stomping ATT&CK T1564.007 Malicious Malicious Document Blacklist VBA 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.