Analysis
-
max time kernel
149s -
max time network
152s -
platform
windows10-2004_x64 -
resource
win10v2004-20240426-en -
resource tags
arch:x64arch:x86image:win10v2004-20240426-enlocale:en-usos:windows10-2004-x64system -
submitted
23-05-2024 01:23
Behavioral task
behavioral1
Sample
a58a792733884063d08ece9fa75c99e7cdfe5d0c1bb0d5a1f4ef203ff5b60744.exe
Resource
win7-20231129-en
General
-
Target
a58a792733884063d08ece9fa75c99e7cdfe5d0c1bb0d5a1f4ef203ff5b60744.exe
-
Size
1.6MB
-
MD5
0b54440728c218b809c865efde2be968
-
SHA1
620c868da0e65cf15bd0fc9ba1bf5dfe8221a5a8
-
SHA256
a58a792733884063d08ece9fa75c99e7cdfe5d0c1bb0d5a1f4ef203ff5b60744
-
SHA512
84108b95a985bd8cddccb121707c02c7d471da0d3cfc02e4b5963e126c40f5d97f8e42258b05d26b3510dd7d1aac91cc0807b6ba4b7079b518d6e8114bd14040
-
SSDEEP
24576:zQ5aILMCfmAUjzX6xQE4efQg3zNn+2jsvercPk9N4hVI3/BxL+XKHZjb//8ISgH4:E5aIwC+Agr6SqCPGC6HZkIT/b/U
Malware Config
Signatures
-
KPOT Core Executable 1 IoCs
resource yara_rule behavioral2/files/0x0007000000023418-21.dat family_kpot -
Trickbot x86 loader 1 IoCs
Detected Trickbot's x86 loader that unpacks the x86 payload.
resource yara_rule behavioral2/memory/3616-15-0x0000000002180000-0x00000000021A9000-memory.dmp trickbot_loader32 -
Executes dropped EXE 3 IoCs
pid Process 4880 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 4792 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 1540 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe -
Suspicious use of AdjustPrivilegeToken 2 IoCs
description pid Process Token: SeTcbPrivilege 4792 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe Token: SeTcbPrivilege 1540 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe -
Suspicious use of SetWindowsHookEx 4 IoCs
pid Process 3616 a58a792733884063d08ece9fa75c99e7cdfe5d0c1bb0d5a1f4ef203ff5b60744.exe 4880 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 4792 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 1540 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe -
Suspicious use of WriteProcessMemory 64 IoCs
description pid Process procid_target PID 3616 wrote to memory of 4880 3616 a58a792733884063d08ece9fa75c99e7cdfe5d0c1bb0d5a1f4ef203ff5b60744.exe 83 PID 3616 wrote to memory of 4880 3616 a58a792733884063d08ece9fa75c99e7cdfe5d0c1bb0d5a1f4ef203ff5b60744.exe 83 PID 3616 wrote to memory of 4880 3616 a58a792733884063d08ece9fa75c99e7cdfe5d0c1bb0d5a1f4ef203ff5b60744.exe 83 PID 4880 wrote to memory of 3508 4880 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 84 PID 4880 wrote to memory of 3508 4880 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 84 PID 4880 wrote to memory of 3508 4880 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 84 PID 4880 wrote to memory of 3508 4880 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 84 PID 4880 wrote to memory of 3508 4880 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 84 PID 4880 wrote to memory of 3508 4880 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 84 PID 4880 wrote to memory of 3508 4880 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 84 PID 4880 wrote to memory of 3508 4880 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 84 PID 4880 wrote to memory of 3508 4880 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 84 PID 4880 wrote to memory of 3508 4880 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 84 PID 4880 wrote to memory of 3508 4880 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 84 PID 4880 wrote to memory of 3508 4880 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 84 PID 4880 wrote to memory of 3508 4880 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 84 PID 4880 wrote to memory of 3508 4880 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 84 PID 4880 wrote to memory of 3508 4880 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 84 PID 4880 wrote to memory of 3508 4880 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 84 PID 4880 wrote to memory of 3508 4880 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 84 PID 4880 wrote to memory of 3508 4880 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 84 PID 4880 wrote to memory of 3508 4880 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 84 PID 4880 wrote to memory of 3508 4880 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 84 PID 4880 wrote to memory of 3508 4880 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 84 PID 4880 wrote to memory of 3508 4880 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 84 PID 4880 wrote to memory of 3508 4880 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 84 PID 4880 wrote to memory of 3508 4880 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 84 PID 4880 wrote to memory of 3508 4880 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 84 PID 4880 wrote to memory of 3508 4880 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 84 PID 4792 wrote to memory of 3664 4792 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 100 PID 4792 wrote to memory of 3664 4792 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 100 PID 4792 wrote to memory of 3664 4792 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 100 PID 4792 wrote to memory of 3664 4792 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 100 PID 4792 wrote to memory of 3664 4792 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 100 PID 4792 wrote to memory of 3664 4792 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 100 PID 4792 wrote to memory of 3664 4792 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 100 PID 4792 wrote to memory of 3664 4792 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 100 PID 4792 wrote to memory of 3664 4792 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 100 PID 4792 wrote to memory of 3664 4792 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 100 PID 4792 wrote to memory of 3664 4792 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 100 PID 4792 wrote to memory of 3664 4792 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 100 PID 4792 wrote to memory of 3664 4792 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 100 PID 4792 wrote to memory of 3664 4792 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 100 PID 4792 wrote to memory of 3664 4792 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 100 PID 4792 wrote to memory of 3664 4792 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 100 PID 4792 wrote to memory of 3664 4792 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 100 PID 4792 wrote to memory of 3664 4792 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 100 PID 4792 wrote to memory of 3664 4792 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 100 PID 4792 wrote to memory of 3664 4792 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 100 PID 4792 wrote to memory of 3664 4792 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 100 PID 4792 wrote to memory of 3664 4792 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 100 PID 4792 wrote to memory of 3664 4792 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 100 PID 4792 wrote to memory of 3664 4792 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 100 PID 4792 wrote to memory of 3664 4792 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 100 PID 4792 wrote to memory of 3664 4792 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 100 PID 1540 wrote to memory of 4016 1540 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 109 PID 1540 wrote to memory of 4016 1540 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 109 PID 1540 wrote to memory of 4016 1540 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 109 PID 1540 wrote to memory of 4016 1540 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 109 PID 1540 wrote to memory of 4016 1540 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 109 PID 1540 wrote to memory of 4016 1540 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 109 PID 1540 wrote to memory of 4016 1540 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 109 PID 1540 wrote to memory of 4016 1540 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 109 PID 1540 wrote to memory of 4016 1540 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 109 -
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\a58a792733884063d08ece9fa75c99e7cdfe5d0c1bb0d5a1f4ef203ff5b60744.exe"C:\Users\Admin\AppData\Local\Temp\a58a792733884063d08ece9fa75c99e7cdfe5d0c1bb0d5a1f4ef203ff5b60744.exe"1⤵
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:3616 -
C:\Users\Admin\AppData\Roaming\WinSocket\a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exeC:\Users\Admin\AppData\Roaming\WinSocket\a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe2⤵
- Executes dropped EXE
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:4880 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:3508
-
-
-
C:\Users\Admin\AppData\Roaming\WinSocket\a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exeC:\Users\Admin\AppData\Roaming\WinSocket\a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe1⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:4792 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe2⤵PID:3664
-
-
C:\Users\Admin\AppData\Roaming\WinSocket\a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exeC:\Users\Admin\AppData\Roaming\WinSocket\a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe1⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:1540 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe2⤵PID:4016
-
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
-
C:\Users\Admin\AppData\Roaming\WinSocket\a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe
Filesize1.6MB
MD50b54440728c218b809c865efde2be968
SHA1620c868da0e65cf15bd0fc9ba1bf5dfe8221a5a8
SHA256a58a792733884063d08ece9fa75c99e7cdfe5d0c1bb0d5a1f4ef203ff5b60744
SHA51284108b95a985bd8cddccb121707c02c7d471da0d3cfc02e4b5963e126c40f5d97f8e42258b05d26b3510dd7d1aac91cc0807b6ba4b7079b518d6e8114bd14040
-
Filesize
61KB
MD5843165d8e3a68cf997e17fceaff743b1
SHA10c726014ae828bef536e2e8250aa6113c5cd15ea
SHA256afb3b6b0d0257fddc709dc3032ba9cb42ca8d6ccf92ee1d08c652024bdaefeae
SHA512d5182283898e89b56c01a99a9675c70c03ff0dfba3df7d95afa77e9ed7fa4b12924f7865332e8f5f7b2f6692500d74f0397d1a0b9d291dd0dcc5de6b2ccb2a33