Analysis
-
max time kernel
135s -
max time network
123s -
platform
windows7_x64 -
resource
win7-20240221-en -
resource tags
arch:x64arch:x86image:win7-20240221-enlocale:en-usos:windows7-x64system -
submitted
26-05-2024 22:08
Static task
static1
Behavioral task
behavioral1
Sample
5c246950929e7fec4fa07f2013b47e8ec22f2e5f5d471ed66d5c21e416322a7a.exe
Resource
win7-20240221-en
General
-
Target
5c246950929e7fec4fa07f2013b47e8ec22f2e5f5d471ed66d5c21e416322a7a.exe
-
Size
1.0MB
-
MD5
927d36ed02f7d228b7beac6727859967
-
SHA1
0044ec8a45f2dd81d799a36400f24bfaecec0379
-
SHA256
5c246950929e7fec4fa07f2013b47e8ec22f2e5f5d471ed66d5c21e416322a7a
-
SHA512
0c2b3542cd06c3656043d9b2156eb42003123c082636e6c26a9382b21620b0260f4c7faf9e4871a4b23ec341dcbba7cce2416901f508dac30401c69a4056dc67
-
SSDEEP
24576:zQ5aILMCfmAUhrSO1YNWdvCzMPqdUD6dNDmwRev:E5aIwC+AUBsWsXH+
Malware Config
Signatures
-
Trickbot x86 loader 1 IoCs
Detected Trickbot's x86 loader that unpacks the x86 payload.
resource yara_rule behavioral1/memory/2220-15-0x00000000003A0000-0x00000000003C9000-memory.dmp trickbot_loader32 -
Executes dropped EXE 3 IoCs
pid Process 2588 6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe 2412 6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe 1044 6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe -
Loads dropped DLL 2 IoCs
pid Process 2220 5c246950929e7fec4fa07f2013b47e8ec22f2e5f5d471ed66d5c21e416322a7a.exe 2220 5c246950929e7fec4fa07f2013b47e8ec22f2e5f5d471ed66d5c21e416322a7a.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 2584 sc.exe 2888 sc.exe 2976 sc.exe 3060 sc.exe -
Suspicious behavior: EnumeratesProcesses 8 IoCs
pid Process 2220 5c246950929e7fec4fa07f2013b47e8ec22f2e5f5d471ed66d5c21e416322a7a.exe 2220 5c246950929e7fec4fa07f2013b47e8ec22f2e5f5d471ed66d5c21e416322a7a.exe 2220 5c246950929e7fec4fa07f2013b47e8ec22f2e5f5d471ed66d5c21e416322a7a.exe 2588 6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe 2588 6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe 2588 6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe 2992 powershell.exe 2560 powershell.exe -
Suspicious use of AdjustPrivilegeToken 4 IoCs
description pid Process Token: SeDebugPrivilege 2992 powershell.exe Token: SeDebugPrivilege 2560 powershell.exe Token: SeTcbPrivilege 2412 6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe Token: SeTcbPrivilege 1044 6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe -
Suspicious use of SetWindowsHookEx 4 IoCs
pid Process 2220 5c246950929e7fec4fa07f2013b47e8ec22f2e5f5d471ed66d5c21e416322a7a.exe 2588 6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe 2412 6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe 1044 6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe -
Suspicious use of WriteProcessMemory 64 IoCs
description pid Process procid_target PID 2220 wrote to memory of 3068 2220 5c246950929e7fec4fa07f2013b47e8ec22f2e5f5d471ed66d5c21e416322a7a.exe 28 PID 2220 wrote to memory of 3068 2220 5c246950929e7fec4fa07f2013b47e8ec22f2e5f5d471ed66d5c21e416322a7a.exe 28 PID 2220 wrote to memory of 3068 2220 5c246950929e7fec4fa07f2013b47e8ec22f2e5f5d471ed66d5c21e416322a7a.exe 28 PID 2220 wrote to memory of 3068 2220 5c246950929e7fec4fa07f2013b47e8ec22f2e5f5d471ed66d5c21e416322a7a.exe 28 PID 2220 wrote to memory of 2860 2220 5c246950929e7fec4fa07f2013b47e8ec22f2e5f5d471ed66d5c21e416322a7a.exe 29 PID 2220 wrote to memory of 2860 2220 5c246950929e7fec4fa07f2013b47e8ec22f2e5f5d471ed66d5c21e416322a7a.exe 29 PID 2220 wrote to memory of 2860 2220 5c246950929e7fec4fa07f2013b47e8ec22f2e5f5d471ed66d5c21e416322a7a.exe 29 PID 2220 wrote to memory of 2860 2220 5c246950929e7fec4fa07f2013b47e8ec22f2e5f5d471ed66d5c21e416322a7a.exe 29 PID 2220 wrote to memory of 2376 2220 5c246950929e7fec4fa07f2013b47e8ec22f2e5f5d471ed66d5c21e416322a7a.exe 32 PID 2220 wrote to memory of 2376 2220 5c246950929e7fec4fa07f2013b47e8ec22f2e5f5d471ed66d5c21e416322a7a.exe 32 PID 2220 wrote to memory of 2376 2220 5c246950929e7fec4fa07f2013b47e8ec22f2e5f5d471ed66d5c21e416322a7a.exe 32 PID 2220 wrote to memory of 2376 2220 5c246950929e7fec4fa07f2013b47e8ec22f2e5f5d471ed66d5c21e416322a7a.exe 32 PID 2220 wrote to memory of 2588 2220 5c246950929e7fec4fa07f2013b47e8ec22f2e5f5d471ed66d5c21e416322a7a.exe 34 PID 2220 wrote to memory of 2588 2220 5c246950929e7fec4fa07f2013b47e8ec22f2e5f5d471ed66d5c21e416322a7a.exe 34 PID 2220 wrote to memory of 2588 2220 5c246950929e7fec4fa07f2013b47e8ec22f2e5f5d471ed66d5c21e416322a7a.exe 34 PID 2220 wrote to memory of 2588 2220 5c246950929e7fec4fa07f2013b47e8ec22f2e5f5d471ed66d5c21e416322a7a.exe 34 PID 3068 wrote to memory of 2584 3068 cmd.exe 36 PID 3068 wrote to memory of 2584 3068 cmd.exe 36 PID 3068 wrote to memory of 2584 3068 cmd.exe 36 PID 3068 wrote to memory of 2584 3068 cmd.exe 36 PID 2860 wrote to memory of 2888 2860 cmd.exe 35 PID 2860 wrote to memory of 2888 2860 cmd.exe 35 PID 2860 wrote to memory of 2888 2860 cmd.exe 35 PID 2860 wrote to memory of 2888 2860 cmd.exe 35 PID 2376 wrote to memory of 2560 2376 cmd.exe 37 PID 2376 wrote to memory of 2560 2376 cmd.exe 37 PID 2376 wrote to memory of 2560 2376 cmd.exe 37 PID 2376 wrote to memory of 2560 2376 cmd.exe 37 PID 2588 wrote to memory of 2824 2588 6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe 38 PID 2588 wrote to memory of 2824 2588 6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe 38 PID 2588 wrote to memory of 2824 2588 6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe 38 PID 2588 wrote to memory of 2824 2588 6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe 38 PID 2588 wrote to memory of 3056 2588 6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe 39 PID 2588 wrote to memory of 3056 2588 6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe 39 PID 2588 wrote to memory of 3056 2588 6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe 39 PID 2588 wrote to memory of 3056 2588 6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe 39 PID 2588 wrote to memory of 2568 2588 6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe 40 PID 2588 wrote to memory of 2568 2588 6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe 40 PID 2588 wrote to memory of 2568 2588 6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe 40 PID 2588 wrote to memory of 2568 2588 6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe 40 PID 2588 wrote to memory of 2496 2588 6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe 42 PID 2588 wrote to memory of 2496 2588 6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe 42 PID 2588 wrote to memory of 2496 2588 6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe 42 PID 2588 wrote to memory of 2496 2588 6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe 42 PID 2588 wrote to memory of 2496 2588 6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe 42 PID 2588 wrote to memory of 2496 2588 6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe 42 PID 2588 wrote to memory of 2496 2588 6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe 42 PID 2588 wrote to memory of 2496 2588 6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe 42 PID 2588 wrote to memory of 2496 2588 6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe 42 PID 2588 wrote to memory of 2496 2588 6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe 42 PID 2588 wrote to memory of 2496 2588 6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe 42 PID 2588 wrote to memory of 2496 2588 6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe 42 PID 2588 wrote to memory of 2496 2588 6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe 42 PID 2588 wrote to memory of 2496 2588 6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe 42 PID 2588 wrote to memory of 2496 2588 6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe 42 PID 2588 wrote to memory of 2496 2588 6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe 42 PID 2588 wrote to memory of 2496 2588 6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe 42 PID 2588 wrote to memory of 2496 2588 6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe 42 PID 2588 wrote to memory of 2496 2588 6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe 42 PID 2588 wrote to memory of 2496 2588 6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe 42 PID 2588 wrote to memory of 2496 2588 6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe 42 PID 2588 wrote to memory of 2496 2588 6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe 42 PID 2588 wrote to memory of 2496 2588 6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe 42 PID 2588 wrote to memory of 2496 2588 6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe 42 -
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\5c246950929e7fec4fa07f2013b47e8ec22f2e5f5d471ed66d5c21e416322a7a.exe"C:\Users\Admin\AppData\Local\Temp\5c246950929e7fec4fa07f2013b47e8ec22f2e5f5d471ed66d5c21e416322a7a.exe"1⤵
- Loads dropped DLL
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2220 -
C:\Windows\SysWOW64\cmd.exe/c sc stop WinDefend2⤵
- Suspicious use of WriteProcessMemory
PID:3068 -
C:\Windows\SysWOW64\sc.exesc stop WinDefend3⤵
- Launches sc.exe
PID:2584
-
-
-
C:\Windows\SysWOW64\cmd.exe/c sc delete WinDefend2⤵
- Suspicious use of WriteProcessMemory
PID:2860 -
C:\Windows\SysWOW64\sc.exesc delete WinDefend3⤵
- Launches sc.exe
PID:2888
-
-
-
C:\Windows\SysWOW64\cmd.exe/c powershell Set-MpPreference -DisableRealtimeMonitoring $true2⤵
- Suspicious use of WriteProcessMemory
PID:2376 -
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:2560
-
-
-
C:\Users\Admin\AppData\Roaming\WinSocket\6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exeC:\Users\Admin\AppData\Roaming\WinSocket\6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe2⤵
- Executes dropped EXE
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2588 -
C:\Windows\SysWOW64\cmd.exe/c sc stop WinDefend3⤵PID:2824
-
C:\Windows\SysWOW64\sc.exesc stop WinDefend4⤵
- Launches sc.exe
PID:2976
-
-
-
C:\Windows\SysWOW64\cmd.exe/c sc delete WinDefend3⤵PID:3056
-
C:\Windows\SysWOW64\sc.exesc delete WinDefend4⤵
- Launches sc.exe
PID:3060
-
-
-
C:\Windows\SysWOW64\cmd.exe/c powershell Set-MpPreference -DisableRealtimeMonitoring $true3⤵PID:2568
-
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:2992
-
-
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:2496
-
-
-
C:\Windows\system32\taskeng.exetaskeng.exe {9111A21F-5363-4EFC-98C1-CCCCB45F47F7} S-1-5-18:NT AUTHORITY\System:Service:1⤵PID:1780
-
C:\Users\Admin\AppData\Roaming\WinSocket\6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exeC:\Users\Admin\AppData\Roaming\WinSocket\6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe2⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
PID:2412 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:1716
-
-
-
C:\Users\Admin\AppData\Roaming\WinSocket\6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exeC:\Users\Admin\AppData\Roaming\WinSocket\6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe2⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
PID:1044 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:2024
-
-
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
MD502894c2127fdd6a4e7d4f5dcc9397777
SHA1886d43b3609cf4a30bf2b9b5de98d3821eb20492
SHA25643870b93a1ea02c1566ff8cd8150109eef012fdd702da796cbd7f53b7a4fa9b7
SHA5123b31383b4311c7a097565e0b25d3ddb3297368cbde051835d9e4a8285ec5b6ccfc12700215e85b7ee4e02facb6220203506f83a5e9f4bd4c67d791fd81367171
-
\Users\Admin\AppData\Roaming\WinSocket\6c247960929e8fec4fa08f2013b48e9ec22f2e6f6d481ed77d6c21e417322a8a.exe
Filesize1.0MB
MD5927d36ed02f7d228b7beac6727859967
SHA10044ec8a45f2dd81d799a36400f24bfaecec0379
SHA2565c246950929e7fec4fa07f2013b47e8ec22f2e5f5d471ed66d5c21e416322a7a
SHA5120c2b3542cd06c3656043d9b2156eb42003123c082636e6c26a9382b21620b0260f4c7faf9e4871a4b23ec341dcbba7cce2416901f508dac30401c69a4056dc67