3102bda0d4ab26577068e2d800d2334e28995e917b6b906bfec7d58704918d7e

Analysis

max time kernel
230s
max time network
254s
platform
windows10-2004_x64
resource
win10v2004-20220812-en
resource tags

arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system
submitted
02-10-2022 22:29

Sharing

Copy URL

Twitter E-mail

Report Analysis Logs

General

Target

3102bda0d4ab26577068e2d800d2334e28995e917b6b906bfec7d58704918d7e.exe
Size

210KB
MD5

02ca32931f38955fe7965a6c0486c2a0
SHA1

776ac4d8fdf33c32625ddcd0218d94cdadcfd25d
SHA256

3102bda0d4ab26577068e2d800d2334e28995e917b6b906bfec7d58704918d7e
SHA512

a976f8200fffd455d08c8ee985ae0fc9a9d58a09749ed03b6f99efb5c57a5fa6fd36dc86e02d6c21c347b1997c243dea4ab983e3db13e542cc4039f3cff2574b
SSDEEP

6144:Pd6VSTMCuhooHyJH5dPMGuMnuqKM9/rrp:oV2hz8GuMnuqx5

Score

6^/10

bootkit persistence

Malware Config

Signatures

Writes to the Master Boot Record (MBR) 1 TTPs 1 IoCs
Bootkits write to the MBR to gain persistence at a level below the operating system.
bootkit persistence

Bootkit
T1067

Processes:

3102bda0d4ab26577068e2d800d2334e28995e917b6b906bfec7d58704918d7e.exe

description ioc process

File opened for modification \??\PHYSICALDRIVE0 3102bda0d4ab26577068e2d800d2334e28995e917b6b906bfec7d58704918d7e.exe

description	ioc	process
File opened for modification	\??\PHYSICALDRIVE0	3102bda0d4ab26577068e2d800d2334e28995e917b6b906bfec7d58704918d7e.exe

Suspicious use of SetThreadContext 1 IoCs

Processes:

3102bda0d4ab26577068e2d800d2334e28995e917b6b906bfec7d58704918d7e.exe

description	pid	process	target process
PID 2064 set thread context of 4400	2064	3102bda0d4ab26577068e2d800d2334e28995e917b6b906bfec7d58704918d7e.exe	3102bda0d4ab26577068e2d800d2334e28995e917b6b906bfec7d58704918d7e.exe

Suspicious behavior: EnumeratesProcesses 2 IoCs

Processes:

3102bda0d4ab26577068e2d800d2334e28995e917b6b906bfec7d58704918d7e.exe

pid	process
2064	3102bda0d4ab26577068e2d800d2334e28995e917b6b906bfec7d58704918d7e.exe
2064	3102bda0d4ab26577068e2d800d2334e28995e917b6b906bfec7d58704918d7e.exe

Suspicious use of SetWindowsHookEx 4 IoCs

Processes:

3102bda0d4ab26577068e2d800d2334e28995e917b6b906bfec7d58704918d7e.exe

pid	process
2064	3102bda0d4ab26577068e2d800d2334e28995e917b6b906bfec7d58704918d7e.exe
2064	3102bda0d4ab26577068e2d800d2334e28995e917b6b906bfec7d58704918d7e.exe
2064	3102bda0d4ab26577068e2d800d2334e28995e917b6b906bfec7d58704918d7e.exe
2064	3102bda0d4ab26577068e2d800d2334e28995e917b6b906bfec7d58704918d7e.exe

Suspicious use of WriteProcessMemory 10 IoCs

Processes:

3102bda0d4ab26577068e2d800d2334e28995e917b6b906bfec7d58704918d7e.exe

description	pid	process	target process
PID 2064 wrote to memory of 4400	2064	3102bda0d4ab26577068e2d800d2334e28995e917b6b906bfec7d58704918d7e.exe	3102bda0d4ab26577068e2d800d2334e28995e917b6b906bfec7d58704918d7e.exe
PID 2064 wrote to memory of 4400	2064	3102bda0d4ab26577068e2d800d2334e28995e917b6b906bfec7d58704918d7e.exe	3102bda0d4ab26577068e2d800d2334e28995e917b6b906bfec7d58704918d7e.exe
PID 2064 wrote to memory of 4400	2064	3102bda0d4ab26577068e2d800d2334e28995e917b6b906bfec7d58704918d7e.exe	3102bda0d4ab26577068e2d800d2334e28995e917b6b906bfec7d58704918d7e.exe
PID 2064 wrote to memory of 4400	2064	3102bda0d4ab26577068e2d800d2334e28995e917b6b906bfec7d58704918d7e.exe	3102bda0d4ab26577068e2d800d2334e28995e917b6b906bfec7d58704918d7e.exe
PID 2064 wrote to memory of 4400	2064	3102bda0d4ab26577068e2d800d2334e28995e917b6b906bfec7d58704918d7e.exe	3102bda0d4ab26577068e2d800d2334e28995e917b6b906bfec7d58704918d7e.exe
PID 2064 wrote to memory of 4400	2064	3102bda0d4ab26577068e2d800d2334e28995e917b6b906bfec7d58704918d7e.exe	3102bda0d4ab26577068e2d800d2334e28995e917b6b906bfec7d58704918d7e.exe
PID 2064 wrote to memory of 4400	2064	3102bda0d4ab26577068e2d800d2334e28995e917b6b906bfec7d58704918d7e.exe	3102bda0d4ab26577068e2d800d2334e28995e917b6b906bfec7d58704918d7e.exe
PID 2064 wrote to memory of 4400	2064	3102bda0d4ab26577068e2d800d2334e28995e917b6b906bfec7d58704918d7e.exe	3102bda0d4ab26577068e2d800d2334e28995e917b6b906bfec7d58704918d7e.exe
PID 2064 wrote to memory of 4400	2064	3102bda0d4ab26577068e2d800d2334e28995e917b6b906bfec7d58704918d7e.exe	3102bda0d4ab26577068e2d800d2334e28995e917b6b906bfec7d58704918d7e.exe
PID 2064 wrote to memory of 4400	2064	3102bda0d4ab26577068e2d800d2334e28995e917b6b906bfec7d58704918d7e.exe	3102bda0d4ab26577068e2d800d2334e28995e917b6b906bfec7d58704918d7e.exe

C:\Users\Admin\AppData\Local\Temp\3102bda0d4ab26577068e2d800d2334e28995e917b6b906bfec7d58704918d7e.exe
"C:\Users\Admin\AppData\Local\Temp\3102bda0d4ab26577068e2d800d2334e28995e917b6b906bfec7d58704918d7e.exe"
1⤵
- Suspicious use of SetThreadContext
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2064

C:\Users\Admin\AppData\Local\Temp\3102bda0d4ab26577068e2d800d2334e28995e917b6b906bfec7d58704918d7e.exe
C:\Users\Admin\AppData\Local\Temp\3102bda0d4ab26577068e2d800d2334e28995e917b6b906bfec7d58704918d7e.exe
2⤵
- Writes to the Master Boot Record (MBR)
PID:4400

Network

MITRE ATT&CK Matrix ATT&CK v6

Initial Access

Execution

Persistence

Bootkit

T1067

Privilege Escalation

Defense Evasion

Credential Access

Discovery

Lateral Movement

Collection

Exfiltration

Command and Control

Impact

Replay Monitor

Loading Replay Monitor...

Downloads

memory/2064-134-0x0000000002AC0000-0x0000000002AC4000-memory.dmp

Filesize
16KB

Download
memory/4400-132-0x0000000000000000-mapping.dmp

Download
memory/4400-133-0x0000000000400000-0x00000000065A8000-memory.dmp

Filesize
97.7MB

Download
memory/4400-136-0x0000000000400000-0x00000000065A8000-memory.dmp

Filesize
97.7MB

Download
memory/4400-137-0x0000000000400000-0x0000000000419000-memory.dmp

Filesize
100KB

Download