Deep Malware Analysis of 4f347eb4b084d1bbee63c916ac926135 | md5: 4f347eb4b084d1bbee63c916ac926135 | Office Document | VBA Stomping | ATT&CK T1564.007 | Malicious | Malicious Document | Blacklist VBA | T1059.005 | Shell.Application | DeObfuscated | VBScript | Obfuscated | T1027 | Excel.sheet | Scripting.FileSystemObject

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.

MD5	4f347eb4b084d1bbee63c916ac926135
Sha1	9b329f33cfc7a855fa96bf0727b92f6de46c6034
Sha256	ad807ab50dc5b8f77c25c8752d18f1d5cc2153bc7175a6d1bc73ecf740cd28a7
Sha384	7b621e7b541f47d066c03824f1f0ab9175110824ee0102f9e2064db18d07e9697ab603479473db19c72a7302ee2ba455
Sha512	b137af6b08202da84cb7327e37bb6b9ca9e9101227eb70e946e73c8cb4be840a664ec23360256349b2e990389ea56a101b71c32a357db03084c4eeccafebb5af
SSDeep	12288:tLani8ZEoIWkIW/j2Myi4JnI058hSCl6isWvk95/dg+02:UitvWKi+4JnI0bCljsWOdg+Z
TLSH	F8C4233ADD3DFCACC21B1D7CA21E685948062E896242FB9B3851F5CC7F911DA4B8C61C

CSHA256

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.

14 / 14

Path oox:xlsm~T1027~T1059.005~T1564.007>oox:media>img

Shape oox:xlsm>oox:media>img

malicious 3 nodes

Path oox:xlsm~T1027~T1059.005~T1564.007>bin

Shape oox:xlsm>bin

malicious 2 nodes

	Module Name0
	CSHA256	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.
	Sheet17	VBA Macro