Deep Malware Analysis of 340172a45c4307d37c0f04730e790f1b | md5: 340172a45c4307d37c0f04730e790f1b | 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	340172a45c4307d37c0f04730e790f1b
Sha1	a2b9a3370c8a5c2a33565ec4c4c33e98d2a01052
Sha256	ded3b318c4b2ed761e6bcb307168ae49dcbfbe9f32a136d6babc131a0f986a2c
Sha384	60da4e8bdfdd94c7bf9801df77c999370bb3a4d772e5ec72f704b74804039861a9259c9e762b0b696e8ae1fb11f3cb3c
Sha512	5e170710d7c0724c0dd24ed7fa30c15fb1ff78109a290bcc6b5b1ac6cf3195a3917dee2791c015b29e6b4e8df977c288b4c1f8aa312bda8837496992363a89d1
SSDeep	12288:4LXSikyQ2BpjhV4GwL4aHoSAWTXS0mfkpmZLW45w05/dg++o:NifQ2Bp1VrDwnIImZLWWdg+t
TLSH	F4C42309C425ED6EDB178538A63D5C72FA012D958341FB7F34A0FA69627E08F43CA89D

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.

15 / 15

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