Analysis
-
max time kernel
142s -
max time network
129s -
platform
windows10-2004_x64 -
resource
win10v2004-20240709-en -
resource tags
arch:x64arch:x86image:win10v2004-20240709-enlocale:en-usos:windows10-2004-x64system -
submitted
22-07-2024 23:58
Behavioral task
behavioral1
Sample
8ada05908f3b6cf8b10cdab402ab94640ecbafce939ac3900c2de5d2d04a2960.exe
Resource
win7-20240704-en
General
-
Target
8ada05908f3b6cf8b10cdab402ab94640ecbafce939ac3900c2de5d2d04a2960.exe
-
Size
1.1MB
-
MD5
db18dc0521f75378e278255bddbb6dc8
-
SHA1
f582540d5b67c8e1a01b9668a4a57aeda24b54ad
-
SHA256
8ada05908f3b6cf8b10cdab402ab94640ecbafce939ac3900c2de5d2d04a2960
-
SHA512
7dced98627725b2819e053a9befc5791c4fbbe601e30bf6caf7849004c24126b6c1c2f0d3ff1f87dd869822af71d5000e5b1571cac8524817f440ed55353076f
-
SSDEEP
24576:zQ5aILMCfmAUjzX6xQ0+wCIygDsAUSTsU9+s8juCCmr:E5aIwC+Agr6SNasrsFCb
Malware Config
Signatures
-
KPOT Core Executable 1 IoCs
resource yara_rule behavioral2/files/0x00070000000234e1-21.dat family_kpot -
Trickbot x86 loader 1 IoCs
Detected Trickbot's x86 loader that unpacks the x86 payload.
resource yara_rule behavioral2/memory/3584-15-0x0000000002180000-0x00000000021A9000-memory.dmp trickbot_loader32 -
Executes dropped EXE 3 IoCs
pid Process 4764 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 312 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 2064 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe -
Suspicious use of AdjustPrivilegeToken 2 IoCs
description pid Process Token: SeTcbPrivilege 312 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe Token: SeTcbPrivilege 2064 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe -
Suspicious use of SetWindowsHookEx 4 IoCs
pid Process 3584 8ada05908f3b6cf8b10cdab402ab94640ecbafce939ac3900c2de5d2d04a2960.exe 4764 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 312 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 2064 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe -
Suspicious use of WriteProcessMemory 64 IoCs
description pid Process procid_target PID 3584 wrote to memory of 4764 3584 8ada05908f3b6cf8b10cdab402ab94640ecbafce939ac3900c2de5d2d04a2960.exe 84 PID 3584 wrote to memory of 4764 3584 8ada05908f3b6cf8b10cdab402ab94640ecbafce939ac3900c2de5d2d04a2960.exe 84 PID 3584 wrote to memory of 4764 3584 8ada05908f3b6cf8b10cdab402ab94640ecbafce939ac3900c2de5d2d04a2960.exe 84 PID 4764 wrote to memory of 4572 4764 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 86 PID 4764 wrote to memory of 4572 4764 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 86 PID 4764 wrote to memory of 4572 4764 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 86 PID 4764 wrote to memory of 4572 4764 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 86 PID 4764 wrote to memory of 4572 4764 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 86 PID 4764 wrote to memory of 4572 4764 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 86 PID 4764 wrote to memory of 4572 4764 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 86 PID 4764 wrote to memory of 4572 4764 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 86 PID 4764 wrote to memory of 4572 4764 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 86 PID 4764 wrote to memory of 4572 4764 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 86 PID 4764 wrote to memory of 4572 4764 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 86 PID 4764 wrote to memory of 4572 4764 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 86 PID 4764 wrote to memory of 4572 4764 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 86 PID 4764 wrote to memory of 4572 4764 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 86 PID 4764 wrote to memory of 4572 4764 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 86 PID 4764 wrote to memory of 4572 4764 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 86 PID 4764 wrote to memory of 4572 4764 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 86 PID 4764 wrote to memory of 4572 4764 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 86 PID 4764 wrote to memory of 4572 4764 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 86 PID 4764 wrote to memory of 4572 4764 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 86 PID 4764 wrote to memory of 4572 4764 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 86 PID 4764 wrote to memory of 4572 4764 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 86 PID 4764 wrote to memory of 4572 4764 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 86 PID 4764 wrote to memory of 4572 4764 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 86 PID 4764 wrote to memory of 4572 4764 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 86 PID 4764 wrote to memory of 4572 4764 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 86 PID 312 wrote to memory of 1844 312 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 100 PID 312 wrote to memory of 1844 312 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 100 PID 312 wrote to memory of 1844 312 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 100 PID 312 wrote to memory of 1844 312 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 100 PID 312 wrote to memory of 1844 312 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 100 PID 312 wrote to memory of 1844 312 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 100 PID 312 wrote to memory of 1844 312 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 100 PID 312 wrote to memory of 1844 312 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 100 PID 312 wrote to memory of 1844 312 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 100 PID 312 wrote to memory of 1844 312 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 100 PID 312 wrote to memory of 1844 312 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 100 PID 312 wrote to memory of 1844 312 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 100 PID 312 wrote to memory of 1844 312 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 100 PID 312 wrote to memory of 1844 312 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 100 PID 312 wrote to memory of 1844 312 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 100 PID 312 wrote to memory of 1844 312 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 100 PID 312 wrote to memory of 1844 312 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 100 PID 312 wrote to memory of 1844 312 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 100 PID 312 wrote to memory of 1844 312 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 100 PID 312 wrote to memory of 1844 312 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 100 PID 312 wrote to memory of 1844 312 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 100 PID 312 wrote to memory of 1844 312 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 100 PID 312 wrote to memory of 1844 312 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 100 PID 312 wrote to memory of 1844 312 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 100 PID 312 wrote to memory of 1844 312 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 100 PID 312 wrote to memory of 1844 312 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 100 PID 2064 wrote to memory of 5112 2064 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 107 PID 2064 wrote to memory of 5112 2064 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 107 PID 2064 wrote to memory of 5112 2064 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 107 PID 2064 wrote to memory of 5112 2064 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 107 PID 2064 wrote to memory of 5112 2064 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 107 PID 2064 wrote to memory of 5112 2064 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 107 PID 2064 wrote to memory of 5112 2064 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 107 PID 2064 wrote to memory of 5112 2064 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 107 PID 2064 wrote to memory of 5112 2064 9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe 107 -
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\8ada05908f3b6cf8b10cdab402ab94640ecbafce939ac3900c2de5d2d04a2960.exe"C:\Users\Admin\AppData\Local\Temp\8ada05908f3b6cf8b10cdab402ab94640ecbafce939ac3900c2de5d2d04a2960.exe"1⤵
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:3584 -
C:\Users\Admin\AppData\Roaming\WinSocket\9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exeC:\Users\Admin\AppData\Roaming\WinSocket\9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe2⤵
- Executes dropped EXE
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:4764 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:4572
-
-
-
C:\Users\Admin\AppData\Roaming\WinSocket\9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exeC:\Users\Admin\AppData\Roaming\WinSocket\9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe1⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:312 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe2⤵PID:1844
-
-
C:\Users\Admin\AppData\Roaming\WinSocket\9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exeC:\Users\Admin\AppData\Roaming\WinSocket\9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe1⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2064 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe2⤵PID:5112
-
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
-
C:\Users\Admin\AppData\Roaming\WinSocket\9ada06909f3b7cf9b10cdab402ab94740ecbafce939ac3900c2de6d2d04a2970.exe
Filesize1.1MB
MD5db18dc0521f75378e278255bddbb6dc8
SHA1f582540d5b67c8e1a01b9668a4a57aeda24b54ad
SHA2568ada05908f3b6cf8b10cdab402ab94640ecbafce939ac3900c2de5d2d04a2960
SHA5127dced98627725b2819e053a9befc5791c4fbbe601e30bf6caf7849004c24126b6c1c2f0d3ff1f87dd869822af71d5000e5b1571cac8524817f440ed55353076f
-
Filesize
59KB
MD558836433c5f449006a3a6fbe411bc65d
SHA17b910a9326b3087bee950978fb28033614e1ceaf
SHA25664ce3474ea44c9c764b6d72d0c3d381a700fb6cb86ce3f8f0d595258e4422fe9
SHA512c9d0f4b86fca8e5b76ef302b239ab6ef156839c43a47099401b24632027bab62294e0a9a90a2e0cc08392f6d84f5686194708d1169d2c36fde253049c0b30db1