Analysis
-
max time kernel
142s -
max time network
147s -
platform
windows10-2004_x64 -
resource
win10v2004-20240508-en -
resource tags
arch:x64arch:x86image:win10v2004-20240508-enlocale:en-usos:windows10-2004-x64system -
submitted
17-05-2024 19:41
Behavioral task
behavioral1
Sample
259b731e27ccc3512e6ba8a4ac31cc7c7266ba2675cb25e61b6127ed51857cb7.exe
Resource
win7-20240508-en
General
-
Target
259b731e27ccc3512e6ba8a4ac31cc7c7266ba2675cb25e61b6127ed51857cb7.exe
-
Size
1.0MB
-
MD5
647fa2e74165743306ed5a8a79d4758f
-
SHA1
3e55567ced75c611ea19a23bb6c893ae34080a50
-
SHA256
259b731e27ccc3512e6ba8a4ac31cc7c7266ba2675cb25e61b6127ed51857cb7
-
SHA512
da33a72f52fd71210e3d80d322d61524dc41c311553700b9a41f66a3958b54e07798c22aa892c3b7bdcc851b123a578b37ec048d9da64e9d2a43afbe5d7258f6
-
SSDEEP
24576:zQ5aILMCfmAUjzX6xQ0+wCIygDsAUSM64:E5aIwC+Agr6SNJ
Malware Config
Signatures
-
KPOT Core Executable 1 IoCs
resource yara_rule behavioral2/files/0x00080000000233f6-21.dat family_kpot -
Trickbot x86 loader 1 IoCs
Detected Trickbot's x86 loader that unpacks the x86 payload.
resource yara_rule behavioral2/memory/4468-15-0x0000000002270000-0x0000000002299000-memory.dmp trickbot_loader32 -
Executes dropped EXE 3 IoCs
pid Process 2564 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 1500 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 5060 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe -
Suspicious use of AdjustPrivilegeToken 2 IoCs
description pid Process Token: SeTcbPrivilege 1500 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe Token: SeTcbPrivilege 5060 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe -
Suspicious use of SetWindowsHookEx 4 IoCs
pid Process 4468 259b731e27ccc3512e6ba8a4ac31cc7c7266ba2675cb25e61b6127ed51857cb7.exe 2564 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 1500 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 5060 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe -
Suspicious use of WriteProcessMemory 64 IoCs
description pid Process procid_target PID 4468 wrote to memory of 2564 4468 259b731e27ccc3512e6ba8a4ac31cc7c7266ba2675cb25e61b6127ed51857cb7.exe 82 PID 4468 wrote to memory of 2564 4468 259b731e27ccc3512e6ba8a4ac31cc7c7266ba2675cb25e61b6127ed51857cb7.exe 82 PID 4468 wrote to memory of 2564 4468 259b731e27ccc3512e6ba8a4ac31cc7c7266ba2675cb25e61b6127ed51857cb7.exe 82 PID 2564 wrote to memory of 3424 2564 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 83 PID 2564 wrote to memory of 3424 2564 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 83 PID 2564 wrote to memory of 3424 2564 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 83 PID 2564 wrote to memory of 3424 2564 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 83 PID 2564 wrote to memory of 3424 2564 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 83 PID 2564 wrote to memory of 3424 2564 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 83 PID 2564 wrote to memory of 3424 2564 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 83 PID 2564 wrote to memory of 3424 2564 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 83 PID 2564 wrote to memory of 3424 2564 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 83 PID 2564 wrote to memory of 3424 2564 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 83 PID 2564 wrote to memory of 3424 2564 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 83 PID 2564 wrote to memory of 3424 2564 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 83 PID 2564 wrote to memory of 3424 2564 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 83 PID 2564 wrote to memory of 3424 2564 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 83 PID 2564 wrote to memory of 3424 2564 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 83 PID 2564 wrote to memory of 3424 2564 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 83 PID 2564 wrote to memory of 3424 2564 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 83 PID 2564 wrote to memory of 3424 2564 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 83 PID 2564 wrote to memory of 3424 2564 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 83 PID 2564 wrote to memory of 3424 2564 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 83 PID 2564 wrote to memory of 3424 2564 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 83 PID 2564 wrote to memory of 3424 2564 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 83 PID 2564 wrote to memory of 3424 2564 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 83 PID 2564 wrote to memory of 3424 2564 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 83 PID 2564 wrote to memory of 3424 2564 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 83 PID 2564 wrote to memory of 3424 2564 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 83 PID 1500 wrote to memory of 3544 1500 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 101 PID 1500 wrote to memory of 3544 1500 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 101 PID 1500 wrote to memory of 3544 1500 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 101 PID 1500 wrote to memory of 3544 1500 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 101 PID 1500 wrote to memory of 3544 1500 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 101 PID 1500 wrote to memory of 3544 1500 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 101 PID 1500 wrote to memory of 3544 1500 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 101 PID 1500 wrote to memory of 3544 1500 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 101 PID 1500 wrote to memory of 3544 1500 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 101 PID 1500 wrote to memory of 3544 1500 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 101 PID 1500 wrote to memory of 3544 1500 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 101 PID 1500 wrote to memory of 3544 1500 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 101 PID 1500 wrote to memory of 3544 1500 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 101 PID 1500 wrote to memory of 3544 1500 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 101 PID 1500 wrote to memory of 3544 1500 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 101 PID 1500 wrote to memory of 3544 1500 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 101 PID 1500 wrote to memory of 3544 1500 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 101 PID 1500 wrote to memory of 3544 1500 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 101 PID 1500 wrote to memory of 3544 1500 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 101 PID 1500 wrote to memory of 3544 1500 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 101 PID 1500 wrote to memory of 3544 1500 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 101 PID 1500 wrote to memory of 3544 1500 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 101 PID 1500 wrote to memory of 3544 1500 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 101 PID 1500 wrote to memory of 3544 1500 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 101 PID 1500 wrote to memory of 3544 1500 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 101 PID 1500 wrote to memory of 3544 1500 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 101 PID 5060 wrote to memory of 1996 5060 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 110 PID 5060 wrote to memory of 1996 5060 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 110 PID 5060 wrote to memory of 1996 5060 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 110 PID 5060 wrote to memory of 1996 5060 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 110 PID 5060 wrote to memory of 1996 5060 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 110 PID 5060 wrote to memory of 1996 5060 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 110 PID 5060 wrote to memory of 1996 5060 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 110 PID 5060 wrote to memory of 1996 5060 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 110 PID 5060 wrote to memory of 1996 5060 269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe 110 -
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\259b731e27ccc3512e6ba8a4ac31cc7c7266ba2675cb25e61b6127ed51857cb7.exe"C:\Users\Admin\AppData\Local\Temp\259b731e27ccc3512e6ba8a4ac31cc7c7266ba2675cb25e61b6127ed51857cb7.exe"1⤵
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:4468 -
C:\Users\Admin\AppData\Roaming\WinSocket\269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exeC:\Users\Admin\AppData\Roaming\WinSocket\269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe2⤵
- Executes dropped EXE
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2564 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:3424
-
-
-
C:\Users\Admin\AppData\Roaming\WinSocket\269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exeC:\Users\Admin\AppData\Roaming\WinSocket\269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe1⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:1500 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe2⤵PID:3544
-
-
C:\Users\Admin\AppData\Roaming\WinSocket\269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exeC:\Users\Admin\AppData\Roaming\WinSocket\269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe1⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:5060 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe2⤵PID:1996
-
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
-
C:\Users\Admin\AppData\Roaming\WinSocket\269b831e28ccc3612e7ba9a4ac31cc8c8277ba2786cb26e71b7128ed61968cb8.exe
Filesize1.0MB
MD5647fa2e74165743306ed5a8a79d4758f
SHA13e55567ced75c611ea19a23bb6c893ae34080a50
SHA256259b731e27ccc3512e6ba8a4ac31cc7c7266ba2675cb25e61b6127ed51857cb7
SHA512da33a72f52fd71210e3d80d322d61524dc41c311553700b9a41f66a3958b54e07798c22aa892c3b7bdcc851b123a578b37ec048d9da64e9d2a43afbe5d7258f6
-
Filesize
51KB
MD5c49245ce4aaf4153582547a97cf6e546
SHA199b80f291615eba76e7eafc2b10603b3b692bd34
SHA25617e71dd7ed6704ac8bb0a65e66231cfcc8a032f82b22acea3c010a44d6560313
SHA51238615cc866ea85cb64121fc9af1f7ad9813aa1e2e81f2d18be8bf04268ebaaf8ccd6b2fae9459bbc350477175a9853890dfac4c27dc46c7f081ee3a14ea57624