Malicious MS Office Document analysis – fc6095c6cfef

Ctrl + scroll to zoom · drag to pan

This sample is a 244.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: fc6095c6cfefef70ff331d2f8911581185b55bae2fe9d70750e769588033387d
MD5: aab36266f41c8ff7b492f6b725441f7b
Verdict: Malicious
File type: MS Office Document · 244.5 KB
MITRE ATT&CK: T1027 T1059.005 T1105

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

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

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 aab36266f41c8ff7b492f6b725441f7b Sha1 c9040812fa99d4bf845071e8ab2b701c07ba0786 Sha256 fc6095c6cfefef70ff331d2f8911581185b55bae2fe9d70750e769588033387d Sha384 c209d57e965124b0ec454aff4c650bc4d75e0ffe86d7a8c67d476c3ea9007f46b690c8272ba55c2d1ff0933bc563a066 Sha512 2b86d35c544d4d6ca463479ae0c1849db5682e1862b088a1a468be203a9e806044e9634bf4b58f4240734b315a7594907d96b43d7cf3bf273746eaa78b0c3547 SSDeep 6144:FxEtjPOtioVjDGUU1qfDlavx+W2QnALrQsHBGilkW8a+TJJp/vC7zoVmzV4ZeTYD:tkskWOlCAImZYMl TLSH 9734AD53B1528DC2D54C83F86D9787EA2F21EF09DA526FCB2150BF0EFB702928C1A125

17 malicious · 29 files

OFFaab36266f41c8ff7b492f6b725441f7b

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.

aab36266f41c8ff7b492f6b725441f7b

Overview

Summary by MalvaGPT

Characteristics

File Structure

Artefacts2

aab36266f41c8ff7b492f6b725441f7b (250.37 KB)

File Structure

Artefacts2