Analysis
-
max time kernel
149s -
max time network
152s -
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 21:43
Behavioral task
behavioral1
Sample
4d23b60ec48e9f6fac3efacc25f5978f0d4ec2fbdd4410f16685f8e2d8830850.exe
Resource
win7-20240215-en
General
-
Target
4d23b60ec48e9f6fac3efacc25f5978f0d4ec2fbdd4410f16685f8e2d8830850.exe
-
Size
1.5MB
-
MD5
34fc400c62b2218cc536b3e2104d3085
-
SHA1
02cf6b268ad52001119b41f4a4bfb867c67238a4
-
SHA256
4d23b60ec48e9f6fac3efacc25f5978f0d4ec2fbdd4410f16685f8e2d8830850
-
SHA512
f6d4d280fd7eac9789afc4743241272db745fdd5d61d4d4c8bf2778b2accd9b1814dcd6efb1ed6caf977ffe8969f97fc4b301d89a50b843941e051978d898c4d
-
SSDEEP
24576:zQ5aILMCfmAUjzX677WOMcT/X2dI7T2FAoUcUOp6doF5ES/okoOdH:E5aIwC+Agr6tdlmU1/eohQ
Malware Config
Signatures
-
KPOT Core Executable 1 IoCs
resource yara_rule behavioral2/files/0x000700000002342a-21.dat family_kpot -
Trickbot x86 loader 1 IoCs
Detected Trickbot's x86 loader that unpacks the x86 payload.
resource yara_rule behavioral2/memory/4764-15-0x0000000002FF0000-0x0000000003019000-memory.dmp trickbot_loader32 -
Executes dropped EXE 3 IoCs
pid Process 4000 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 1800 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 2712 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe -
Suspicious use of AdjustPrivilegeToken 2 IoCs
description pid Process Token: SeTcbPrivilege 1800 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe Token: SeTcbPrivilege 2712 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe -
Suspicious use of SetWindowsHookEx 4 IoCs
pid Process 4764 4d23b60ec48e9f6fac3efacc25f5978f0d4ec2fbdd4410f16685f8e2d8830850.exe 4000 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 1800 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 2712 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe -
Suspicious use of WriteProcessMemory 64 IoCs
description pid Process procid_target PID 4764 wrote to memory of 4000 4764 4d23b60ec48e9f6fac3efacc25f5978f0d4ec2fbdd4410f16685f8e2d8830850.exe 83 PID 4764 wrote to memory of 4000 4764 4d23b60ec48e9f6fac3efacc25f5978f0d4ec2fbdd4410f16685f8e2d8830850.exe 83 PID 4764 wrote to memory of 4000 4764 4d23b60ec48e9f6fac3efacc25f5978f0d4ec2fbdd4410f16685f8e2d8830850.exe 83 PID 4000 wrote to memory of 4324 4000 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 84 PID 4000 wrote to memory of 4324 4000 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 84 PID 4000 wrote to memory of 4324 4000 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 84 PID 4000 wrote to memory of 4324 4000 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 84 PID 4000 wrote to memory of 4324 4000 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 84 PID 4000 wrote to memory of 4324 4000 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 84 PID 4000 wrote to memory of 4324 4000 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 84 PID 4000 wrote to memory of 4324 4000 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 84 PID 4000 wrote to memory of 4324 4000 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 84 PID 4000 wrote to memory of 4324 4000 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 84 PID 4000 wrote to memory of 4324 4000 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 84 PID 4000 wrote to memory of 4324 4000 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 84 PID 4000 wrote to memory of 4324 4000 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 84 PID 4000 wrote to memory of 4324 4000 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 84 PID 4000 wrote to memory of 4324 4000 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 84 PID 4000 wrote to memory of 4324 4000 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 84 PID 4000 wrote to memory of 4324 4000 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 84 PID 4000 wrote to memory of 4324 4000 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 84 PID 4000 wrote to memory of 4324 4000 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 84 PID 4000 wrote to memory of 4324 4000 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 84 PID 4000 wrote to memory of 4324 4000 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 84 PID 4000 wrote to memory of 4324 4000 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 84 PID 4000 wrote to memory of 4324 4000 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 84 PID 4000 wrote to memory of 4324 4000 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 84 PID 4000 wrote to memory of 4324 4000 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 84 PID 4000 wrote to memory of 4324 4000 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 84 PID 1800 wrote to memory of 2224 1800 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 98 PID 1800 wrote to memory of 2224 1800 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 98 PID 1800 wrote to memory of 2224 1800 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 98 PID 1800 wrote to memory of 2224 1800 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 98 PID 1800 wrote to memory of 2224 1800 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 98 PID 1800 wrote to memory of 2224 1800 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 98 PID 1800 wrote to memory of 2224 1800 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 98 PID 1800 wrote to memory of 2224 1800 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 98 PID 1800 wrote to memory of 2224 1800 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 98 PID 1800 wrote to memory of 2224 1800 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 98 PID 1800 wrote to memory of 2224 1800 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 98 PID 1800 wrote to memory of 2224 1800 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 98 PID 1800 wrote to memory of 2224 1800 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 98 PID 1800 wrote to memory of 2224 1800 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 98 PID 1800 wrote to memory of 2224 1800 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 98 PID 1800 wrote to memory of 2224 1800 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 98 PID 1800 wrote to memory of 2224 1800 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 98 PID 1800 wrote to memory of 2224 1800 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 98 PID 1800 wrote to memory of 2224 1800 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 98 PID 1800 wrote to memory of 2224 1800 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 98 PID 1800 wrote to memory of 2224 1800 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 98 PID 1800 wrote to memory of 2224 1800 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 98 PID 1800 wrote to memory of 2224 1800 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 98 PID 1800 wrote to memory of 2224 1800 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 98 PID 1800 wrote to memory of 2224 1800 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 98 PID 1800 wrote to memory of 2224 1800 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 98 PID 2712 wrote to memory of 3832 2712 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 108 PID 2712 wrote to memory of 3832 2712 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 108 PID 2712 wrote to memory of 3832 2712 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 108 PID 2712 wrote to memory of 3832 2712 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 108 PID 2712 wrote to memory of 3832 2712 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 108 PID 2712 wrote to memory of 3832 2712 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 108 PID 2712 wrote to memory of 3832 2712 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 108 PID 2712 wrote to memory of 3832 2712 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 108 PID 2712 wrote to memory of 3832 2712 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 108 -
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\4d23b60ec48e9f6fac3efacc25f5978f0d4ec2fbdd4410f16685f8e2d8830850.exe"C:\Users\Admin\AppData\Local\Temp\4d23b60ec48e9f6fac3efacc25f5978f0d4ec2fbdd4410f16685f8e2d8830850.exe"1⤵
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:4764 -
C:\Users\Admin\AppData\Roaming\WinSocket\4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exeC:\Users\Admin\AppData\Roaming\WinSocket\4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe2⤵
- Executes dropped EXE
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:4000 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:4324
-
-
-
C:\Users\Admin\AppData\Roaming\WinSocket\4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exeC:\Users\Admin\AppData\Roaming\WinSocket\4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe1⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:1800 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe2⤵PID:2224
-
-
C:\Users\Admin\AppData\Roaming\WinSocket\4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exeC:\Users\Admin\AppData\Roaming\WinSocket\4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe1⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2712 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe2⤵PID:3832
-
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
-
C:\Users\Admin\AppData\Roaming\WinSocket\4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe
Filesize1.5MB
MD534fc400c62b2218cc536b3e2104d3085
SHA102cf6b268ad52001119b41f4a4bfb867c67238a4
SHA2564d23b60ec48e9f6fac3efacc25f5978f0d4ec2fbdd4410f16685f8e2d8830850
SHA512f6d4d280fd7eac9789afc4743241272db745fdd5d61d4d4c8bf2778b2accd9b1814dcd6efb1ed6caf977ffe8969f97fc4b301d89a50b843941e051978d898c4d
-
Filesize
25KB
MD5ac91ec356828c9e143410fb04735ddfb
SHA103583f9b292df2b7a40e82cad8a696671296d8ee
SHA2562367dd05efcefa5d229bd45dfa62b772666905fb3e5e11d0ab3aa702617c2bab
SHA512a0b074dd2e46940f9ca73ef88db7b08f55534dd86f1d9ed419187a7d84079e335c0ba3872b356d8358e79b35f418e451051c0e8d517514f5853687eec29549b0