Analysis
-
max time kernel
135s -
max time network
121s -
platform
windows7_x64 -
resource
win7-20240221-en -
resource tags
arch:x64arch:x86image:win7-20240221-enlocale:en-usos:windows7-x64system -
submitted
07-05-2024 18:50
Behavioral task
behavioral1
Sample
121f01636a3ea9d02d42f317f417af9d1ec553805f88d788b9ade83586d694ba.exe
Resource
win7-20240221-en
General
-
Target
121f01636a3ea9d02d42f317f417af9d1ec553805f88d788b9ade83586d694ba.exe
-
Size
1.3MB
-
MD5
fb79f9fb02992d0e53b0aeb701e0d439
-
SHA1
d89df905142cd634123d55d6e7537cfc36e49981
-
SHA256
121f01636a3ea9d02d42f317f417af9d1ec553805f88d788b9ade83586d694ba
-
SHA512
819032457fc18a892c45ca524c3ba7f43ef48915b8afdd758614009f289fb525d7b86d0336cf8136e2fa4410d142110cfaa77f7f6552689ac79c3f0c581df32d
-
SSDEEP
24576:zQ5aILMCfmAUjzX6gfU1pjwjbsXhmvZssrD+nRgnf4NvlOSw:E5aIwC+Agr6g81p1vsrNiw
Malware Config
Signatures
-
KPOT Core Executable 1 IoCs
Processes:
resource yara_rule \Users\Admin\AppData\Roaming\WinSocket\121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe family_kpot -
Trickbot x86 loader 1 IoCs
Detected Trickbot's x86 loader that unpacks the x86 payload.
Processes:
resource yara_rule behavioral1/memory/2696-15-0x00000000003A0000-0x00000000003C9000-memory.dmp trickbot_loader32 -
Executes dropped EXE 3 IoCs
Processes:
121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exepid process 1124 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe 884 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe 624 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe -
Loads dropped DLL 2 IoCs
Processes:
121f01636a3ea9d02d42f317f417af9d1ec553805f88d788b9ade83586d694ba.exepid process 2696 121f01636a3ea9d02d42f317f417af9d1ec553805f88d788b9ade83586d694ba.exe 2696 121f01636a3ea9d02d42f317f417af9d1ec553805f88d788b9ade83586d694ba.exe -
Drops file in System32 directory 2 IoCs
Processes:
powershell.exepowershell.exedescription 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.
Processes:
sc.exesc.exesc.exesc.exepid process 2436 sc.exe 2652 sc.exe 2724 sc.exe 2728 sc.exe -
Suspicious behavior: EnumeratesProcesses 8 IoCs
Processes:
121f01636a3ea9d02d42f317f417af9d1ec553805f88d788b9ade83586d694ba.exe121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exepowershell.exepowershell.exepid process 2696 121f01636a3ea9d02d42f317f417af9d1ec553805f88d788b9ade83586d694ba.exe 2696 121f01636a3ea9d02d42f317f417af9d1ec553805f88d788b9ade83586d694ba.exe 2696 121f01636a3ea9d02d42f317f417af9d1ec553805f88d788b9ade83586d694ba.exe 1124 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe 1124 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe 1124 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe 2756 powershell.exe 2552 powershell.exe -
Suspicious use of AdjustPrivilegeToken 4 IoCs
Processes:
powershell.exepowershell.exe121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exedescription pid process Token: SeDebugPrivilege 2756 powershell.exe Token: SeDebugPrivilege 2552 powershell.exe Token: SeTcbPrivilege 884 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe Token: SeTcbPrivilege 624 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe -
Suspicious use of SetWindowsHookEx 4 IoCs
Processes:
121f01636a3ea9d02d42f317f417af9d1ec553805f88d788b9ade83586d694ba.exe121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exepid process 2696 121f01636a3ea9d02d42f317f417af9d1ec553805f88d788b9ade83586d694ba.exe 1124 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe 884 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe 624 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe -
Suspicious use of WriteProcessMemory 64 IoCs
Processes:
121f01636a3ea9d02d42f317f417af9d1ec553805f88d788b9ade83586d694ba.execmd.execmd.execmd.exe121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exedescription pid process target process PID 2696 wrote to memory of 2668 2696 121f01636a3ea9d02d42f317f417af9d1ec553805f88d788b9ade83586d694ba.exe cmd.exe PID 2696 wrote to memory of 2668 2696 121f01636a3ea9d02d42f317f417af9d1ec553805f88d788b9ade83586d694ba.exe cmd.exe PID 2696 wrote to memory of 2668 2696 121f01636a3ea9d02d42f317f417af9d1ec553805f88d788b9ade83586d694ba.exe cmd.exe PID 2696 wrote to memory of 2668 2696 121f01636a3ea9d02d42f317f417af9d1ec553805f88d788b9ade83586d694ba.exe cmd.exe PID 2696 wrote to memory of 2644 2696 121f01636a3ea9d02d42f317f417af9d1ec553805f88d788b9ade83586d694ba.exe cmd.exe PID 2696 wrote to memory of 2644 2696 121f01636a3ea9d02d42f317f417af9d1ec553805f88d788b9ade83586d694ba.exe cmd.exe PID 2696 wrote to memory of 2644 2696 121f01636a3ea9d02d42f317f417af9d1ec553805f88d788b9ade83586d694ba.exe cmd.exe PID 2696 wrote to memory of 2644 2696 121f01636a3ea9d02d42f317f417af9d1ec553805f88d788b9ade83586d694ba.exe cmd.exe PID 2696 wrote to memory of 2564 2696 121f01636a3ea9d02d42f317f417af9d1ec553805f88d788b9ade83586d694ba.exe cmd.exe PID 2696 wrote to memory of 2564 2696 121f01636a3ea9d02d42f317f417af9d1ec553805f88d788b9ade83586d694ba.exe cmd.exe PID 2696 wrote to memory of 2564 2696 121f01636a3ea9d02d42f317f417af9d1ec553805f88d788b9ade83586d694ba.exe cmd.exe PID 2696 wrote to memory of 2564 2696 121f01636a3ea9d02d42f317f417af9d1ec553805f88d788b9ade83586d694ba.exe cmd.exe PID 2696 wrote to memory of 1124 2696 121f01636a3ea9d02d42f317f417af9d1ec553805f88d788b9ade83586d694ba.exe 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe PID 2696 wrote to memory of 1124 2696 121f01636a3ea9d02d42f317f417af9d1ec553805f88d788b9ade83586d694ba.exe 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe PID 2696 wrote to memory of 1124 2696 121f01636a3ea9d02d42f317f417af9d1ec553805f88d788b9ade83586d694ba.exe 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe PID 2696 wrote to memory of 1124 2696 121f01636a3ea9d02d42f317f417af9d1ec553805f88d788b9ade83586d694ba.exe 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe PID 2668 wrote to memory of 2436 2668 cmd.exe sc.exe PID 2668 wrote to memory of 2436 2668 cmd.exe sc.exe PID 2668 wrote to memory of 2436 2668 cmd.exe sc.exe PID 2668 wrote to memory of 2436 2668 cmd.exe sc.exe PID 2644 wrote to memory of 2652 2644 cmd.exe sc.exe PID 2644 wrote to memory of 2652 2644 cmd.exe sc.exe PID 2644 wrote to memory of 2652 2644 cmd.exe sc.exe PID 2644 wrote to memory of 2652 2644 cmd.exe sc.exe PID 2564 wrote to memory of 2552 2564 cmd.exe powershell.exe PID 2564 wrote to memory of 2552 2564 cmd.exe powershell.exe PID 2564 wrote to memory of 2552 2564 cmd.exe powershell.exe PID 2564 wrote to memory of 2552 2564 cmd.exe powershell.exe PID 1124 wrote to memory of 2536 1124 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe cmd.exe PID 1124 wrote to memory of 2536 1124 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe cmd.exe PID 1124 wrote to memory of 2536 1124 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe cmd.exe PID 1124 wrote to memory of 2536 1124 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe cmd.exe PID 1124 wrote to memory of 2332 1124 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe cmd.exe PID 1124 wrote to memory of 2332 1124 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe cmd.exe PID 1124 wrote to memory of 2332 1124 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe cmd.exe PID 1124 wrote to memory of 2332 1124 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe cmd.exe PID 1124 wrote to memory of 2892 1124 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe cmd.exe PID 1124 wrote to memory of 2892 1124 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe cmd.exe PID 1124 wrote to memory of 2892 1124 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe cmd.exe PID 1124 wrote to memory of 2892 1124 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe cmd.exe PID 1124 wrote to memory of 2324 1124 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe svchost.exe PID 1124 wrote to memory of 2324 1124 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe svchost.exe PID 1124 wrote to memory of 2324 1124 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe svchost.exe PID 1124 wrote to memory of 2324 1124 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe svchost.exe PID 1124 wrote to memory of 2324 1124 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe svchost.exe PID 1124 wrote to memory of 2324 1124 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe svchost.exe PID 1124 wrote to memory of 2324 1124 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe svchost.exe PID 1124 wrote to memory of 2324 1124 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe svchost.exe PID 1124 wrote to memory of 2324 1124 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe svchost.exe PID 1124 wrote to memory of 2324 1124 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe svchost.exe PID 1124 wrote to memory of 2324 1124 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe svchost.exe PID 1124 wrote to memory of 2324 1124 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe svchost.exe PID 1124 wrote to memory of 2324 1124 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe svchost.exe PID 1124 wrote to memory of 2324 1124 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe svchost.exe PID 1124 wrote to memory of 2324 1124 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe svchost.exe PID 1124 wrote to memory of 2324 1124 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe svchost.exe PID 1124 wrote to memory of 2324 1124 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe svchost.exe PID 1124 wrote to memory of 2324 1124 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe svchost.exe PID 1124 wrote to memory of 2324 1124 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe svchost.exe PID 1124 wrote to memory of 2324 1124 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe svchost.exe PID 1124 wrote to memory of 2324 1124 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe svchost.exe PID 1124 wrote to memory of 2324 1124 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe svchost.exe PID 1124 wrote to memory of 2324 1124 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe svchost.exe PID 1124 wrote to memory of 2324 1124 121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe svchost.exe -
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\121f01636a3ea9d02d42f317f417af9d1ec553805f88d788b9ade83586d694ba.exe"C:\Users\Admin\AppData\Local\Temp\121f01636a3ea9d02d42f317f417af9d1ec553805f88d788b9ade83586d694ba.exe"1⤵
- Loads dropped DLL
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2696 -
C:\Windows\SysWOW64\cmd.exe/c sc stop WinDefend2⤵
- Suspicious use of WriteProcessMemory
PID:2668 -
C:\Windows\SysWOW64\sc.exesc stop WinDefend3⤵
- Launches sc.exe
PID:2436 -
C:\Windows\SysWOW64\cmd.exe/c sc delete WinDefend2⤵
- Suspicious use of WriteProcessMemory
PID:2644 -
C:\Windows\SysWOW64\sc.exesc delete WinDefend3⤵
- Launches sc.exe
PID:2652 -
C:\Windows\SysWOW64\cmd.exe/c powershell Set-MpPreference -DisableRealtimeMonitoring $true2⤵
- Suspicious use of WriteProcessMemory
PID:2564 -
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:2552 -
C:\Users\Admin\AppData\Roaming\WinSocket\121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exeC:\Users\Admin\AppData\Roaming\WinSocket\121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe2⤵
- Executes dropped EXE
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:1124 -
C:\Windows\SysWOW64\cmd.exe/c sc stop WinDefend3⤵PID:2536
-
C:\Windows\SysWOW64\sc.exesc stop WinDefend4⤵
- Launches sc.exe
PID:2724 -
C:\Windows\SysWOW64\cmd.exe/c sc delete WinDefend3⤵PID:2332
-
C:\Windows\SysWOW64\sc.exesc delete WinDefend4⤵
- Launches sc.exe
PID:2728 -
C:\Windows\SysWOW64\cmd.exe/c powershell Set-MpPreference -DisableRealtimeMonitoring $true3⤵PID:2892
-
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:2756 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:2324
-
C:\Windows\system32\taskeng.exetaskeng.exe {D2404C0E-5496-44E2-A9E2-D036361D31FE} S-1-5-18:NT AUTHORITY\System:Service:1⤵PID:604
-
C:\Users\Admin\AppData\Roaming\WinSocket\121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exeC:\Users\Admin\AppData\Roaming\WinSocket\121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe2⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
PID:884 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:1716
-
C:\Users\Admin\AppData\Roaming\WinSocket\121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exeC:\Users\Admin\AppData\Roaming\WinSocket\121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe2⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
PID:624 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:2212
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
MD5b2a6e163b8200907b68db14e1ffcf62f
SHA109d545b2bec824055f85ec0ab4f694edb99c17b4
SHA256c16c4bf9762f76268c7894e489575c7c6b84efaac588faabffb097e64bf6367f
SHA512cba92e1f0c61953feeead5a3c9fbee2b5e3a7e11cf2029e18892448f1d48c972b508dd3498a7c5d2d313eb69e803bb8e2de1f3ef25648f5ead2d5c50d38c103b
-
\Users\Admin\AppData\Roaming\WinSocket\121f01737a3ea9d02d42f318f418af9d1ec663906f99d899b9ade93697d794ba.exe
Filesize1.3MB
MD5fb79f9fb02992d0e53b0aeb701e0d439
SHA1d89df905142cd634123d55d6e7537cfc36e49981
SHA256121f01636a3ea9d02d42f317f417af9d1ec553805f88d788b9ade83586d694ba
SHA512819032457fc18a892c45ca524c3ba7f43ef48915b8afdd758614009f289fb525d7b86d0336cf8136e2fa4410d142110cfaa77f7f6552689ac79c3f0c581df32d