Analysis
-
max time kernel
135s -
max time network
118s -
platform
windows7_x64 -
resource
win7-20240419-en -
resource tags
arch:x64arch:x86image:win7-20240419-enlocale:en-usos:windows7-x64system -
submitted
11-05-2024 22:04
Behavioral task
behavioral1
Sample
591a8e23e0da8fbd771c930d921410196091ba72ff821e18ab4315d105c35174.exe
Resource
win7-20240419-en
General
-
Target
591a8e23e0da8fbd771c930d921410196091ba72ff821e18ab4315d105c35174.exe
-
Size
915KB
-
MD5
9cbc7cb10150e6522acf2efbbcdb04c9
-
SHA1
c0cc51589fee47ca0d7368f54a4333b6958cf03d
-
SHA256
591a8e23e0da8fbd771c930d921410196091ba72ff821e18ab4315d105c35174
-
SHA512
67470b5ba7f6397284c68de14e473be97051a14ea5259148501a91feb1954fe21d93232b6d06fb33aedaef60aa2745929a0f39554cdeeece0ad2fd8c6be7ea41
-
SSDEEP
12288:zJB0lh5aILwtFPCfmAUtFC6NXbv+GEBQqtGSsGa60C+4PMAQNhW4LbjujY1:zQ5aILMCfmAUjzX6xQtjmsNLXIE
Malware Config
Signatures
-
KPOT Core Executable 1 IoCs
resource yara_rule behavioral1/files/0x0008000000014254-19.dat family_kpot -
Trickbot x86 loader 1 IoCs
Detected Trickbot's x86 loader that unpacks the x86 payload.
resource yara_rule behavioral1/memory/2460-15-0x00000000002A0000-0x00000000002C9000-memory.dmp trickbot_loader32 -
Executes dropped EXE 3 IoCs
pid Process 2960 691a9e23e0da9fbd881c930d921410197091ba82ff921e19ab4316d106c36184.exe 1304 691a9e23e0da9fbd881c930d921410197091ba82ff921e19ab4316d106c36184.exe 856 691a9e23e0da9fbd881c930d921410197091ba82ff921e19ab4316d106c36184.exe -
Loads dropped DLL 2 IoCs
pid Process 2460 591a8e23e0da8fbd771c930d921410196091ba72ff821e18ab4315d105c35174.exe 2460 591a8e23e0da8fbd771c930d921410196091ba72ff821e18ab4315d105c35174.exe -
Drops file in System32 directory 1 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 -
Launches sc.exe 2 IoCs
Sc.exe is a Windows utlilty to control services on the system.
pid Process 1984 sc.exe 2944 sc.exe -
Suspicious behavior: EnumeratesProcesses 4 IoCs
pid Process 2460 591a8e23e0da8fbd771c930d921410196091ba72ff821e18ab4315d105c35174.exe 2460 591a8e23e0da8fbd771c930d921410196091ba72ff821e18ab4315d105c35174.exe 2460 591a8e23e0da8fbd771c930d921410196091ba72ff821e18ab4315d105c35174.exe 2828 powershell.exe -
Suspicious use of AdjustPrivilegeToken 3 IoCs
description pid Process Token: SeDebugPrivilege 2828 powershell.exe Token: SeTcbPrivilege 1304 691a9e23e0da9fbd881c930d921410197091ba82ff921e19ab4316d106c36184.exe Token: SeTcbPrivilege 856 691a9e23e0da9fbd881c930d921410197091ba82ff921e19ab4316d106c36184.exe -
Suspicious use of SetWindowsHookEx 4 IoCs
pid Process 2460 591a8e23e0da8fbd771c930d921410196091ba72ff821e18ab4315d105c35174.exe 2960 691a9e23e0da9fbd881c930d921410197091ba82ff921e19ab4316d106c36184.exe 1304 691a9e23e0da9fbd881c930d921410197091ba82ff921e19ab4316d106c36184.exe 856 691a9e23e0da9fbd881c930d921410197091ba82ff921e19ab4316d106c36184.exe -
Suspicious use of WriteProcessMemory 64 IoCs
description pid Process procid_target PID 2460 wrote to memory of 2108 2460 591a8e23e0da8fbd771c930d921410196091ba72ff821e18ab4315d105c35174.exe 28 PID 2460 wrote to memory of 2108 2460 591a8e23e0da8fbd771c930d921410196091ba72ff821e18ab4315d105c35174.exe 28 PID 2460 wrote to memory of 2108 2460 591a8e23e0da8fbd771c930d921410196091ba72ff821e18ab4315d105c35174.exe 28 PID 2460 wrote to memory of 2108 2460 591a8e23e0da8fbd771c930d921410196091ba72ff821e18ab4315d105c35174.exe 28 PID 2460 wrote to memory of 2348 2460 591a8e23e0da8fbd771c930d921410196091ba72ff821e18ab4315d105c35174.exe 29 PID 2460 wrote to memory of 2348 2460 591a8e23e0da8fbd771c930d921410196091ba72ff821e18ab4315d105c35174.exe 29 PID 2460 wrote to memory of 2348 2460 591a8e23e0da8fbd771c930d921410196091ba72ff821e18ab4315d105c35174.exe 29 PID 2460 wrote to memory of 2348 2460 591a8e23e0da8fbd771c930d921410196091ba72ff821e18ab4315d105c35174.exe 29 PID 2460 wrote to memory of 2680 2460 591a8e23e0da8fbd771c930d921410196091ba72ff821e18ab4315d105c35174.exe 31 PID 2460 wrote to memory of 2680 2460 591a8e23e0da8fbd771c930d921410196091ba72ff821e18ab4315d105c35174.exe 31 PID 2460 wrote to memory of 2680 2460 591a8e23e0da8fbd771c930d921410196091ba72ff821e18ab4315d105c35174.exe 31 PID 2460 wrote to memory of 2680 2460 591a8e23e0da8fbd771c930d921410196091ba72ff821e18ab4315d105c35174.exe 31 PID 2460 wrote to memory of 2960 2460 591a8e23e0da8fbd771c930d921410196091ba72ff821e18ab4315d105c35174.exe 34 PID 2460 wrote to memory of 2960 2460 591a8e23e0da8fbd771c930d921410196091ba72ff821e18ab4315d105c35174.exe 34 PID 2460 wrote to memory of 2960 2460 591a8e23e0da8fbd771c930d921410196091ba72ff821e18ab4315d105c35174.exe 34 PID 2460 wrote to memory of 2960 2460 591a8e23e0da8fbd771c930d921410196091ba72ff821e18ab4315d105c35174.exe 34 PID 2108 wrote to memory of 1984 2108 cmd.exe 35 PID 2108 wrote to memory of 1984 2108 cmd.exe 35 PID 2108 wrote to memory of 1984 2108 cmd.exe 35 PID 2108 wrote to memory of 1984 2108 cmd.exe 35 PID 2348 wrote to memory of 2944 2348 cmd.exe 36 PID 2348 wrote to memory of 2944 2348 cmd.exe 36 PID 2348 wrote to memory of 2944 2348 cmd.exe 36 PID 2348 wrote to memory of 2944 2348 cmd.exe 36 PID 2680 wrote to memory of 2828 2680 cmd.exe 37 PID 2680 wrote to memory of 2828 2680 cmd.exe 37 PID 2680 wrote to memory of 2828 2680 cmd.exe 37 PID 2680 wrote to memory of 2828 2680 cmd.exe 37 PID 2960 wrote to memory of 2544 2960 691a9e23e0da9fbd881c930d921410197091ba82ff921e19ab4316d106c36184.exe 38 PID 2960 wrote to memory of 2544 2960 691a9e23e0da9fbd881c930d921410197091ba82ff921e19ab4316d106c36184.exe 38 PID 2960 wrote to memory of 2544 2960 691a9e23e0da9fbd881c930d921410197091ba82ff921e19ab4316d106c36184.exe 38 PID 2960 wrote to memory of 2544 2960 691a9e23e0da9fbd881c930d921410197091ba82ff921e19ab4316d106c36184.exe 38 PID 2960 wrote to memory of 2544 2960 691a9e23e0da9fbd881c930d921410197091ba82ff921e19ab4316d106c36184.exe 38 PID 2960 wrote to memory of 2544 2960 691a9e23e0da9fbd881c930d921410197091ba82ff921e19ab4316d106c36184.exe 38 PID 2960 wrote to memory of 2544 2960 691a9e23e0da9fbd881c930d921410197091ba82ff921e19ab4316d106c36184.exe 38 PID 2960 wrote to memory of 2544 2960 691a9e23e0da9fbd881c930d921410197091ba82ff921e19ab4316d106c36184.exe 38 PID 2960 wrote to memory of 2544 2960 691a9e23e0da9fbd881c930d921410197091ba82ff921e19ab4316d106c36184.exe 38 PID 2960 wrote to memory of 2544 2960 691a9e23e0da9fbd881c930d921410197091ba82ff921e19ab4316d106c36184.exe 38 PID 2960 wrote to memory of 2544 2960 691a9e23e0da9fbd881c930d921410197091ba82ff921e19ab4316d106c36184.exe 38 PID 2960 wrote to memory of 2544 2960 691a9e23e0da9fbd881c930d921410197091ba82ff921e19ab4316d106c36184.exe 38 PID 2960 wrote to memory of 2544 2960 691a9e23e0da9fbd881c930d921410197091ba82ff921e19ab4316d106c36184.exe 38 PID 2960 wrote to memory of 2544 2960 691a9e23e0da9fbd881c930d921410197091ba82ff921e19ab4316d106c36184.exe 38 PID 2960 wrote to memory of 2544 2960 691a9e23e0da9fbd881c930d921410197091ba82ff921e19ab4316d106c36184.exe 38 PID 2960 wrote to memory of 2544 2960 691a9e23e0da9fbd881c930d921410197091ba82ff921e19ab4316d106c36184.exe 38 PID 2960 wrote to memory of 2544 2960 691a9e23e0da9fbd881c930d921410197091ba82ff921e19ab4316d106c36184.exe 38 PID 2960 wrote to memory of 2544 2960 691a9e23e0da9fbd881c930d921410197091ba82ff921e19ab4316d106c36184.exe 38 PID 2960 wrote to memory of 2544 2960 691a9e23e0da9fbd881c930d921410197091ba82ff921e19ab4316d106c36184.exe 38 PID 2960 wrote to memory of 2544 2960 691a9e23e0da9fbd881c930d921410197091ba82ff921e19ab4316d106c36184.exe 38 PID 2960 wrote to memory of 2544 2960 691a9e23e0da9fbd881c930d921410197091ba82ff921e19ab4316d106c36184.exe 38 PID 2960 wrote to memory of 2544 2960 691a9e23e0da9fbd881c930d921410197091ba82ff921e19ab4316d106c36184.exe 38 PID 2960 wrote to memory of 2544 2960 691a9e23e0da9fbd881c930d921410197091ba82ff921e19ab4316d106c36184.exe 38 PID 2960 wrote to memory of 2544 2960 691a9e23e0da9fbd881c930d921410197091ba82ff921e19ab4316d106c36184.exe 38 PID 2960 wrote to memory of 2544 2960 691a9e23e0da9fbd881c930d921410197091ba82ff921e19ab4316d106c36184.exe 38 PID 2960 wrote to memory of 2544 2960 691a9e23e0da9fbd881c930d921410197091ba82ff921e19ab4316d106c36184.exe 38 PID 2960 wrote to memory of 2544 2960 691a9e23e0da9fbd881c930d921410197091ba82ff921e19ab4316d106c36184.exe 38 PID 2960 wrote to memory of 2544 2960 691a9e23e0da9fbd881c930d921410197091ba82ff921e19ab4316d106c36184.exe 38 PID 844 wrote to memory of 1304 844 taskeng.exe 42 PID 844 wrote to memory of 1304 844 taskeng.exe 42 PID 844 wrote to memory of 1304 844 taskeng.exe 42 PID 844 wrote to memory of 1304 844 taskeng.exe 42 PID 1304 wrote to memory of 2512 1304 691a9e23e0da9fbd881c930d921410197091ba82ff921e19ab4316d106c36184.exe 43 PID 1304 wrote to memory of 2512 1304 691a9e23e0da9fbd881c930d921410197091ba82ff921e19ab4316d106c36184.exe 43 PID 1304 wrote to memory of 2512 1304 691a9e23e0da9fbd881c930d921410197091ba82ff921e19ab4316d106c36184.exe 43 PID 1304 wrote to memory of 2512 1304 691a9e23e0da9fbd881c930d921410197091ba82ff921e19ab4316d106c36184.exe 43 -
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\591a8e23e0da8fbd771c930d921410196091ba72ff821e18ab4315d105c35174.exe"C:\Users\Admin\AppData\Local\Temp\591a8e23e0da8fbd771c930d921410196091ba72ff821e18ab4315d105c35174.exe"1⤵
- Loads dropped DLL
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2460 -
C:\Windows\SysWOW64\cmd.exe/c sc stop WinDefend2⤵
- Suspicious use of WriteProcessMemory
PID:2108 -
C:\Windows\SysWOW64\sc.exesc stop WinDefend3⤵
- Launches sc.exe
PID:1984
-
-
-
C:\Windows\SysWOW64\cmd.exe/c sc delete WinDefend2⤵
- Suspicious use of WriteProcessMemory
PID:2348 -
C:\Windows\SysWOW64\sc.exesc delete WinDefend3⤵
- Launches sc.exe
PID:2944
-
-
-
C:\Windows\SysWOW64\cmd.exe/c powershell Set-MpPreference -DisableRealtimeMonitoring $true2⤵
- Suspicious use of WriteProcessMemory
PID:2680 -
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:2828
-
-
-
C:\Users\Admin\AppData\Roaming\WinSocket\691a9e23e0da9fbd881c930d921410197091ba82ff921e19ab4316d106c36184.exeC:\Users\Admin\AppData\Roaming\WinSocket\691a9e23e0da9fbd881c930d921410197091ba82ff921e19ab4316d106c36184.exe2⤵
- Executes dropped EXE
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2960 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:2544
-
-
-
C:\Windows\system32\taskeng.exetaskeng.exe {5FEBF2AE-84C9-4BFC-898F-24504AF52EA3} S-1-5-18:NT AUTHORITY\System:Service:1⤵
- Suspicious use of WriteProcessMemory
PID:844 -
C:\Users\Admin\AppData\Roaming\WinSocket\691a9e23e0da9fbd881c930d921410197091ba82ff921e19ab4316d106c36184.exeC:\Users\Admin\AppData\Roaming\WinSocket\691a9e23e0da9fbd881c930d921410197091ba82ff921e19ab4316d106c36184.exe2⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:1304 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:2512
-
-
-
C:\Users\Admin\AppData\Roaming\WinSocket\691a9e23e0da9fbd881c930d921410197091ba82ff921e19ab4316d106c36184.exeC:\Users\Admin\AppData\Roaming\WinSocket\691a9e23e0da9fbd881c930d921410197091ba82ff921e19ab4316d106c36184.exe2⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
PID:856 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:956
-
-
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
-
\Users\Admin\AppData\Roaming\WinSocket\691a9e23e0da9fbd881c930d921410197091ba82ff921e19ab4316d106c36184.exe
Filesize915KB
MD59cbc7cb10150e6522acf2efbbcdb04c9
SHA1c0cc51589fee47ca0d7368f54a4333b6958cf03d
SHA256591a8e23e0da8fbd771c930d921410196091ba72ff821e18ab4315d105c35174
SHA51267470b5ba7f6397284c68de14e473be97051a14ea5259148501a91feb1954fe21d93232b6d06fb33aedaef60aa2745929a0f39554cdeeece0ad2fd8c6be7ea41