Analysis
-
max time kernel
135s -
max time network
123s -
platform
windows7_x64 -
resource
win7-20240419-en -
resource tags
arch:x64arch:x86image:win7-20240419-enlocale:en-usos:windows7-x64system -
submitted
11-06-2024 05:11
Behavioral task
behavioral1
Sample
f6764d8c3bdf43e73d258cb1e2853719a0f4d3c2ca1917f8b2538574a79b6599.exe
Resource
win7-20240419-en
General
-
Target
f6764d8c3bdf43e73d258cb1e2853719a0f4d3c2ca1917f8b2538574a79b6599.exe
-
Size
1.1MB
-
MD5
e2033482b1fe8d03a3fb8a16a7c99134
-
SHA1
be42717d3bf76893aad0ffd3ecce1c534ff4ef83
-
SHA256
f6764d8c3bdf43e73d258cb1e2853719a0f4d3c2ca1917f8b2538574a79b6599
-
SHA512
f89f9e42703ae7a3034b4a0f87ce8b505b1751295a631c626462ba7323189d0bc6fa0a80c203a8201de82c58507722f11712ac9b647460bb2c265a694766aaf5
-
SSDEEP
12288:zJB0lh5aILwtFPCfmAUtFC6NXbv+GEBQqtGSsGa60C+4PMAQBnm46MoCBuu0JphT:zQ5aILMCfmAUjzX6xQtjmssdqex/n
Malware Config
Signatures
-
KPOT Core Executable 1 IoCs
resource yara_rule behavioral1/files/0x00080000000146a7-20.dat family_kpot -
Trickbot x86 loader 1 IoCs
Detected Trickbot's x86 loader that unpacks the x86 payload.
resource yara_rule behavioral1/memory/2288-15-0x0000000000490000-0x00000000004B9000-memory.dmp trickbot_loader32 -
Executes dropped EXE 3 IoCs
pid Process 2764 f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe 2936 f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe 2120 f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe -
Loads dropped DLL 2 IoCs
pid Process 2288 f6764d8c3bdf43e73d258cb1e2853719a0f4d3c2ca1917f8b2538574a79b6599.exe 2288 f6764d8c3bdf43e73d258cb1e2853719a0f4d3c2ca1917f8b2538574a79b6599.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 2176 sc.exe 2720 sc.exe 2104 sc.exe 2828 sc.exe -
Suspicious behavior: EnumeratesProcesses 8 IoCs
pid Process 2288 f6764d8c3bdf43e73d258cb1e2853719a0f4d3c2ca1917f8b2538574a79b6599.exe 2288 f6764d8c3bdf43e73d258cb1e2853719a0f4d3c2ca1917f8b2538574a79b6599.exe 2288 f6764d8c3bdf43e73d258cb1e2853719a0f4d3c2ca1917f8b2538574a79b6599.exe 2764 f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe 2764 f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe 2764 f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe 2424 powershell.exe 2432 powershell.exe -
Suspicious use of AdjustPrivilegeToken 4 IoCs
description pid Process Token: SeDebugPrivilege 2424 powershell.exe Token: SeDebugPrivilege 2432 powershell.exe Token: SeTcbPrivilege 2936 f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe Token: SeTcbPrivilege 2120 f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe -
Suspicious use of SetWindowsHookEx 4 IoCs
pid Process 2288 f6764d8c3bdf43e73d258cb1e2853719a0f4d3c2ca1917f8b2538574a79b6599.exe 2764 f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe 2936 f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe 2120 f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe -
Suspicious use of WriteProcessMemory 64 IoCs
description pid Process procid_target PID 2288 wrote to memory of 2356 2288 f6764d8c3bdf43e73d258cb1e2853719a0f4d3c2ca1917f8b2538574a79b6599.exe 28 PID 2288 wrote to memory of 2356 2288 f6764d8c3bdf43e73d258cb1e2853719a0f4d3c2ca1917f8b2538574a79b6599.exe 28 PID 2288 wrote to memory of 2356 2288 f6764d8c3bdf43e73d258cb1e2853719a0f4d3c2ca1917f8b2538574a79b6599.exe 28 PID 2288 wrote to memory of 2356 2288 f6764d8c3bdf43e73d258cb1e2853719a0f4d3c2ca1917f8b2538574a79b6599.exe 28 PID 2288 wrote to memory of 2088 2288 f6764d8c3bdf43e73d258cb1e2853719a0f4d3c2ca1917f8b2538574a79b6599.exe 29 PID 2288 wrote to memory of 2088 2288 f6764d8c3bdf43e73d258cb1e2853719a0f4d3c2ca1917f8b2538574a79b6599.exe 29 PID 2288 wrote to memory of 2088 2288 f6764d8c3bdf43e73d258cb1e2853719a0f4d3c2ca1917f8b2538574a79b6599.exe 29 PID 2288 wrote to memory of 2088 2288 f6764d8c3bdf43e73d258cb1e2853719a0f4d3c2ca1917f8b2538574a79b6599.exe 29 PID 2288 wrote to memory of 2644 2288 f6764d8c3bdf43e73d258cb1e2853719a0f4d3c2ca1917f8b2538574a79b6599.exe 31 PID 2288 wrote to memory of 2644 2288 f6764d8c3bdf43e73d258cb1e2853719a0f4d3c2ca1917f8b2538574a79b6599.exe 31 PID 2288 wrote to memory of 2644 2288 f6764d8c3bdf43e73d258cb1e2853719a0f4d3c2ca1917f8b2538574a79b6599.exe 31 PID 2288 wrote to memory of 2644 2288 f6764d8c3bdf43e73d258cb1e2853719a0f4d3c2ca1917f8b2538574a79b6599.exe 31 PID 2288 wrote to memory of 2764 2288 f6764d8c3bdf43e73d258cb1e2853719a0f4d3c2ca1917f8b2538574a79b6599.exe 34 PID 2288 wrote to memory of 2764 2288 f6764d8c3bdf43e73d258cb1e2853719a0f4d3c2ca1917f8b2538574a79b6599.exe 34 PID 2288 wrote to memory of 2764 2288 f6764d8c3bdf43e73d258cb1e2853719a0f4d3c2ca1917f8b2538574a79b6599.exe 34 PID 2288 wrote to memory of 2764 2288 f6764d8c3bdf43e73d258cb1e2853719a0f4d3c2ca1917f8b2538574a79b6599.exe 34 PID 2356 wrote to memory of 2720 2356 cmd.exe 35 PID 2356 wrote to memory of 2720 2356 cmd.exe 35 PID 2356 wrote to memory of 2720 2356 cmd.exe 35 PID 2356 wrote to memory of 2720 2356 cmd.exe 35 PID 2088 wrote to memory of 2104 2088 cmd.exe 36 PID 2088 wrote to memory of 2104 2088 cmd.exe 36 PID 2088 wrote to memory of 2104 2088 cmd.exe 36 PID 2088 wrote to memory of 2104 2088 cmd.exe 36 PID 2644 wrote to memory of 2432 2644 cmd.exe 37 PID 2644 wrote to memory of 2432 2644 cmd.exe 37 PID 2644 wrote to memory of 2432 2644 cmd.exe 37 PID 2644 wrote to memory of 2432 2644 cmd.exe 37 PID 2764 wrote to memory of 2700 2764 f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe 38 PID 2764 wrote to memory of 2700 2764 f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe 38 PID 2764 wrote to memory of 2700 2764 f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe 38 PID 2764 wrote to memory of 2700 2764 f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe 38 PID 2764 wrote to memory of 768 2764 f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe 39 PID 2764 wrote to memory of 768 2764 f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe 39 PID 2764 wrote to memory of 768 2764 f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe 39 PID 2764 wrote to memory of 768 2764 f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe 39 PID 2764 wrote to memory of 2820 2764 f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe 40 PID 2764 wrote to memory of 2820 2764 f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe 40 PID 2764 wrote to memory of 2820 2764 f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe 40 PID 2764 wrote to memory of 2820 2764 f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe 40 PID 2764 wrote to memory of 2548 2764 f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe 41 PID 2764 wrote to memory of 2548 2764 f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe 41 PID 2764 wrote to memory of 2548 2764 f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe 41 PID 2764 wrote to memory of 2548 2764 f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe 41 PID 2764 wrote to memory of 2548 2764 f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe 41 PID 2764 wrote to memory of 2548 2764 f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe 41 PID 2764 wrote to memory of 2548 2764 f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe 41 PID 2764 wrote to memory of 2548 2764 f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe 41 PID 2764 wrote to memory of 2548 2764 f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe 41 PID 2764 wrote to memory of 2548 2764 f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe 41 PID 2764 wrote to memory of 2548 2764 f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe 41 PID 2764 wrote to memory of 2548 2764 f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe 41 PID 2764 wrote to memory of 2548 2764 f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe 41 PID 2764 wrote to memory of 2548 2764 f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe 41 PID 2764 wrote to memory of 2548 2764 f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe 41 PID 2764 wrote to memory of 2548 2764 f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe 41 PID 2764 wrote to memory of 2548 2764 f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe 41 PID 2764 wrote to memory of 2548 2764 f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe 41 PID 2764 wrote to memory of 2548 2764 f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe 41 PID 2764 wrote to memory of 2548 2764 f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe 41 PID 2764 wrote to memory of 2548 2764 f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe 41 PID 2764 wrote to memory of 2548 2764 f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe 41 PID 2764 wrote to memory of 2548 2764 f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe 41 PID 2764 wrote to memory of 2548 2764 f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe 41 -
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\f6764d8c3bdf43e73d258cb1e2853719a0f4d3c2ca1917f8b2538574a79b6599.exe"C:\Users\Admin\AppData\Local\Temp\f6764d8c3bdf43e73d258cb1e2853719a0f4d3c2ca1917f8b2538574a79b6599.exe"1⤵
- Loads dropped DLL
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2288 -
C:\Windows\SysWOW64\cmd.exe/c sc stop WinDefend2⤵
- Suspicious use of WriteProcessMemory
PID:2356 -
C:\Windows\SysWOW64\sc.exesc stop WinDefend3⤵
- Launches sc.exe
PID:2720
-
-
-
C:\Windows\SysWOW64\cmd.exe/c sc delete WinDefend2⤵
- Suspicious use of WriteProcessMemory
PID:2088 -
C:\Windows\SysWOW64\sc.exesc delete WinDefend3⤵
- Launches sc.exe
PID:2104
-
-
-
C:\Windows\SysWOW64\cmd.exe/c powershell Set-MpPreference -DisableRealtimeMonitoring $true2⤵
- Suspicious use of WriteProcessMemory
PID:2644 -
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:2432
-
-
-
C:\Users\Admin\AppData\Roaming\WinSocket\f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exeC:\Users\Admin\AppData\Roaming\WinSocket\f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe2⤵
- Executes dropped EXE
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2764 -
C:\Windows\SysWOW64\cmd.exe/c sc stop WinDefend3⤵PID:2700
-
C:\Windows\SysWOW64\sc.exesc stop WinDefend4⤵
- Launches sc.exe
PID:2828
-
-
-
C:\Windows\SysWOW64\cmd.exe/c sc delete WinDefend3⤵PID:768
-
C:\Windows\SysWOW64\sc.exesc delete WinDefend4⤵
- Launches sc.exe
PID:2176
-
-
-
C:\Windows\SysWOW64\cmd.exe/c powershell Set-MpPreference -DisableRealtimeMonitoring $true3⤵PID:2820
-
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:2424
-
-
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:2548
-
-
-
C:\Windows\system32\taskeng.exetaskeng.exe {8E233408-49B2-427E-934D-5188247CDACC} S-1-5-18:NT AUTHORITY\System:Service:1⤵PID:2092
-
C:\Users\Admin\AppData\Roaming\WinSocket\f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exeC:\Users\Admin\AppData\Roaming\WinSocket\f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe2⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
PID:2936 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:1660
-
-
-
C:\Users\Admin\AppData\Roaming\WinSocket\f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exeC:\Users\Admin\AppData\Roaming\WinSocket\f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe2⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
PID:2120 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:1904
-
-
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
MD5cc2f7b2368c567f1276031fdf867f5be
SHA16f3a278101784299bfca4c22674138351c975ead
SHA2565094a4b011f2aace6d5da3d2fc1c682fba4deb9ae4eb724891b08885829da48a
SHA512e9e788c2ce00556b227f35dcff3e5d7e97f78f74eabe4fd9072fb2badfe4aaf9d059b551d5755d7aee1327025983b6553f2fb781e4ae2c2c515b9fe214dfd18c
-
\Users\Admin\AppData\Roaming\WinSocket\f7874d9c3bdf43e83d269cb1e2963819a0f4d3c2ca1918f9b2639684a89b7699.exe
Filesize1.1MB
MD5e2033482b1fe8d03a3fb8a16a7c99134
SHA1be42717d3bf76893aad0ffd3ecce1c534ff4ef83
SHA256f6764d8c3bdf43e73d258cb1e2853719a0f4d3c2ca1917f8b2538574a79b6599
SHA512f89f9e42703ae7a3034b4a0f87ce8b505b1751295a631c626462ba7323189d0bc6fa0a80c203a8201de82c58507722f11712ac9b647460bb2c265a694766aaf5