Analysis
-
max time kernel
137s -
max time network
128s -
platform
windows10-2004_x64 -
resource
win10v2004-20240419-en -
resource tags
arch:x64arch:x86image:win10v2004-20240419-enlocale:en-usos:windows10-2004-x64system -
submitted
04/05/2024, 01:04
Behavioral task
behavioral1
Sample
9e4e42cf36a70195dcd5ac6c57dae6868d9ee0616097319681a30cee28f208e1.exe
Resource
win7-20240221-en
General
-
Target
9e4e42cf36a70195dcd5ac6c57dae6868d9ee0616097319681a30cee28f208e1.exe
-
Size
1.1MB
-
MD5
5db3ab3ad40e5fcfd755fea0a1728d78
-
SHA1
fd9904dceae0eacabcb2a1aae9120d221bfafd84
-
SHA256
9e4e42cf36a70195dcd5ac6c57dae6868d9ee0616097319681a30cee28f208e1
-
SHA512
31a9299e765814775e3f7ba6d0b8cca30b31931594327278af308e77830d91b2ac3f018e97c0e92984d4b05e601412af1faddd5c52b7c0a66e4324a424cf12af
-
SSDEEP
24576:zQ5aILMCfmAUjzX6xQGCZLFdGm1StE10/ZcnDPsc:E5aIwC+Agr6S/FFC+Lsc
Malware Config
Signatures
-
KPOT Core Executable 1 IoCs
resource yara_rule behavioral2/files/0x000a000000023b8a-21.dat family_kpot -
Trickbot x86 loader 1 IoCs
Detected Trickbot's x86 loader that unpacks the x86 payload.
resource yara_rule behavioral2/memory/392-15-0x0000000002AB0000-0x0000000002AD9000-memory.dmp trickbot_loader32 -
Executes dropped EXE 3 IoCs
pid Process 4260 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 3876 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 4112 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe -
Suspicious use of AdjustPrivilegeToken 2 IoCs
description pid Process Token: SeTcbPrivilege 3876 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe Token: SeTcbPrivilege 4112 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe -
Suspicious use of SetWindowsHookEx 4 IoCs
pid Process 392 9e4e42cf36a70195dcd5ac6c57dae6868d9ee0616097319681a30cee28f208e1.exe 4260 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 3876 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 4112 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe -
Suspicious use of WriteProcessMemory 64 IoCs
description pid Process procid_target PID 392 wrote to memory of 4260 392 9e4e42cf36a70195dcd5ac6c57dae6868d9ee0616097319681a30cee28f208e1.exe 83 PID 392 wrote to memory of 4260 392 9e4e42cf36a70195dcd5ac6c57dae6868d9ee0616097319681a30cee28f208e1.exe 83 PID 392 wrote to memory of 4260 392 9e4e42cf36a70195dcd5ac6c57dae6868d9ee0616097319681a30cee28f208e1.exe 83 PID 4260 wrote to memory of 4324 4260 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 84 PID 4260 wrote to memory of 4324 4260 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 84 PID 4260 wrote to memory of 4324 4260 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 84 PID 4260 wrote to memory of 4324 4260 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 84 PID 4260 wrote to memory of 4324 4260 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 84 PID 4260 wrote to memory of 4324 4260 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 84 PID 4260 wrote to memory of 4324 4260 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 84 PID 4260 wrote to memory of 4324 4260 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 84 PID 4260 wrote to memory of 4324 4260 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 84 PID 4260 wrote to memory of 4324 4260 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 84 PID 4260 wrote to memory of 4324 4260 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 84 PID 4260 wrote to memory of 4324 4260 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 84 PID 4260 wrote to memory of 4324 4260 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 84 PID 4260 wrote to memory of 4324 4260 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 84 PID 4260 wrote to memory of 4324 4260 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 84 PID 4260 wrote to memory of 4324 4260 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 84 PID 4260 wrote to memory of 4324 4260 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 84 PID 4260 wrote to memory of 4324 4260 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 84 PID 4260 wrote to memory of 4324 4260 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 84 PID 4260 wrote to memory of 4324 4260 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 84 PID 4260 wrote to memory of 4324 4260 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 84 PID 4260 wrote to memory of 4324 4260 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 84 PID 4260 wrote to memory of 4324 4260 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 84 PID 4260 wrote to memory of 4324 4260 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 84 PID 4260 wrote to memory of 4324 4260 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 84 PID 4260 wrote to memory of 4324 4260 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 84 PID 3876 wrote to memory of 444 3876 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 101 PID 3876 wrote to memory of 444 3876 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 101 PID 3876 wrote to memory of 444 3876 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 101 PID 3876 wrote to memory of 444 3876 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 101 PID 3876 wrote to memory of 444 3876 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 101 PID 3876 wrote to memory of 444 3876 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 101 PID 3876 wrote to memory of 444 3876 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 101 PID 3876 wrote to memory of 444 3876 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 101 PID 3876 wrote to memory of 444 3876 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 101 PID 3876 wrote to memory of 444 3876 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 101 PID 3876 wrote to memory of 444 3876 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 101 PID 3876 wrote to memory of 444 3876 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 101 PID 3876 wrote to memory of 444 3876 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 101 PID 3876 wrote to memory of 444 3876 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 101 PID 3876 wrote to memory of 444 3876 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 101 PID 3876 wrote to memory of 444 3876 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 101 PID 3876 wrote to memory of 444 3876 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 101 PID 3876 wrote to memory of 444 3876 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 101 PID 3876 wrote to memory of 444 3876 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 101 PID 3876 wrote to memory of 444 3876 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 101 PID 3876 wrote to memory of 444 3876 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 101 PID 3876 wrote to memory of 444 3876 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 101 PID 3876 wrote to memory of 444 3876 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 101 PID 3876 wrote to memory of 444 3876 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 101 PID 3876 wrote to memory of 444 3876 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 101 PID 3876 wrote to memory of 444 3876 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 101 PID 4112 wrote to memory of 4548 4112 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 114 PID 4112 wrote to memory of 4548 4112 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 114 PID 4112 wrote to memory of 4548 4112 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 114 PID 4112 wrote to memory of 4548 4112 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 114 PID 4112 wrote to memory of 4548 4112 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 114 PID 4112 wrote to memory of 4548 4112 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 114 PID 4112 wrote to memory of 4548 4112 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 114 PID 4112 wrote to memory of 4548 4112 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 114 PID 4112 wrote to memory of 4548 4112 9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe 114 -
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\9e4e42cf36a70195dcd5ac6c57dae6868d9ee0616097319681a30cee28f208e1.exe"C:\Users\Admin\AppData\Local\Temp\9e4e42cf36a70195dcd5ac6c57dae6868d9ee0616097319681a30cee28f208e1.exe"1⤵
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:392 -
C:\Users\Admin\AppData\Roaming\WinSocket\9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exeC:\Users\Admin\AppData\Roaming\WinSocket\9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe2⤵
- Executes dropped EXE
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:4260 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:4324
-
-
-
C:\Users\Admin\AppData\Roaming\WinSocket\9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exeC:\Users\Admin\AppData\Roaming\WinSocket\9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe1⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:3876 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe2⤵PID:444
-
-
C:\Users\Admin\AppData\Roaming\WinSocket\9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exeC:\Users\Admin\AppData\Roaming\WinSocket\9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe1⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:4112 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe2⤵PID:4548
-
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
-
C:\Users\Admin\AppData\Roaming\WinSocket\9e4e42cf37a80196dcd6ac7c68dae7979d9ee0717098319791a30cee29f209e1.exe
Filesize1.1MB
MD55db3ab3ad40e5fcfd755fea0a1728d78
SHA1fd9904dceae0eacabcb2a1aae9120d221bfafd84
SHA2569e4e42cf36a70195dcd5ac6c57dae6868d9ee0616097319681a30cee28f208e1
SHA51231a9299e765814775e3f7ba6d0b8cca30b31931594327278af308e77830d91b2ac3f018e97c0e92984d4b05e601412af1faddd5c52b7c0a66e4324a424cf12af
-
Filesize
89KB
MD5c6cf76c32f4abf12714328ce65577db2
SHA19e666c3176d083ba55cbd91b38db9ac9a56284d0
SHA25666ef70046d572ff301034eaa7e99d2e1d933b1214c0afab9ed8d8e18ba14d1b6
SHA512b07615e0d15cba46510fd1d69e6f05b3b5b8a48d0262e254e26a7dcbf782ba2422ac5fcbe5c825df538d76a9fd70676192c5842ceb851106272555644a6b3837