Analysis
-
max time kernel
136s -
max time network
139s -
platform
windows10-2004_x64 -
resource
win10v2004-20240426-en -
resource tags
arch:x64arch:x86image:win10v2004-20240426-enlocale:en-usos:windows10-2004-x64system -
submitted
18-05-2024 02:09
Behavioral task
behavioral1
Sample
b2a9480f8f1f1c943e61edff78428bf13761ae9b442eb516de5a228d3c0232cb.exe
Resource
win7-20240221-en
General
-
Target
b2a9480f8f1f1c943e61edff78428bf13761ae9b442eb516de5a228d3c0232cb.exe
-
Size
1.1MB
-
MD5
0b09f7f9f53069928390292e6bd9e895
-
SHA1
8721a2bc14854db97efb153a2b94c3f3427cef50
-
SHA256
b2a9480f8f1f1c943e61edff78428bf13761ae9b442eb516de5a228d3c0232cb
-
SHA512
d35abfe5ab1d95534134739afff3fc6bdc36a35833ead92083b6da8649bee460b705dd131dc661b92878a6898f9f4673c78d0cf343e18c4798b7b12cc9a531be
-
SSDEEP
24576:zQ5aILMCfmAUjzX6xQt+4En+bcMHI+rMUx+N43XVZpFyI:E5aIwC+Agr6StVEnmcI+2zTyI
Malware Config
Signatures
-
KPOT Core Executable 1 IoCs
resource yara_rule behavioral2/files/0x0007000000023405-21.dat family_kpot -
Trickbot x86 loader 1 IoCs
Detected Trickbot's x86 loader that unpacks the x86 payload.
resource yara_rule behavioral2/memory/3524-15-0x0000000002270000-0x0000000002299000-memory.dmp trickbot_loader32 -
Executes dropped EXE 3 IoCs
pid Process 1596 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 2144 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 2368 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe -
Suspicious use of AdjustPrivilegeToken 2 IoCs
description pid Process Token: SeTcbPrivilege 2144 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe Token: SeTcbPrivilege 2368 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe -
Suspicious use of SetWindowsHookEx 4 IoCs
pid Process 3524 b2a9480f8f1f1c943e61edff78428bf13761ae9b442eb516de5a228d3c0232cb.exe 1596 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 2144 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 2368 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe -
Suspicious use of WriteProcessMemory 64 IoCs
description pid Process procid_target PID 3524 wrote to memory of 1596 3524 b2a9480f8f1f1c943e61edff78428bf13761ae9b442eb516de5a228d3c0232cb.exe 85 PID 3524 wrote to memory of 1596 3524 b2a9480f8f1f1c943e61edff78428bf13761ae9b442eb516de5a228d3c0232cb.exe 85 PID 3524 wrote to memory of 1596 3524 b2a9480f8f1f1c943e61edff78428bf13761ae9b442eb516de5a228d3c0232cb.exe 85 PID 1596 wrote to memory of 1684 1596 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 86 PID 1596 wrote to memory of 1684 1596 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 86 PID 1596 wrote to memory of 1684 1596 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 86 PID 1596 wrote to memory of 1684 1596 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 86 PID 1596 wrote to memory of 1684 1596 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 86 PID 1596 wrote to memory of 1684 1596 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 86 PID 1596 wrote to memory of 1684 1596 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 86 PID 1596 wrote to memory of 1684 1596 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 86 PID 1596 wrote to memory of 1684 1596 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 86 PID 1596 wrote to memory of 1684 1596 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 86 PID 1596 wrote to memory of 1684 1596 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 86 PID 1596 wrote to memory of 1684 1596 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 86 PID 1596 wrote to memory of 1684 1596 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 86 PID 1596 wrote to memory of 1684 1596 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 86 PID 1596 wrote to memory of 1684 1596 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 86 PID 1596 wrote to memory of 1684 1596 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 86 PID 1596 wrote to memory of 1684 1596 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 86 PID 1596 wrote to memory of 1684 1596 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 86 PID 1596 wrote to memory of 1684 1596 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 86 PID 1596 wrote to memory of 1684 1596 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 86 PID 1596 wrote to memory of 1684 1596 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 86 PID 1596 wrote to memory of 1684 1596 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 86 PID 1596 wrote to memory of 1684 1596 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 86 PID 1596 wrote to memory of 1684 1596 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 86 PID 1596 wrote to memory of 1684 1596 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 86 PID 1596 wrote to memory of 1684 1596 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 86 PID 2144 wrote to memory of 4992 2144 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 103 PID 2144 wrote to memory of 4992 2144 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 103 PID 2144 wrote to memory of 4992 2144 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 103 PID 2144 wrote to memory of 4992 2144 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 103 PID 2144 wrote to memory of 4992 2144 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 103 PID 2144 wrote to memory of 4992 2144 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 103 PID 2144 wrote to memory of 4992 2144 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 103 PID 2144 wrote to memory of 4992 2144 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 103 PID 2144 wrote to memory of 4992 2144 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 103 PID 2144 wrote to memory of 4992 2144 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 103 PID 2144 wrote to memory of 4992 2144 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 103 PID 2144 wrote to memory of 4992 2144 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 103 PID 2144 wrote to memory of 4992 2144 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 103 PID 2144 wrote to memory of 4992 2144 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 103 PID 2144 wrote to memory of 4992 2144 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 103 PID 2144 wrote to memory of 4992 2144 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 103 PID 2144 wrote to memory of 4992 2144 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 103 PID 2144 wrote to memory of 4992 2144 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 103 PID 2144 wrote to memory of 4992 2144 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 103 PID 2144 wrote to memory of 4992 2144 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 103 PID 2144 wrote to memory of 4992 2144 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 103 PID 2144 wrote to memory of 4992 2144 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 103 PID 2144 wrote to memory of 4992 2144 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 103 PID 2144 wrote to memory of 4992 2144 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 103 PID 2144 wrote to memory of 4992 2144 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 103 PID 2144 wrote to memory of 4992 2144 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 103 PID 2368 wrote to memory of 2628 2368 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 111 PID 2368 wrote to memory of 2628 2368 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 111 PID 2368 wrote to memory of 2628 2368 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 111 PID 2368 wrote to memory of 2628 2368 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 111 PID 2368 wrote to memory of 2628 2368 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 111 PID 2368 wrote to memory of 2628 2368 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 111 PID 2368 wrote to memory of 2628 2368 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 111 PID 2368 wrote to memory of 2628 2368 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 111 PID 2368 wrote to memory of 2628 2368 b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe 111 -
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\b2a9480f8f1f1c943e61edff78428bf13761ae9b442eb516de5a228d3c0232cb.exe"C:\Users\Admin\AppData\Local\Temp\b2a9480f8f1f1c943e61edff78428bf13761ae9b442eb516de5a228d3c0232cb.exe"1⤵
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:3524 -
C:\Users\Admin\AppData\Roaming\WinSocket\b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exeC:\Users\Admin\AppData\Roaming\WinSocket\b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe2⤵
- Executes dropped EXE
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:1596 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:1684
-
-
-
C:\Users\Admin\AppData\Roaming\WinSocket\b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exeC:\Users\Admin\AppData\Roaming\WinSocket\b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe1⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2144 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe2⤵PID:4992
-
-
C:\Users\Admin\AppData\Roaming\WinSocket\b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exeC:\Users\Admin\AppData\Roaming\WinSocket\b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe1⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2368 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe2⤵PID:2628
-
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
-
C:\Users\Admin\AppData\Roaming\WinSocket\b2a9490f9f1f1c943e71edff89429bf13871ae9b442eb617de6a229d3c0232cb.exe
Filesize1.1MB
MD50b09f7f9f53069928390292e6bd9e895
SHA18721a2bc14854db97efb153a2b94c3f3427cef50
SHA256b2a9480f8f1f1c943e61edff78428bf13761ae9b442eb516de5a228d3c0232cb
SHA512d35abfe5ab1d95534134739afff3fc6bdc36a35833ead92083b6da8649bee460b705dd131dc661b92878a6898f9f4673c78d0cf343e18c4798b7b12cc9a531be
-
Filesize
11KB
MD5ddd67322d5fb9fa63ded29ff420b9e59
SHA1f434047718cc87516bde36b5ea1a9f567e957e89
SHA25668493281f137f78f7c5d96b1b8a1b00deb40b1167e8d935bb4634b26d65bdcda
SHA512e664c23521004c7d34d8800e6c4483dac5486380d73cd3cefa92d1642e3e2cd08fa8e325941e1f85b1ee7c3e509ee9de712d181bbdddbd378728036e350d7a93