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
251.9 KB · 251,904 B
First seen
2026-10-25 14:30 · 40 minutes ago
Last seen
2026-10-25 14:30 · 40 minutes ago
Last analysis
2026-10-25 14:30 · 40 minutes ago
Hashes
MD5 392aa3e89971dfb2d4bdda87e283484f Sha1 2e62fcf3681b61264db3cf6db2d4a00d137da429 Sha256 3aa30f06226f74ac5d99e3893a5b819ddbde990861469a950aca84e78dee36e8 Sha384 fa1d86082eb74633007618c481ea65b42c204255248b41a7e94d5f436fda07478645c31970b24ac02cc988361a70cd3c Sha512 daec04d4e8723fee21706225c7d9d4cc29f9ed72d4f22de4d6cff4e0db190d3f02f9814b6a499296435cd8420d5c5b0b521344e58546d2161c05d7b6bcf665b7 SSDeep 6144:KxEtjPOtioVjDGUU1qfDlavx+W2QnALrQsHBGilkW8a+TJJp/vC7zoVmzV4ZeTYS:AkskWOlCAImZYMt TLSH C034AD53B1529DC2D54C83F96E9787EA2F22EF05DA566FCB2150BF0EFB702424C16225
17 malicious · 29 files
OFF392aa3e89971dfb2d4bdda87e283484f
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 3huhuhuhuhuhuhuhuhuhuhu
Trace COM ordonnée UNKNWOWNmalicious
line 1huhuhuhuhuhuhuhuhuhuhu
Full artefact values (URLs, paths, registry keys, scripts…) are available with Essential.
Unlock with Essential
17 malicious · 29 files
OFF392aa3e89971dfb2d4bdda87e283484f
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

vbaDNA - VBA Stomping & Purging Stategy detection

Module Name
Module1
VBA Stomping
ATT&CK T1564.007
Malicious
Malicious Document
VBA Macro

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

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.

No malware configuration was found at this point.
Trace COM ordonnée UNKNWOWNmalicious
line 3huhuhuhuhuhuhuhuhuhuhu
392aa3e89971dfb2d4bdda87e283484f › Root Entry › _VBA_PROJECT_CUR › VBA › ThisWorkbook › [Decompiled VBA]
Trace COM ordonnée UNKNWOWNmalicious
line 1huhuhuhuhuhuhuhuhuhuhu
392aa3e89971dfb2d4bdda87e283484f › Root Entry › _VBA_PROJECT_CUR › VBA › ThisWorkbook › [Stored VBA]
Full artefact values (URLs, paths, registry keys, scripts…) are available with Essential.
Unlock with Essential
You must be signed in to view YARA rules.
An error has occurred. This application may no longer respond until reloaded. Reload 🗙