Analysis
-
max time kernel
135s -
max time network
121s -
platform
windows7_x64 -
resource
win7-20240419-en -
resource tags
arch:x64arch:x86image:win7-20240419-enlocale:en-usos:windows7-x64system -
submitted
25-05-2024 19:56
Behavioral task
behavioral1
Sample
2ad21f5d6f2a3d8f969f00962b95e6b19aaf13e932c00bcc14acf057176d1e16.exe
Resource
win7-20240419-en
General
-
Target
2ad21f5d6f2a3d8f969f00962b95e6b19aaf13e932c00bcc14acf057176d1e16.exe
-
Size
1.3MB
-
MD5
4fce9750489bad1288f98987d06b252f
-
SHA1
6d74e9efdd1965525d93b7291200688c9ba82f4d
-
SHA256
2ad21f5d6f2a3d8f969f00962b95e6b19aaf13e932c00bcc14acf057176d1e16
-
SHA512
e076d5b5cd0db969d5d15905d33f1079f63bac0031a742ba80327f648643ba73e1d2c9cd617f6be660590d21fb73fee1d0be5b62c2e45b146b52cf510d6f5544
-
SSDEEP
24576:zQ5aILMCfmAUjzX6xQGCZLFdGm1SdrzRjVYaQ/n2lbcMfcz5l8ut:E5aIwC+Agr6S/FYqOc2ZE
Malware Config
Signatures
-
KPOT Core Executable 1 IoCs
Processes:
resource yara_rule \Users\Admin\AppData\Roaming\WinSocket\2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe family_kpot -
Trickbot x86 loader 1 IoCs
Detected Trickbot's x86 loader that unpacks the x86 payload.
Processes:
resource yara_rule behavioral1/memory/2844-15-0x00000000003B0000-0x00000000003D9000-memory.dmp trickbot_loader32 -
Executes dropped EXE 3 IoCs
Processes:
2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exepid process 2480 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe 576 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe 2852 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe -
Loads dropped DLL 2 IoCs
Processes:
2ad21f5d6f2a3d8f969f00962b95e6b19aaf13e932c00bcc14acf057176d1e16.exepid process 2844 2ad21f5d6f2a3d8f969f00962b95e6b19aaf13e932c00bcc14acf057176d1e16.exe 2844 2ad21f5d6f2a3d8f969f00962b95e6b19aaf13e932c00bcc14acf057176d1e16.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 2488 sc.exe 2788 sc.exe 2572 sc.exe 2468 sc.exe -
Suspicious behavior: EnumeratesProcesses 8 IoCs
Processes:
2ad21f5d6f2a3d8f969f00962b95e6b19aaf13e932c00bcc14acf057176d1e16.exe2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exepowershell.exepowershell.exepid process 2844 2ad21f5d6f2a3d8f969f00962b95e6b19aaf13e932c00bcc14acf057176d1e16.exe 2844 2ad21f5d6f2a3d8f969f00962b95e6b19aaf13e932c00bcc14acf057176d1e16.exe 2844 2ad21f5d6f2a3d8f969f00962b95e6b19aaf13e932c00bcc14acf057176d1e16.exe 2480 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe 2480 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe 2480 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe 816 powershell.exe 2764 powershell.exe -
Suspicious use of AdjustPrivilegeToken 4 IoCs
Processes:
powershell.exepowershell.exe2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exedescription pid process Token: SeDebugPrivilege 816 powershell.exe Token: SeDebugPrivilege 2764 powershell.exe Token: SeTcbPrivilege 576 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe Token: SeTcbPrivilege 2852 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe -
Suspicious use of SetWindowsHookEx 4 IoCs
Processes:
2ad21f5d6f2a3d8f969f00962b95e6b19aaf13e932c00bcc14acf057176d1e16.exe2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exepid process 2844 2ad21f5d6f2a3d8f969f00962b95e6b19aaf13e932c00bcc14acf057176d1e16.exe 2480 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe 576 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe 2852 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe -
Suspicious use of WriteProcessMemory 64 IoCs
Processes:
2ad21f5d6f2a3d8f969f00962b95e6b19aaf13e932c00bcc14acf057176d1e16.execmd.exe2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.execmd.execmd.exedescription pid process target process PID 2844 wrote to memory of 2696 2844 2ad21f5d6f2a3d8f969f00962b95e6b19aaf13e932c00bcc14acf057176d1e16.exe cmd.exe PID 2844 wrote to memory of 2696 2844 2ad21f5d6f2a3d8f969f00962b95e6b19aaf13e932c00bcc14acf057176d1e16.exe cmd.exe PID 2844 wrote to memory of 2696 2844 2ad21f5d6f2a3d8f969f00962b95e6b19aaf13e932c00bcc14acf057176d1e16.exe cmd.exe PID 2844 wrote to memory of 2696 2844 2ad21f5d6f2a3d8f969f00962b95e6b19aaf13e932c00bcc14acf057176d1e16.exe cmd.exe PID 2844 wrote to memory of 2720 2844 2ad21f5d6f2a3d8f969f00962b95e6b19aaf13e932c00bcc14acf057176d1e16.exe cmd.exe PID 2844 wrote to memory of 2720 2844 2ad21f5d6f2a3d8f969f00962b95e6b19aaf13e932c00bcc14acf057176d1e16.exe cmd.exe PID 2844 wrote to memory of 2720 2844 2ad21f5d6f2a3d8f969f00962b95e6b19aaf13e932c00bcc14acf057176d1e16.exe cmd.exe PID 2844 wrote to memory of 2720 2844 2ad21f5d6f2a3d8f969f00962b95e6b19aaf13e932c00bcc14acf057176d1e16.exe cmd.exe PID 2844 wrote to memory of 2624 2844 2ad21f5d6f2a3d8f969f00962b95e6b19aaf13e932c00bcc14acf057176d1e16.exe cmd.exe PID 2844 wrote to memory of 2624 2844 2ad21f5d6f2a3d8f969f00962b95e6b19aaf13e932c00bcc14acf057176d1e16.exe cmd.exe PID 2844 wrote to memory of 2624 2844 2ad21f5d6f2a3d8f969f00962b95e6b19aaf13e932c00bcc14acf057176d1e16.exe cmd.exe PID 2844 wrote to memory of 2624 2844 2ad21f5d6f2a3d8f969f00962b95e6b19aaf13e932c00bcc14acf057176d1e16.exe cmd.exe PID 2844 wrote to memory of 2480 2844 2ad21f5d6f2a3d8f969f00962b95e6b19aaf13e932c00bcc14acf057176d1e16.exe 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe PID 2844 wrote to memory of 2480 2844 2ad21f5d6f2a3d8f969f00962b95e6b19aaf13e932c00bcc14acf057176d1e16.exe 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe PID 2844 wrote to memory of 2480 2844 2ad21f5d6f2a3d8f969f00962b95e6b19aaf13e932c00bcc14acf057176d1e16.exe 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe PID 2844 wrote to memory of 2480 2844 2ad21f5d6f2a3d8f969f00962b95e6b19aaf13e932c00bcc14acf057176d1e16.exe 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe PID 2720 wrote to memory of 2468 2720 cmd.exe sc.exe PID 2720 wrote to memory of 2468 2720 cmd.exe sc.exe PID 2720 wrote to memory of 2468 2720 cmd.exe sc.exe PID 2720 wrote to memory of 2468 2720 cmd.exe sc.exe PID 2480 wrote to memory of 2516 2480 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe cmd.exe PID 2480 wrote to memory of 2516 2480 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe cmd.exe PID 2480 wrote to memory of 2516 2480 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe cmd.exe PID 2480 wrote to memory of 2516 2480 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe cmd.exe PID 2480 wrote to memory of 2548 2480 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe cmd.exe PID 2480 wrote to memory of 2548 2480 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe cmd.exe PID 2480 wrote to memory of 2548 2480 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe cmd.exe PID 2480 wrote to memory of 2548 2480 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe cmd.exe PID 2696 wrote to memory of 2488 2696 cmd.exe sc.exe PID 2696 wrote to memory of 2488 2696 cmd.exe sc.exe PID 2696 wrote to memory of 2488 2696 cmd.exe sc.exe PID 2696 wrote to memory of 2488 2696 cmd.exe sc.exe PID 2480 wrote to memory of 2592 2480 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe cmd.exe PID 2480 wrote to memory of 2592 2480 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe cmd.exe PID 2480 wrote to memory of 2592 2480 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe cmd.exe PID 2480 wrote to memory of 2592 2480 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe cmd.exe PID 2480 wrote to memory of 2524 2480 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe svchost.exe PID 2480 wrote to memory of 2524 2480 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe svchost.exe PID 2480 wrote to memory of 2524 2480 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe svchost.exe PID 2480 wrote to memory of 2524 2480 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe svchost.exe PID 2480 wrote to memory of 2524 2480 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe svchost.exe PID 2480 wrote to memory of 2524 2480 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe svchost.exe PID 2480 wrote to memory of 2524 2480 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe svchost.exe PID 2624 wrote to memory of 816 2624 cmd.exe powershell.exe PID 2624 wrote to memory of 816 2624 cmd.exe powershell.exe PID 2624 wrote to memory of 816 2624 cmd.exe powershell.exe PID 2624 wrote to memory of 816 2624 cmd.exe powershell.exe PID 2480 wrote to memory of 2524 2480 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe svchost.exe PID 2480 wrote to memory of 2524 2480 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe svchost.exe PID 2480 wrote to memory of 2524 2480 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe svchost.exe PID 2480 wrote to memory of 2524 2480 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe svchost.exe PID 2480 wrote to memory of 2524 2480 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe svchost.exe PID 2480 wrote to memory of 2524 2480 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe svchost.exe PID 2480 wrote to memory of 2524 2480 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe svchost.exe PID 2480 wrote to memory of 2524 2480 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe svchost.exe PID 2480 wrote to memory of 2524 2480 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe svchost.exe PID 2480 wrote to memory of 2524 2480 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe svchost.exe PID 2480 wrote to memory of 2524 2480 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe svchost.exe PID 2480 wrote to memory of 2524 2480 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe svchost.exe PID 2480 wrote to memory of 2524 2480 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe svchost.exe PID 2480 wrote to memory of 2524 2480 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe svchost.exe PID 2480 wrote to memory of 2524 2480 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe svchost.exe PID 2480 wrote to memory of 2524 2480 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe svchost.exe PID 2480 wrote to memory of 2524 2480 2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.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\2ad21f5d6f2a3d8f969f00962b95e6b19aaf13e932c00bcc14acf057176d1e16.exe"C:\Users\Admin\AppData\Local\Temp\2ad21f5d6f2a3d8f969f00962b95e6b19aaf13e932c00bcc14acf057176d1e16.exe"1⤵
- Loads dropped DLL
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2844 -
C:\Windows\SysWOW64\cmd.exe/c sc stop WinDefend2⤵
- Suspicious use of WriteProcessMemory
PID:2696 -
C:\Windows\SysWOW64\sc.exesc stop WinDefend3⤵
- Launches sc.exe
PID:2488 -
C:\Windows\SysWOW64\cmd.exe/c sc delete WinDefend2⤵
- Suspicious use of WriteProcessMemory
PID:2720 -
C:\Windows\SysWOW64\sc.exesc delete WinDefend3⤵
- Launches sc.exe
PID:2468 -
C:\Windows\SysWOW64\cmd.exe/c powershell Set-MpPreference -DisableRealtimeMonitoring $true2⤵
- Suspicious use of WriteProcessMemory
PID:2624 -
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:816 -
C:\Users\Admin\AppData\Roaming\WinSocket\2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exeC:\Users\Admin\AppData\Roaming\WinSocket\2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe2⤵
- Executes dropped EXE
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2480 -
C:\Windows\SysWOW64\cmd.exe/c sc stop WinDefend3⤵PID:2516
-
C:\Windows\SysWOW64\sc.exesc stop WinDefend4⤵
- Launches sc.exe
PID:2572 -
C:\Windows\SysWOW64\cmd.exe/c sc delete WinDefend3⤵PID:2548
-
C:\Windows\SysWOW64\sc.exesc delete WinDefend4⤵
- Launches sc.exe
PID:2788 -
C:\Windows\SysWOW64\cmd.exe/c powershell Set-MpPreference -DisableRealtimeMonitoring $true3⤵PID:2592
-
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:2764 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:2524
-
C:\Windows\system32\taskeng.exetaskeng.exe {6F305B59-A46A-412F-B18D-6885B05C0AD4} S-1-5-18:NT AUTHORITY\System:Service:1⤵PID:548
-
C:\Users\Admin\AppData\Roaming\WinSocket\2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exeC:\Users\Admin\AppData\Roaming\WinSocket\2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe2⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
PID:576 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:2432
-
C:\Users\Admin\AppData\Roaming\WinSocket\2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exeC:\Users\Admin\AppData\Roaming\WinSocket\2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe2⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
PID:2852 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:2160
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
MD520ffaa563c9a7c9c4d1d5970fc04d007
SHA10f2d20e4072874b743f75fec45b61ea45bac6aca
SHA256b6ec32341dea9c9922656c3a761432151033e75101e5f0a50cbbdac3b3b55171
SHA512aebef5273729d26e4ff94b4232a06b5fddc186bc38c50c525e6decff23d3b6b8749a6155d5b5b466ea29490a84a508b0b0d1bbd5396b69254d1c163612b20675
-
\Users\Admin\AppData\Roaming\WinSocket\2ad21f6d7f2a3d9f979f00972b96e7b19aaf13e932c00bcc14acf068187d1e17.exe
Filesize1.3MB
MD54fce9750489bad1288f98987d06b252f
SHA16d74e9efdd1965525d93b7291200688c9ba82f4d
SHA2562ad21f5d6f2a3d8f969f00962b95e6b19aaf13e932c00bcc14acf057176d1e16
SHA512e076d5b5cd0db969d5d15905d33f1079f63bac0031a742ba80327f648643ba73e1d2c9cd617f6be660590d21fb73fee1d0be5b62c2e45b146b52cf510d6f5544