Analysis
-
max time kernel
135s -
max time network
136s -
platform
windows10-2004_x64 -
resource
win10v2004-20240419-en -
resource tags
arch:x64arch:x86image:win10v2004-20240419-enlocale:en-usos:windows10-2004-x64system -
submitted
05/05/2024, 21:05
Behavioral task
behavioral1
Sample
42755e0fbbf9c46c82c1777d4068e32ffa36c3c4b5f6e3580094286f8985f9f2.exe
Resource
win7-20240215-en
General
-
Target
42755e0fbbf9c46c82c1777d4068e32ffa36c3c4b5f6e3580094286f8985f9f2.exe
-
Size
1.3MB
-
MD5
2f99d51a67ac96a6132b73e558c036ff
-
SHA1
3228f440838a43bf7863d99438d9c288dd3ee8a6
-
SHA256
42755e0fbbf9c46c82c1777d4068e32ffa36c3c4b5f6e3580094286f8985f9f2
-
SHA512
f80971069f357a691a639b675b399ac2bc80e62a85aec188168232dc9c84ffcd76f52cd173c5e039994d587fdd62ec3848782746999c3d8eece21f323f823fc2
-
SSDEEP
24576:zQ5aILMCfmAUjzX677WOMc7qzz1IojVD0UOSQCM0:E5aIwC+Agr6twjVDT
Malware Config
Signatures
-
KPOT Core Executable 1 IoCs
resource yara_rule behavioral2/files/0x000a000000023ba8-21.dat family_kpot -
Trickbot x86 loader 1 IoCs
Detected Trickbot's x86 loader that unpacks the x86 payload.
resource yara_rule behavioral2/memory/1648-15-0x0000000002270000-0x0000000002299000-memory.dmp trickbot_loader32 -
Executes dropped EXE 3 IoCs
pid Process 4356 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 4316 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 696 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe -
Suspicious use of AdjustPrivilegeToken 2 IoCs
description pid Process Token: SeTcbPrivilege 4316 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe Token: SeTcbPrivilege 696 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe -
Suspicious use of SetWindowsHookEx 4 IoCs
pid Process 1648 42755e0fbbf9c46c82c1777d4068e32ffa36c3c4b5f6e3580094286f8985f9f2.exe 4356 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 4316 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 696 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe -
Suspicious use of WriteProcessMemory 64 IoCs
description pid Process procid_target PID 1648 wrote to memory of 4356 1648 42755e0fbbf9c46c82c1777d4068e32ffa36c3c4b5f6e3580094286f8985f9f2.exe 85 PID 1648 wrote to memory of 4356 1648 42755e0fbbf9c46c82c1777d4068e32ffa36c3c4b5f6e3580094286f8985f9f2.exe 85 PID 1648 wrote to memory of 4356 1648 42755e0fbbf9c46c82c1777d4068e32ffa36c3c4b5f6e3580094286f8985f9f2.exe 85 PID 4356 wrote to memory of 3268 4356 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 86 PID 4356 wrote to memory of 3268 4356 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 86 PID 4356 wrote to memory of 3268 4356 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 86 PID 4356 wrote to memory of 3268 4356 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 86 PID 4356 wrote to memory of 3268 4356 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 86 PID 4356 wrote to memory of 3268 4356 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 86 PID 4356 wrote to memory of 3268 4356 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 86 PID 4356 wrote to memory of 3268 4356 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 86 PID 4356 wrote to memory of 3268 4356 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 86 PID 4356 wrote to memory of 3268 4356 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 86 PID 4356 wrote to memory of 3268 4356 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 86 PID 4356 wrote to memory of 3268 4356 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 86 PID 4356 wrote to memory of 3268 4356 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 86 PID 4356 wrote to memory of 3268 4356 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 86 PID 4356 wrote to memory of 3268 4356 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 86 PID 4356 wrote to memory of 3268 4356 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 86 PID 4356 wrote to memory of 3268 4356 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 86 PID 4356 wrote to memory of 3268 4356 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 86 PID 4356 wrote to memory of 3268 4356 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 86 PID 4356 wrote to memory of 3268 4356 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 86 PID 4356 wrote to memory of 3268 4356 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 86 PID 4356 wrote to memory of 3268 4356 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 86 PID 4356 wrote to memory of 3268 4356 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 86 PID 4356 wrote to memory of 3268 4356 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 86 PID 4356 wrote to memory of 3268 4356 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 86 PID 4356 wrote to memory of 3268 4356 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 86 PID 4316 wrote to memory of 3656 4316 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 103 PID 4316 wrote to memory of 3656 4316 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 103 PID 4316 wrote to memory of 3656 4316 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 103 PID 4316 wrote to memory of 3656 4316 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 103 PID 4316 wrote to memory of 3656 4316 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 103 PID 4316 wrote to memory of 3656 4316 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 103 PID 4316 wrote to memory of 3656 4316 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 103 PID 4316 wrote to memory of 3656 4316 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 103 PID 4316 wrote to memory of 3656 4316 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 103 PID 4316 wrote to memory of 3656 4316 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 103 PID 4316 wrote to memory of 3656 4316 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 103 PID 4316 wrote to memory of 3656 4316 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 103 PID 4316 wrote to memory of 3656 4316 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 103 PID 4316 wrote to memory of 3656 4316 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 103 PID 4316 wrote to memory of 3656 4316 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 103 PID 4316 wrote to memory of 3656 4316 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 103 PID 4316 wrote to memory of 3656 4316 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 103 PID 4316 wrote to memory of 3656 4316 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 103 PID 4316 wrote to memory of 3656 4316 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 103 PID 4316 wrote to memory of 3656 4316 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 103 PID 4316 wrote to memory of 3656 4316 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 103 PID 4316 wrote to memory of 3656 4316 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 103 PID 4316 wrote to memory of 3656 4316 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 103 PID 4316 wrote to memory of 3656 4316 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 103 PID 4316 wrote to memory of 3656 4316 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 103 PID 4316 wrote to memory of 3656 4316 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 103 PID 696 wrote to memory of 1128 696 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 112 PID 696 wrote to memory of 1128 696 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 112 PID 696 wrote to memory of 1128 696 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 112 PID 696 wrote to memory of 1128 696 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 112 PID 696 wrote to memory of 1128 696 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 112 PID 696 wrote to memory of 1128 696 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 112 PID 696 wrote to memory of 1128 696 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 112 PID 696 wrote to memory of 1128 696 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 112 PID 696 wrote to memory of 1128 696 42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe 112 -
Uses Task Scheduler COM API 1 TTPs
The Task Scheduler COM API can be used to schedule applications to run on boot or at set times.
Processes
-
C:\Users\Admin\AppData\Local\Temp\42755e0fbbf9c46c82c1777d4068e32ffa36c3c4b5f6e3580094286f8985f9f2.exe"C:\Users\Admin\AppData\Local\Temp\42755e0fbbf9c46c82c1777d4068e32ffa36c3c4b5f6e3580094286f8985f9f2.exe"1⤵
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:1648 -
C:\Users\Admin\AppData\Roaming\WinSocket\42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exeC:\Users\Admin\AppData\Roaming\WinSocket\42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe2⤵
- Executes dropped EXE
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:4356 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:3268
-
-
-
C:\Users\Admin\AppData\Roaming\WinSocket\42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exeC:\Users\Admin\AppData\Roaming\WinSocket\42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe1⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:4316 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe2⤵PID:3656
-
-
C:\Users\Admin\AppData\Roaming\WinSocket\42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exeC:\Users\Admin\AppData\Roaming\WinSocket\42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe1⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:696 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe2⤵PID:1128
-
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
-
C:\Users\Admin\AppData\Roaming\WinSocket\42866e0fbbf9c47c92c1888d4079e32ffa37c3c4b6f7e3690094297f9996f9f2.exe
Filesize1.3MB
MD52f99d51a67ac96a6132b73e558c036ff
SHA13228f440838a43bf7863d99438d9c288dd3ee8a6
SHA25642755e0fbbf9c46c82c1777d4068e32ffa36c3c4b5f6e3580094286f8985f9f2
SHA512f80971069f357a691a639b675b399ac2bc80e62a85aec188168232dc9c84ffcd76f52cd173c5e039994d587fdd62ec3848782746999c3d8eece21f323f823fc2
-
Filesize
45KB
MD55dd2378e95ef199bc0eb41b2b67ce926
SHA1fc54d68a78a0bcdc2a995c8e6c731d14224458be
SHA256ecf3331ebb0448a78f5c3389e593d1b9d2bb6e0e840ca688fa5f8331cbb2ecff
SHA512ed535049b135f224a76155bfc4b19f17b1e03c51361635ae2d44a304061cb18876a6d8190bfb935c40ad76d7e1b9aa396b530874b614353ab4e822a124c8036b