Analysis
-
max time kernel
148s -
max time network
161s -
platform
windows10-2004_x64 -
resource
win10v2004-20240508-en -
resource tags
arch:x64arch:x86image:win10v2004-20240508-enlocale:en-usos:windows10-2004-x64system -
submitted
02-06-2024 00:37
Behavioral task
behavioral1
Sample
9c7c25055db19708c4cd137c67c1c569fad69e37bb86263d46dbe54fbb3cd2df.exe
Resource
win7-20240419-en
General
-
Target
9c7c25055db19708c4cd137c67c1c569fad69e37bb86263d46dbe54fbb3cd2df.exe
-
Size
1002KB
-
MD5
8b532e3a92eb3dc5f617ac5380ea8767
-
SHA1
d9f36a0d5bf4b024f14740db2a679f05ac195be5
-
SHA256
9c7c25055db19708c4cd137c67c1c569fad69e37bb86263d46dbe54fbb3cd2df
-
SHA512
a1f8463d78b529894e14ef2a9ddb666a32eceb53fe3d91493e49965ed6295492dfd257f8ffa55a97de16d5b1283ed689dfac4e7830ff1dc6c8f6abdce4053160
-
SSDEEP
24576:zQ5aILMCfmAUjzX6xQ0+wCIygDsAUSTsU9C:E5aIwC+Agr6SNas3
Malware Config
Signatures
-
KPOT Core Executable 1 IoCs
resource yara_rule behavioral2/files/0x000700000002342d-21.dat family_kpot -
Trickbot x86 loader 1 IoCs
Detected Trickbot's x86 loader that unpacks the x86 payload.
resource yara_rule behavioral2/memory/660-15-0x0000000002B10000-0x0000000002B39000-memory.dmp trickbot_loader32 -
Executes dropped EXE 3 IoCs
pid Process 2160 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 3264 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 3132 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe -
Suspicious use of AdjustPrivilegeToken 2 IoCs
description pid Process Token: SeTcbPrivilege 3264 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe Token: SeTcbPrivilege 3132 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe -
Suspicious use of SetWindowsHookEx 4 IoCs
pid Process 660 9c7c25055db19708c4cd137c67c1c569fad69e37bb86263d46dbe54fbb3cd2df.exe 2160 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 3264 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 3132 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe -
Suspicious use of WriteProcessMemory 64 IoCs
description pid Process procid_target PID 660 wrote to memory of 2160 660 9c7c25055db19708c4cd137c67c1c569fad69e37bb86263d46dbe54fbb3cd2df.exe 83 PID 660 wrote to memory of 2160 660 9c7c25055db19708c4cd137c67c1c569fad69e37bb86263d46dbe54fbb3cd2df.exe 83 PID 660 wrote to memory of 2160 660 9c7c25055db19708c4cd137c67c1c569fad69e37bb86263d46dbe54fbb3cd2df.exe 83 PID 2160 wrote to memory of 1748 2160 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 84 PID 2160 wrote to memory of 1748 2160 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 84 PID 2160 wrote to memory of 1748 2160 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 84 PID 2160 wrote to memory of 1748 2160 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 84 PID 2160 wrote to memory of 1748 2160 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 84 PID 2160 wrote to memory of 1748 2160 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 84 PID 2160 wrote to memory of 1748 2160 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 84 PID 2160 wrote to memory of 1748 2160 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 84 PID 2160 wrote to memory of 1748 2160 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 84 PID 2160 wrote to memory of 1748 2160 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 84 PID 2160 wrote to memory of 1748 2160 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 84 PID 2160 wrote to memory of 1748 2160 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 84 PID 2160 wrote to memory of 1748 2160 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 84 PID 2160 wrote to memory of 1748 2160 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 84 PID 2160 wrote to memory of 1748 2160 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 84 PID 2160 wrote to memory of 1748 2160 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 84 PID 2160 wrote to memory of 1748 2160 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 84 PID 2160 wrote to memory of 1748 2160 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 84 PID 2160 wrote to memory of 1748 2160 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 84 PID 2160 wrote to memory of 1748 2160 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 84 PID 2160 wrote to memory of 1748 2160 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 84 PID 2160 wrote to memory of 1748 2160 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 84 PID 2160 wrote to memory of 1748 2160 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 84 PID 2160 wrote to memory of 1748 2160 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 84 PID 2160 wrote to memory of 1748 2160 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 84 PID 2160 wrote to memory of 1748 2160 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 84 PID 3264 wrote to memory of 2840 3264 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 99 PID 3264 wrote to memory of 2840 3264 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 99 PID 3264 wrote to memory of 2840 3264 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 99 PID 3264 wrote to memory of 2840 3264 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 99 PID 3264 wrote to memory of 2840 3264 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 99 PID 3264 wrote to memory of 2840 3264 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 99 PID 3264 wrote to memory of 2840 3264 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 99 PID 3264 wrote to memory of 2840 3264 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 99 PID 3264 wrote to memory of 2840 3264 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 99 PID 3264 wrote to memory of 2840 3264 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 99 PID 3264 wrote to memory of 2840 3264 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 99 PID 3264 wrote to memory of 2840 3264 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 99 PID 3264 wrote to memory of 2840 3264 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 99 PID 3264 wrote to memory of 2840 3264 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 99 PID 3264 wrote to memory of 2840 3264 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 99 PID 3264 wrote to memory of 2840 3264 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 99 PID 3264 wrote to memory of 2840 3264 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 99 PID 3264 wrote to memory of 2840 3264 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 99 PID 3264 wrote to memory of 2840 3264 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 99 PID 3264 wrote to memory of 2840 3264 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 99 PID 3264 wrote to memory of 2840 3264 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 99 PID 3264 wrote to memory of 2840 3264 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 99 PID 3264 wrote to memory of 2840 3264 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 99 PID 3264 wrote to memory of 2840 3264 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 99 PID 3264 wrote to memory of 2840 3264 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 99 PID 3264 wrote to memory of 2840 3264 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 99 PID 3132 wrote to memory of 3148 3132 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 110 PID 3132 wrote to memory of 3148 3132 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 110 PID 3132 wrote to memory of 3148 3132 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 110 PID 3132 wrote to memory of 3148 3132 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 110 PID 3132 wrote to memory of 3148 3132 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 110 PID 3132 wrote to memory of 3148 3132 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 110 PID 3132 wrote to memory of 3148 3132 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 110 PID 3132 wrote to memory of 3148 3132 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe 110 PID 3132 wrote to memory of 3148 3132 9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.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\9c7c25055db19708c4cd137c67c1c569fad69e37bb86263d46dbe54fbb3cd2df.exe"C:\Users\Admin\AppData\Local\Temp\9c7c25055db19708c4cd137c67c1c569fad69e37bb86263d46dbe54fbb3cd2df.exe"1⤵
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:660 -
C:\Users\Admin\AppData\Roaming\WinSocket\9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exeC:\Users\Admin\AppData\Roaming\WinSocket\9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe2⤵
- Executes dropped EXE
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2160 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:1748
-
-
-
C:\Users\Admin\AppData\Roaming\WinSocket\9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exeC:\Users\Admin\AppData\Roaming\WinSocket\9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe1⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:3264 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe2⤵PID:2840
-
-
C:\Users\Admin\AppData\Roaming\WinSocket\9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exeC:\Users\Admin\AppData\Roaming\WinSocket\9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe1⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:3132 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe2⤵PID:3148
-
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
-
C:\Users\Admin\AppData\Roaming\WinSocket\9c8c26066db19809c4cd138c78c1c679fad79e38bb97273d47dbe64fbb3cd2df.exe
Filesize1002KB
MD58b532e3a92eb3dc5f617ac5380ea8767
SHA1d9f36a0d5bf4b024f14740db2a679f05ac195be5
SHA2569c7c25055db19708c4cd137c67c1c569fad69e37bb86263d46dbe54fbb3cd2df
SHA512a1f8463d78b529894e14ef2a9ddb666a32eceb53fe3d91493e49965ed6295492dfd257f8ffa55a97de16d5b1283ed689dfac4e7830ff1dc6c8f6abdce4053160
-
Filesize
41KB
MD59abb14f6fb6d56074157f0df6572afab
SHA127fc8da43e2f404e7d7af2bc11b725b44a5dad2c
SHA256969aed4ee6d693a5beec96f604a49a7763423a8e97f866aa54d9069297bf0f71
SHA51206d573bd51f0d33dc97788412f2ec93bfea5e18de5e063627c85c5e37ab91d75e5bfe77ff257fd92f55e28dfcaae052c7d2089f188c71d1c690f75380a454f01