Analysis
-
max time kernel
137s -
max time network
129s -
platform
windows10-2004_x64 -
resource
win10v2004-20240426-en -
resource tags
arch:x64arch:x86image:win10v2004-20240426-enlocale:en-usos:windows10-2004-x64system -
submitted
19-05-2024 10:38
Behavioral task
behavioral1
Sample
72cebf37d27ac7210a756eb9f6180a9bb6153b9cf887550e303f17e6b9573f13.exe
Resource
win7-20240221-en
General
-
Target
72cebf37d27ac7210a756eb9f6180a9bb6153b9cf887550e303f17e6b9573f13.exe
-
Size
1.1MB
-
MD5
060c16ffab2baf7d36ce23605c8433f0
-
SHA1
912093cdd6e04b4269a014208e8c1a603a006845
-
SHA256
72cebf37d27ac7210a756eb9f6180a9bb6153b9cf887550e303f17e6b9573f13
-
SHA512
bf63034bb9f94d0b51c44c13c281517b42988d232b01a80981d8fddc8f5e23581bfdfbecafff70a30696fb4212cdfa6bcd966d35cc8fb6a2f76b9b75c7e85902
-
SSDEEP
24576:zQ5aILMCfmAUjzX6xQt+4En+bcMHI+rMUx+N43XVZpFy/my:E5aIwC+Agr6StVEnmcI+2zTy/h
Malware Config
Signatures
-
KPOT Core Executable 1 IoCs
resource yara_rule behavioral2/files/0x0007000000023424-21.dat family_kpot -
Trickbot x86 loader 1 IoCs
Detected Trickbot's x86 loader that unpacks the x86 payload.
resource yara_rule behavioral2/memory/2208-15-0x0000000002180000-0x00000000021A9000-memory.dmp trickbot_loader32 -
Executes dropped EXE 3 IoCs
pid Process 4104 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 3992 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 5092 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe -
Suspicious use of AdjustPrivilegeToken 2 IoCs
description pid Process Token: SeTcbPrivilege 3992 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe Token: SeTcbPrivilege 5092 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe -
Suspicious use of SetWindowsHookEx 4 IoCs
pid Process 2208 72cebf37d27ac7210a756eb9f6180a9bb6153b9cf887550e303f17e6b9573f13.exe 4104 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 3992 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 5092 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe -
Suspicious use of WriteProcessMemory 64 IoCs
description pid Process procid_target PID 2208 wrote to memory of 4104 2208 72cebf37d27ac7210a756eb9f6180a9bb6153b9cf887550e303f17e6b9573f13.exe 83 PID 2208 wrote to memory of 4104 2208 72cebf37d27ac7210a756eb9f6180a9bb6153b9cf887550e303f17e6b9573f13.exe 83 PID 2208 wrote to memory of 4104 2208 72cebf37d27ac7210a756eb9f6180a9bb6153b9cf887550e303f17e6b9573f13.exe 83 PID 4104 wrote to memory of 3456 4104 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 84 PID 4104 wrote to memory of 3456 4104 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 84 PID 4104 wrote to memory of 3456 4104 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 84 PID 4104 wrote to memory of 3456 4104 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 84 PID 4104 wrote to memory of 3456 4104 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 84 PID 4104 wrote to memory of 3456 4104 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 84 PID 4104 wrote to memory of 3456 4104 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 84 PID 4104 wrote to memory of 3456 4104 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 84 PID 4104 wrote to memory of 3456 4104 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 84 PID 4104 wrote to memory of 3456 4104 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 84 PID 4104 wrote to memory of 3456 4104 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 84 PID 4104 wrote to memory of 3456 4104 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 84 PID 4104 wrote to memory of 3456 4104 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 84 PID 4104 wrote to memory of 3456 4104 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 84 PID 4104 wrote to memory of 3456 4104 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 84 PID 4104 wrote to memory of 3456 4104 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 84 PID 4104 wrote to memory of 3456 4104 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 84 PID 4104 wrote to memory of 3456 4104 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 84 PID 4104 wrote to memory of 3456 4104 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 84 PID 4104 wrote to memory of 3456 4104 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 84 PID 4104 wrote to memory of 3456 4104 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 84 PID 4104 wrote to memory of 3456 4104 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 84 PID 4104 wrote to memory of 3456 4104 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 84 PID 4104 wrote to memory of 3456 4104 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 84 PID 4104 wrote to memory of 3456 4104 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 84 PID 4104 wrote to memory of 3456 4104 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 84 PID 3992 wrote to memory of 2336 3992 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 101 PID 3992 wrote to memory of 2336 3992 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 101 PID 3992 wrote to memory of 2336 3992 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 101 PID 3992 wrote to memory of 2336 3992 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 101 PID 3992 wrote to memory of 2336 3992 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 101 PID 3992 wrote to memory of 2336 3992 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 101 PID 3992 wrote to memory of 2336 3992 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 101 PID 3992 wrote to memory of 2336 3992 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 101 PID 3992 wrote to memory of 2336 3992 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 101 PID 3992 wrote to memory of 2336 3992 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 101 PID 3992 wrote to memory of 2336 3992 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 101 PID 3992 wrote to memory of 2336 3992 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 101 PID 3992 wrote to memory of 2336 3992 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 101 PID 3992 wrote to memory of 2336 3992 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 101 PID 3992 wrote to memory of 2336 3992 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 101 PID 3992 wrote to memory of 2336 3992 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 101 PID 3992 wrote to memory of 2336 3992 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 101 PID 3992 wrote to memory of 2336 3992 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 101 PID 3992 wrote to memory of 2336 3992 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 101 PID 3992 wrote to memory of 2336 3992 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 101 PID 3992 wrote to memory of 2336 3992 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 101 PID 3992 wrote to memory of 2336 3992 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 101 PID 3992 wrote to memory of 2336 3992 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 101 PID 3992 wrote to memory of 2336 3992 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 101 PID 3992 wrote to memory of 2336 3992 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 101 PID 3992 wrote to memory of 2336 3992 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 101 PID 5092 wrote to memory of 4568 5092 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 110 PID 5092 wrote to memory of 4568 5092 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 110 PID 5092 wrote to memory of 4568 5092 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 110 PID 5092 wrote to memory of 4568 5092 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 110 PID 5092 wrote to memory of 4568 5092 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 110 PID 5092 wrote to memory of 4568 5092 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 110 PID 5092 wrote to memory of 4568 5092 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 110 PID 5092 wrote to memory of 4568 5092 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe 110 PID 5092 wrote to memory of 4568 5092 82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.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\72cebf37d27ac7210a756eb9f6180a9bb6153b9cf887550e303f17e6b9573f13.exe"C:\Users\Admin\AppData\Local\Temp\72cebf37d27ac7210a756eb9f6180a9bb6153b9cf887550e303f17e6b9573f13.exe"1⤵
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2208 -
C:\Users\Admin\AppData\Roaming\WinSocket\82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exeC:\Users\Admin\AppData\Roaming\WinSocket\82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe2⤵
- Executes dropped EXE
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:4104 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:3456
-
-
-
C:\Users\Admin\AppData\Roaming\WinSocket\82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exeC:\Users\Admin\AppData\Roaming\WinSocket\82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe1⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:3992 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe2⤵PID:2336
-
-
C:\Users\Admin\AppData\Roaming\WinSocket\82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exeC:\Users\Admin\AppData\Roaming\WinSocket\82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe1⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:5092 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe2⤵PID:4568
-
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
-
C:\Users\Admin\AppData\Roaming\WinSocket\82cebf38d28ac8210a867eb9f7190a9bb7163b9cf998660e303f18e7b9683f13.exe
Filesize1.1MB
MD5060c16ffab2baf7d36ce23605c8433f0
SHA1912093cdd6e04b4269a014208e8c1a603a006845
SHA25672cebf37d27ac7210a756eb9f6180a9bb6153b9cf887550e303f17e6b9573f13
SHA512bf63034bb9f94d0b51c44c13c281517b42988d232b01a80981d8fddc8f5e23581bfdfbecafff70a30696fb4212cdfa6bcd966d35cc8fb6a2f76b9b75c7e85902
-
Filesize
34KB
MD5e48a558ba575114c21faac81a02fe9de
SHA101922090f9c87d86103c02390a1523411eaf3ec3
SHA25663a07681d1f4c261e9f697a7c228b48a612615e37a96a2efc4ea184cadf94c66
SHA51232193ac4b88cff1d968d8d4c209f13f0b63f23d7be7d87a4cb8455b611f2cd012ceae72921d5ffe65f3035db12342a6c866db32e1480050d67ee1307a2b6d4af