Deep Malware Analysis of 597719abd504b23e320fa06a291bd107 | md5: 597719abd504b23e320fa06a291bd107 | Office Document | VBA Stomping | ATT&CK T1564.007 | Malicious | Malicious Document | Blacklist VBA | DeObfuscated | VBScript | T1059.005 | Obfuscated | T1027 | SOS: 0.70 | COM Behavior Trace | 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

Hashes

MD5 597719abd504b23e320fa06a291bd107 Sha1 e545a9859c3e78a0ab7cb0f211b5f64e005ce226 Sha256 d19a948a2c1f353f3b2e9fa4e415cbaa835f4fb354b7f6b5cf6e3439d2ee9957 Sha384 5d818abdc412dab44b7a3ef8a13978c17c7a8cb4de84cb94441395d58474fd8350f75437b219db423b464c5296073287 Sha512 f49e15530ec0888c1b5aa02fbb750f2faf083f48760248f270d7d4317af8ded9c5d6d5a1c26372bf766292d95695334861a04c6d1dc25fce03fbdd0f17d4aed3 SSDeep 6144:9xEtjPOtioVjDGUU1qfDlavx+W2QnALrQsHBGilkW8a+TJJp/vC7zoVmzV4ZeTYD:lkskWOlCAImZYMl TLSH 1F34AD53B2529DC2D50C83F46E9787EA2F21EF19DA56AFCB2150BF4EFB702824C16125

18 malicious · 30 files

OFF597719abd504b23e320fa06a291bd107

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

VBS[Full Diff]

VBS[Full Diff].deobfuscated.vbs

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.

6 / 6

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.