Analysis
-
max time kernel
135s -
max time network
121s -
platform
windows7_x64 -
resource
win7-20240215-en -
resource tags
arch:x64arch:x86image:win7-20240215-enlocale:en-usos:windows7-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 behavioral1/files/0x0008000000015cf5-20.dat family_kpot -
Trickbot x86 loader 1 IoCs
Detected Trickbot's x86 loader that unpacks the x86 payload.
resource yara_rule behavioral1/memory/2268-15-0x0000000002390000-0x00000000023B9000-memory.dmp trickbot_loader32 -
Executes dropped EXE 3 IoCs
pid Process 2608 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 384 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 1036 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe -
Loads dropped DLL 2 IoCs
pid Process 2268 4d23b60ec48e9f6fac3efacc25f5978f0d4ec2fbdd4410f16685f8e2d8830850.exe 2268 4d23b60ec48e9f6fac3efacc25f5978f0d4ec2fbdd4410f16685f8e2d8830850.exe -
Drops file in System32 directory 2 IoCs
description ioc Process File opened for modification C:\Windows\SysWOW64\%ProgramData%\Microsoft\Windows\Start Menu\Programs\Accessories\Windows PowerShell\Windows PowerShell.lnk powershell.exe File opened for modification C:\Windows\SysWOW64\%ProgramData%\Microsoft\Windows\Start Menu\Programs\Accessories\Windows PowerShell\Windows PowerShell.lnk powershell.exe -
Launches sc.exe 4 IoCs
Sc.exe is a Windows utlilty to control services on the system.
pid Process 2552 sc.exe 2320 sc.exe 2016 sc.exe 2532 sc.exe -
Suspicious behavior: EnumeratesProcesses 8 IoCs
pid Process 2268 4d23b60ec48e9f6fac3efacc25f5978f0d4ec2fbdd4410f16685f8e2d8830850.exe 2268 4d23b60ec48e9f6fac3efacc25f5978f0d4ec2fbdd4410f16685f8e2d8830850.exe 2268 4d23b60ec48e9f6fac3efacc25f5978f0d4ec2fbdd4410f16685f8e2d8830850.exe 2608 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 2608 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 2608 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 2412 powershell.exe 2280 powershell.exe -
Suspicious use of AdjustPrivilegeToken 4 IoCs
description pid Process Token: SeDebugPrivilege 2412 powershell.exe Token: SeDebugPrivilege 2280 powershell.exe Token: SeTcbPrivilege 384 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe Token: SeTcbPrivilege 1036 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe -
Suspicious use of SetWindowsHookEx 4 IoCs
pid Process 2268 4d23b60ec48e9f6fac3efacc25f5978f0d4ec2fbdd4410f16685f8e2d8830850.exe 2608 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 384 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 1036 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe -
Suspicious use of WriteProcessMemory 64 IoCs
description pid Process procid_target PID 2268 wrote to memory of 2948 2268 4d23b60ec48e9f6fac3efacc25f5978f0d4ec2fbdd4410f16685f8e2d8830850.exe 28 PID 2268 wrote to memory of 2948 2268 4d23b60ec48e9f6fac3efacc25f5978f0d4ec2fbdd4410f16685f8e2d8830850.exe 28 PID 2268 wrote to memory of 2948 2268 4d23b60ec48e9f6fac3efacc25f5978f0d4ec2fbdd4410f16685f8e2d8830850.exe 28 PID 2268 wrote to memory of 2948 2268 4d23b60ec48e9f6fac3efacc25f5978f0d4ec2fbdd4410f16685f8e2d8830850.exe 28 PID 2268 wrote to memory of 2912 2268 4d23b60ec48e9f6fac3efacc25f5978f0d4ec2fbdd4410f16685f8e2d8830850.exe 29 PID 2268 wrote to memory of 2912 2268 4d23b60ec48e9f6fac3efacc25f5978f0d4ec2fbdd4410f16685f8e2d8830850.exe 29 PID 2268 wrote to memory of 2912 2268 4d23b60ec48e9f6fac3efacc25f5978f0d4ec2fbdd4410f16685f8e2d8830850.exe 29 PID 2268 wrote to memory of 2912 2268 4d23b60ec48e9f6fac3efacc25f5978f0d4ec2fbdd4410f16685f8e2d8830850.exe 29 PID 2268 wrote to memory of 2520 2268 4d23b60ec48e9f6fac3efacc25f5978f0d4ec2fbdd4410f16685f8e2d8830850.exe 32 PID 2268 wrote to memory of 2520 2268 4d23b60ec48e9f6fac3efacc25f5978f0d4ec2fbdd4410f16685f8e2d8830850.exe 32 PID 2268 wrote to memory of 2520 2268 4d23b60ec48e9f6fac3efacc25f5978f0d4ec2fbdd4410f16685f8e2d8830850.exe 32 PID 2268 wrote to memory of 2520 2268 4d23b60ec48e9f6fac3efacc25f5978f0d4ec2fbdd4410f16685f8e2d8830850.exe 32 PID 2268 wrote to memory of 2608 2268 4d23b60ec48e9f6fac3efacc25f5978f0d4ec2fbdd4410f16685f8e2d8830850.exe 34 PID 2268 wrote to memory of 2608 2268 4d23b60ec48e9f6fac3efacc25f5978f0d4ec2fbdd4410f16685f8e2d8830850.exe 34 PID 2268 wrote to memory of 2608 2268 4d23b60ec48e9f6fac3efacc25f5978f0d4ec2fbdd4410f16685f8e2d8830850.exe 34 PID 2268 wrote to memory of 2608 2268 4d23b60ec48e9f6fac3efacc25f5978f0d4ec2fbdd4410f16685f8e2d8830850.exe 34 PID 2948 wrote to memory of 2532 2948 cmd.exe 35 PID 2948 wrote to memory of 2532 2948 cmd.exe 35 PID 2948 wrote to memory of 2532 2948 cmd.exe 35 PID 2948 wrote to memory of 2532 2948 cmd.exe 35 PID 2912 wrote to memory of 2552 2912 cmd.exe 36 PID 2912 wrote to memory of 2552 2912 cmd.exe 36 PID 2912 wrote to memory of 2552 2912 cmd.exe 36 PID 2912 wrote to memory of 2552 2912 cmd.exe 36 PID 2608 wrote to memory of 2528 2608 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 37 PID 2608 wrote to memory of 2528 2608 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 37 PID 2608 wrote to memory of 2528 2608 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 37 PID 2608 wrote to memory of 2528 2608 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 37 PID 2608 wrote to memory of 2672 2608 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 38 PID 2608 wrote to memory of 2672 2608 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 38 PID 2608 wrote to memory of 2672 2608 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 38 PID 2608 wrote to memory of 2672 2608 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 38 PID 2520 wrote to memory of 2412 2520 cmd.exe 39 PID 2520 wrote to memory of 2412 2520 cmd.exe 39 PID 2520 wrote to memory of 2412 2520 cmd.exe 39 PID 2520 wrote to memory of 2412 2520 cmd.exe 39 PID 2608 wrote to memory of 2428 2608 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 41 PID 2608 wrote to memory of 2428 2608 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 41 PID 2608 wrote to memory of 2428 2608 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 41 PID 2608 wrote to memory of 2428 2608 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 41 PID 2608 wrote to memory of 2632 2608 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 42 PID 2608 wrote to memory of 2632 2608 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 42 PID 2608 wrote to memory of 2632 2608 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 42 PID 2608 wrote to memory of 2632 2608 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 42 PID 2608 wrote to memory of 2632 2608 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 42 PID 2608 wrote to memory of 2632 2608 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 42 PID 2608 wrote to memory of 2632 2608 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 42 PID 2608 wrote to memory of 2632 2608 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 42 PID 2608 wrote to memory of 2632 2608 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 42 PID 2608 wrote to memory of 2632 2608 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 42 PID 2608 wrote to memory of 2632 2608 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 42 PID 2608 wrote to memory of 2632 2608 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 42 PID 2608 wrote to memory of 2632 2608 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 42 PID 2608 wrote to memory of 2632 2608 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 42 PID 2608 wrote to memory of 2632 2608 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 42 PID 2608 wrote to memory of 2632 2608 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 42 PID 2608 wrote to memory of 2632 2608 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 42 PID 2608 wrote to memory of 2632 2608 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 42 PID 2608 wrote to memory of 2632 2608 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 42 PID 2608 wrote to memory of 2632 2608 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 42 PID 2608 wrote to memory of 2632 2608 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 42 PID 2608 wrote to memory of 2632 2608 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 42 PID 2608 wrote to memory of 2632 2608 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 42 PID 2608 wrote to memory of 2632 2608 4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe 42 -
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⤵
- Loads dropped DLL
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2268 -
C:\Windows\SysWOW64\cmd.exe/c sc stop WinDefend2⤵
- Suspicious use of WriteProcessMemory
PID:2948 -
C:\Windows\SysWOW64\sc.exesc stop WinDefend3⤵
- Launches sc.exe
PID:2532
-
-
-
C:\Windows\SysWOW64\cmd.exe/c sc delete WinDefend2⤵
- Suspicious use of WriteProcessMemory
PID:2912 -
C:\Windows\SysWOW64\sc.exesc delete WinDefend3⤵
- Launches sc.exe
PID:2552
-
-
-
C:\Windows\SysWOW64\cmd.exe/c powershell Set-MpPreference -DisableRealtimeMonitoring $true2⤵
- Suspicious use of WriteProcessMemory
PID:2520 -
C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exepowershell Set-MpPreference -DisableRealtimeMonitoring $true3⤵
- Drops file in System32 directory
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of AdjustPrivilegeToken
PID:2412
-
-
-
C:\Users\Admin\AppData\Roaming\WinSocket\4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exeC:\Users\Admin\AppData\Roaming\WinSocket\4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe2⤵
- Executes dropped EXE
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2608 -
C:\Windows\SysWOW64\cmd.exe/c sc stop WinDefend3⤵PID:2528
-
C:\Windows\SysWOW64\sc.exesc stop WinDefend4⤵
- Launches sc.exe
PID:2320
-
-
-
C:\Windows\SysWOW64\cmd.exe/c sc delete WinDefend3⤵PID:2672
-
C:\Windows\SysWOW64\sc.exesc delete WinDefend4⤵
- Launches sc.exe
PID:2016
-
-
-
C:\Windows\SysWOW64\cmd.exe/c powershell Set-MpPreference -DisableRealtimeMonitoring $true3⤵PID:2428
-
C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exepowershell Set-MpPreference -DisableRealtimeMonitoring $true4⤵
- Drops file in System32 directory
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of AdjustPrivilegeToken
PID:2280
-
-
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:2632
-
-
-
C:\Windows\system32\taskeng.exetaskeng.exe {128616E7-A32D-414C-97E0-9F85BDDA1F61} S-1-5-18:NT AUTHORITY\System:Service:1⤵PID:2748
-
C:\Users\Admin\AppData\Roaming\WinSocket\4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exeC:\Users\Admin\AppData\Roaming\WinSocket\4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe2⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
PID:384 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:2592
-
-
-
C:\Users\Admin\AppData\Roaming\WinSocket\4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exeC:\Users\Admin\AppData\Roaming\WinSocket\4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe2⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
PID:1036 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:992
-
-
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
-
C:\Users\Admin\AppData\Roaming\Microsoft\Windows\Recent\CustomDestinations\d93f411851d7c929.customDestinations-ms
Filesize7KB
MD5901b261085ca35e66a3c2a7f0fa0cead
SHA1fbf365de49f4476cffdafbe763c3a9c9cfcd62eb
SHA25628a2a974410db762faf53b9a0c88a6d86ff956ecbbf137836b01d2dd7f94428b
SHA512672174f2bbe5a61cdfa57f5c90f7c03aba20ab3e5c3c203696522e815a1ef86ab87f58324c038b55a102404c167c9aac75ec0512652a0da5910db5c26eb56994
-
\Users\Admin\AppData\Roaming\WinSocket\4d23b70ec49e9f7fac3efacc26f6989f0d4ec2fbdd4410f17796f9e2d9930960.exe
Filesize1.5MB
MD534fc400c62b2218cc536b3e2104d3085
SHA102cf6b268ad52001119b41f4a4bfb867c67238a4
SHA2564d23b60ec48e9f6fac3efacc25f5978f0d4ec2fbdd4410f16685f8e2d8830850
SHA512f6d4d280fd7eac9789afc4743241272db745fdd5d61d4d4c8bf2778b2accd9b1814dcd6efb1ed6caf977ffe8969f97fc4b301d89a50b843941e051978d898c4d