Analysis
-
max time kernel
135s -
max time network
117s -
platform
windows7_x64 -
resource
win7-20240221-en -
resource tags
arch:x64arch:x86image:win7-20240221-enlocale:en-usos:windows7-x64system -
submitted
05-05-2024 03:41
Behavioral task
behavioral1
Sample
bb3dd78596475cc7c72f8039e221ef4fb2ab0604f6b81a4dfe6d0281f4b65ba3.exe
Resource
win7-20240221-en
General
-
Target
bb3dd78596475cc7c72f8039e221ef4fb2ab0604f6b81a4dfe6d0281f4b65ba3.exe
-
Size
1.3MB
-
MD5
c480908dbb73f40acfe629f08a7bdeb5
-
SHA1
234f593a4c607d5f202a9e6eed8dd46061c880a2
-
SHA256
bb3dd78596475cc7c72f8039e221ef4fb2ab0604f6b81a4dfe6d0281f4b65ba3
-
SHA512
d6c9c8ea13df5f60f921521f6c3896848750a6fc915850eb848b242c8ee62ceccbac0addc2828ebf36f22d684562a8f710a739d66586c27d295d6a5e304095dd
-
SSDEEP
24576:zQ5aILMCfmAUjzX6gfU1pjwjbsXhmvZssrD+nRgnf4NvlOS2e:E5aIwC+Agr6g81p1vsrNiL
Malware Config
Signatures
-
KPOT Core Executable 1 IoCs
Processes:
resource yara_rule C:\Users\Admin\AppData\Roaming\WinSocket\bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe family_kpot -
Trickbot x86 loader 1 IoCs
Detected Trickbot's x86 loader that unpacks the x86 payload.
Processes:
resource yara_rule behavioral1/memory/2272-15-0x0000000000330000-0x0000000000359000-memory.dmp trickbot_loader32 -
Executes dropped EXE 3 IoCs
Processes:
bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exebb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exebb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exepid process 2664 bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe 2808 bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe 1052 bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe -
Loads dropped DLL 2 IoCs
Processes:
bb3dd78596475cc7c72f8039e221ef4fb2ab0604f6b81a4dfe6d0281f4b65ba3.exepid process 2272 bb3dd78596475cc7c72f8039e221ef4fb2ab0604f6b81a4dfe6d0281f4b65ba3.exe 2272 bb3dd78596475cc7c72f8039e221ef4fb2ab0604f6b81a4dfe6d0281f4b65ba3.exe -
Drops file in System32 directory 1 IoCs
Processes:
powershell.exedescription 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.
Processes:
sc.exesc.exepid process 2696 sc.exe 1948 sc.exe -
Suspicious behavior: EnumeratesProcesses 4 IoCs
Processes:
bb3dd78596475cc7c72f8039e221ef4fb2ab0604f6b81a4dfe6d0281f4b65ba3.exepowershell.exepid process 2272 bb3dd78596475cc7c72f8039e221ef4fb2ab0604f6b81a4dfe6d0281f4b65ba3.exe 2272 bb3dd78596475cc7c72f8039e221ef4fb2ab0604f6b81a4dfe6d0281f4b65ba3.exe 2272 bb3dd78596475cc7c72f8039e221ef4fb2ab0604f6b81a4dfe6d0281f4b65ba3.exe 2568 powershell.exe -
Suspicious use of AdjustPrivilegeToken 3 IoCs
Processes:
powershell.exebb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exebb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exedescription pid process Token: SeDebugPrivilege 2568 powershell.exe Token: SeTcbPrivilege 2808 bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe Token: SeTcbPrivilege 1052 bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe -
Suspicious use of SetWindowsHookEx 4 IoCs
Processes:
bb3dd78596475cc7c72f8039e221ef4fb2ab0604f6b81a4dfe6d0281f4b65ba3.exebb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exebb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exebb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exepid process 2272 bb3dd78596475cc7c72f8039e221ef4fb2ab0604f6b81a4dfe6d0281f4b65ba3.exe 2664 bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe 2808 bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe 1052 bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe -
Suspicious use of WriteProcessMemory 64 IoCs
Processes:
bb3dd78596475cc7c72f8039e221ef4fb2ab0604f6b81a4dfe6d0281f4b65ba3.execmd.execmd.execmd.exebb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exetaskeng.exebb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exedescription pid process target process PID 2272 wrote to memory of 2600 2272 bb3dd78596475cc7c72f8039e221ef4fb2ab0604f6b81a4dfe6d0281f4b65ba3.exe cmd.exe PID 2272 wrote to memory of 2600 2272 bb3dd78596475cc7c72f8039e221ef4fb2ab0604f6b81a4dfe6d0281f4b65ba3.exe cmd.exe PID 2272 wrote to memory of 2600 2272 bb3dd78596475cc7c72f8039e221ef4fb2ab0604f6b81a4dfe6d0281f4b65ba3.exe cmd.exe PID 2272 wrote to memory of 2600 2272 bb3dd78596475cc7c72f8039e221ef4fb2ab0604f6b81a4dfe6d0281f4b65ba3.exe cmd.exe PID 2272 wrote to memory of 2616 2272 bb3dd78596475cc7c72f8039e221ef4fb2ab0604f6b81a4dfe6d0281f4b65ba3.exe cmd.exe PID 2272 wrote to memory of 2616 2272 bb3dd78596475cc7c72f8039e221ef4fb2ab0604f6b81a4dfe6d0281f4b65ba3.exe cmd.exe PID 2272 wrote to memory of 2616 2272 bb3dd78596475cc7c72f8039e221ef4fb2ab0604f6b81a4dfe6d0281f4b65ba3.exe cmd.exe PID 2272 wrote to memory of 2616 2272 bb3dd78596475cc7c72f8039e221ef4fb2ab0604f6b81a4dfe6d0281f4b65ba3.exe cmd.exe PID 2272 wrote to memory of 2768 2272 bb3dd78596475cc7c72f8039e221ef4fb2ab0604f6b81a4dfe6d0281f4b65ba3.exe cmd.exe PID 2272 wrote to memory of 2768 2272 bb3dd78596475cc7c72f8039e221ef4fb2ab0604f6b81a4dfe6d0281f4b65ba3.exe cmd.exe PID 2272 wrote to memory of 2768 2272 bb3dd78596475cc7c72f8039e221ef4fb2ab0604f6b81a4dfe6d0281f4b65ba3.exe cmd.exe PID 2272 wrote to memory of 2768 2272 bb3dd78596475cc7c72f8039e221ef4fb2ab0604f6b81a4dfe6d0281f4b65ba3.exe cmd.exe PID 2272 wrote to memory of 2664 2272 bb3dd78596475cc7c72f8039e221ef4fb2ab0604f6b81a4dfe6d0281f4b65ba3.exe bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe PID 2272 wrote to memory of 2664 2272 bb3dd78596475cc7c72f8039e221ef4fb2ab0604f6b81a4dfe6d0281f4b65ba3.exe bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe PID 2272 wrote to memory of 2664 2272 bb3dd78596475cc7c72f8039e221ef4fb2ab0604f6b81a4dfe6d0281f4b65ba3.exe bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe PID 2272 wrote to memory of 2664 2272 bb3dd78596475cc7c72f8039e221ef4fb2ab0604f6b81a4dfe6d0281f4b65ba3.exe bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe PID 2768 wrote to memory of 2568 2768 cmd.exe powershell.exe PID 2768 wrote to memory of 2568 2768 cmd.exe powershell.exe PID 2768 wrote to memory of 2568 2768 cmd.exe powershell.exe PID 2768 wrote to memory of 2568 2768 cmd.exe powershell.exe PID 2616 wrote to memory of 1948 2616 cmd.exe sc.exe PID 2616 wrote to memory of 1948 2616 cmd.exe sc.exe PID 2616 wrote to memory of 1948 2616 cmd.exe sc.exe PID 2616 wrote to memory of 1948 2616 cmd.exe sc.exe PID 2600 wrote to memory of 2696 2600 cmd.exe sc.exe PID 2600 wrote to memory of 2696 2600 cmd.exe sc.exe PID 2600 wrote to memory of 2696 2600 cmd.exe sc.exe PID 2600 wrote to memory of 2696 2600 cmd.exe sc.exe PID 2664 wrote to memory of 2484 2664 bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe svchost.exe PID 2664 wrote to memory of 2484 2664 bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe svchost.exe PID 2664 wrote to memory of 2484 2664 bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe svchost.exe PID 2664 wrote to memory of 2484 2664 bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe svchost.exe PID 2664 wrote to memory of 2484 2664 bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe svchost.exe PID 2664 wrote to memory of 2484 2664 bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe svchost.exe PID 2664 wrote to memory of 2484 2664 bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe svchost.exe PID 2664 wrote to memory of 2484 2664 bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe svchost.exe PID 2664 wrote to memory of 2484 2664 bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe svchost.exe PID 2664 wrote to memory of 2484 2664 bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe svchost.exe PID 2664 wrote to memory of 2484 2664 bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe svchost.exe PID 2664 wrote to memory of 2484 2664 bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe svchost.exe PID 2664 wrote to memory of 2484 2664 bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe svchost.exe PID 2664 wrote to memory of 2484 2664 bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe svchost.exe PID 2664 wrote to memory of 2484 2664 bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe svchost.exe PID 2664 wrote to memory of 2484 2664 bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe svchost.exe PID 2664 wrote to memory of 2484 2664 bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe svchost.exe PID 2664 wrote to memory of 2484 2664 bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe svchost.exe PID 2664 wrote to memory of 2484 2664 bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe svchost.exe PID 2664 wrote to memory of 2484 2664 bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe svchost.exe PID 2664 wrote to memory of 2484 2664 bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe svchost.exe PID 2664 wrote to memory of 2484 2664 bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe svchost.exe PID 2664 wrote to memory of 2484 2664 bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe svchost.exe PID 2664 wrote to memory of 2484 2664 bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe svchost.exe PID 2664 wrote to memory of 2484 2664 bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe svchost.exe PID 2664 wrote to memory of 2484 2664 bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe svchost.exe PID 2664 wrote to memory of 2484 2664 bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe svchost.exe PID 2664 wrote to memory of 2484 2664 bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe svchost.exe PID 1048 wrote to memory of 2808 1048 taskeng.exe bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe PID 1048 wrote to memory of 2808 1048 taskeng.exe bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe PID 1048 wrote to memory of 2808 1048 taskeng.exe bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe PID 1048 wrote to memory of 2808 1048 taskeng.exe bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe PID 2808 wrote to memory of 2216 2808 bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe svchost.exe PID 2808 wrote to memory of 2216 2808 bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe svchost.exe PID 2808 wrote to memory of 2216 2808 bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe svchost.exe PID 2808 wrote to memory of 2216 2808 bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.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\bb3dd78596475cc7c72f8039e221ef4fb2ab0604f6b81a4dfe6d0281f4b65ba3.exe"C:\Users\Admin\AppData\Local\Temp\bb3dd78596475cc7c72f8039e221ef4fb2ab0604f6b81a4dfe6d0281f4b65ba3.exe"1⤵
- Loads dropped DLL
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2272 -
C:\Windows\SysWOW64\cmd.exe/c sc stop WinDefend2⤵
- Suspicious use of WriteProcessMemory
PID:2600 -
C:\Windows\SysWOW64\sc.exesc stop WinDefend3⤵
- Launches sc.exe
PID:2696 -
C:\Windows\SysWOW64\cmd.exe/c sc delete WinDefend2⤵
- Suspicious use of WriteProcessMemory
PID:2616 -
C:\Windows\SysWOW64\sc.exesc delete WinDefend3⤵
- Launches sc.exe
PID:1948 -
C:\Windows\SysWOW64\cmd.exe/c powershell Set-MpPreference -DisableRealtimeMonitoring $true2⤵
- Suspicious use of WriteProcessMemory
PID:2768 -
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:2568 -
C:\Users\Admin\AppData\Roaming\WinSocket\bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exeC:\Users\Admin\AppData\Roaming\WinSocket\bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe2⤵
- Executes dropped EXE
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2664 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:2484
-
C:\Windows\system32\taskeng.exetaskeng.exe {4F8410DE-39E3-4753-BD6F-2FB7BE85B216} S-1-5-18:NT AUTHORITY\System:Service:1⤵
- Suspicious use of WriteProcessMemory
PID:1048 -
C:\Users\Admin\AppData\Roaming\WinSocket\bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exeC:\Users\Admin\AppData\Roaming\WinSocket\bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe2⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2808 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:2216
-
C:\Users\Admin\AppData\Roaming\WinSocket\bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exeC:\Users\Admin\AppData\Roaming\WinSocket\bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe2⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
PID:1052 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:1328
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
-
C:\Users\Admin\AppData\Roaming\WinSocket\bb3dd89697486cc8c82f9039e221ef4fb2ab0704f7b91a4dfe7d0291f4b76ba3.exe
Filesize1.3MB
MD5c480908dbb73f40acfe629f08a7bdeb5
SHA1234f593a4c607d5f202a9e6eed8dd46061c880a2
SHA256bb3dd78596475cc7c72f8039e221ef4fb2ab0604f6b81a4dfe6d0281f4b65ba3
SHA512d6c9c8ea13df5f60f921521f6c3896848750a6fc915850eb848b242c8ee62ceccbac0addc2828ebf36f22d684562a8f710a739d66586c27d295d6a5e304095dd