Malicious MS Office Document analysis – b50cbccb1189

Ctrl + scroll to zoom · drag to pan

This sample is a 247.5 KB MS Office Document for which Malva.RE's static analysis did not establish a malicious verdict. Static analysis extracted 28 embedded or derived files. It matches 12 YARA rules. Observed behaviours map to MITRE ATT&CK T1027, T1059.005 and T1105. The file was analysed statically: it was parsed and decompiled, never executed.

SHA256: b50cbccb118983cef416958e90cb75d8c7dc2b4466f6687ca8916acdf5fcb450
MD5: dbc9e597e02bc10f17477cc4497ec17c
Verdict: Malicious
File type: MS Office Document · 247.5 KB
MITRE ATT&CK: T1027 T1059.005 T1105

Cite this report: https://app.malva.re/sha256/b50cbccb118983cef416958e90cb75d8c7dc2b4466f6687ca8916acdf5fcb450

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

253.44 KB · 253,440 B

First seen

2026-10-26 07:30 · 6 days ago

Last seen

2026-10-26 07:30 · 6 days ago

Last analysis

2026-10-26 07:30 · 6 days ago

Hashes

MD5 dbc9e597e02bc10f17477cc4497ec17c Sha1 d8ac2c4db3bb5896747fe5e9c18f6703f2627847 Sha256 b50cbccb118983cef416958e90cb75d8c7dc2b4466f6687ca8916acdf5fcb450 Sha384 9e00cb3fc8624abf4c145be2168327a931e2d03ca32d4e9af4715f00a10e55b6888a1c619e407b2ac4199661756ef247 Sha512 57cf20e7157e300e3aa4582293b8671b0d3a0c88d34267ed858d29cd719fc319401d691f865f21701c6aed9e04d18cedc67ee79f5ee04e89acbd8348b7998576 SSDeep 6144:7xEtjPOtioVjDGUU1qfDlavx+W2QnA1rQsHBGilkW8a+TJJp/vC7zoVmzV4ZeTYg:FkskWOlCAImZYMFY TLSH 4044AE53B1569DC2D50C83F46D9787E62F22EF09DA56AFCB2150BF0EFB702924C1A125

17 malicious · 29 files

OFFdbc9e597e02bc10f17477cc4497ec17c

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~T1564.007

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.

dbc9e597e02bc10f17477cc4497ec17c

Overview

Summary by MalvaGPT

Characteristics

File Structure

Artefacts2

dbc9e597e02bc10f17477cc4497ec17c (253.44 KB)

File Structure

Artefacts2