Analysis
-
max time kernel
135s -
max time network
119s -
platform
windows7_x64 -
resource
win7-20240508-en -
resource tags
arch:x64arch:x86image:win7-20240508-enlocale:en-usos:windows7-x64system -
submitted
26-05-2024 21:04
Static task
static1
Behavioral task
behavioral1
Sample
426fb7b515cef8db65ef38980d8cc0b01fc12084f0bd7a33e4290e9fb1ed043c.exe
Resource
win7-20240508-en
General
-
Target
426fb7b515cef8db65ef38980d8cc0b01fc12084f0bd7a33e4290e9fb1ed043c.exe
-
Size
1.0MB
-
MD5
2cc9e1d0e03ca6a0998f1361282ae394
-
SHA1
e690dfceb4da060def5ff7f28d10c6652a1766e3
-
SHA256
426fb7b515cef8db65ef38980d8cc0b01fc12084f0bd7a33e4290e9fb1ed043c
-
SHA512
511fe4f163ac85f7c6fa4c8009c545313bdaf9519d7aabf12b805a9de0de40f13fbda760ab49f1daf0746d6e41592bbdf0388dca5a8e2437b71e5b7e2bd2715e
-
SSDEEP
24576:zQ5aILMCfmAUhrSO1YNWdvCzMPqdUD6dNDmwi+j0:E5aIwC+AUBsWsXHLw
Malware Config
Signatures
-
Trickbot x86 loader 1 IoCs
Detected Trickbot's x86 loader that unpacks the x86 payload.
resource yara_rule behavioral1/memory/2368-15-0x0000000000370000-0x0000000000399000-memory.dmp trickbot_loader32 -
Executes dropped EXE 3 IoCs
pid Process 2584 427fb8b616cef9db76ef39990d9cc0b01fc12094f0bd8a33e4290e9fb1ed043c.exe 584 427fb8b616cef9db76ef39990d9cc0b01fc12094f0bd8a33e4290e9fb1ed043c.exe 2280 427fb8b616cef9db76ef39990d9cc0b01fc12094f0bd8a33e4290e9fb1ed043c.exe -
Loads dropped DLL 2 IoCs
pid Process 2368 426fb7b515cef8db65ef38980d8cc0b01fc12084f0bd7a33e4290e9fb1ed043c.exe 2368 426fb7b515cef8db65ef38980d8cc0b01fc12084f0bd7a33e4290e9fb1ed043c.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 1712 sc.exe 2472 sc.exe -
Suspicious behavior: EnumeratesProcesses 4 IoCs
pid Process 2368 426fb7b515cef8db65ef38980d8cc0b01fc12084f0bd7a33e4290e9fb1ed043c.exe 2368 426fb7b515cef8db65ef38980d8cc0b01fc12084f0bd7a33e4290e9fb1ed043c.exe 2368 426fb7b515cef8db65ef38980d8cc0b01fc12084f0bd7a33e4290e9fb1ed043c.exe 2732 powershell.exe -
Suspicious use of AdjustPrivilegeToken 3 IoCs
description pid Process Token: SeDebugPrivilege 2732 powershell.exe Token: SeTcbPrivilege 584 427fb8b616cef9db76ef39990d9cc0b01fc12094f0bd8a33e4290e9fb1ed043c.exe Token: SeTcbPrivilege 2280 427fb8b616cef9db76ef39990d9cc0b01fc12094f0bd8a33e4290e9fb1ed043c.exe -
Suspicious use of SetWindowsHookEx 4 IoCs
pid Process 2368 426fb7b515cef8db65ef38980d8cc0b01fc12084f0bd7a33e4290e9fb1ed043c.exe 2584 427fb8b616cef9db76ef39990d9cc0b01fc12094f0bd8a33e4290e9fb1ed043c.exe 584 427fb8b616cef9db76ef39990d9cc0b01fc12094f0bd8a33e4290e9fb1ed043c.exe 2280 427fb8b616cef9db76ef39990d9cc0b01fc12094f0bd8a33e4290e9fb1ed043c.exe -
Suspicious use of WriteProcessMemory 64 IoCs
description pid Process procid_target PID 2368 wrote to memory of 1620 2368 426fb7b515cef8db65ef38980d8cc0b01fc12084f0bd7a33e4290e9fb1ed043c.exe 28 PID 2368 wrote to memory of 1620 2368 426fb7b515cef8db65ef38980d8cc0b01fc12084f0bd7a33e4290e9fb1ed043c.exe 28 PID 2368 wrote to memory of 1620 2368 426fb7b515cef8db65ef38980d8cc0b01fc12084f0bd7a33e4290e9fb1ed043c.exe 28 PID 2368 wrote to memory of 1620 2368 426fb7b515cef8db65ef38980d8cc0b01fc12084f0bd7a33e4290e9fb1ed043c.exe 28 PID 2368 wrote to memory of 2704 2368 426fb7b515cef8db65ef38980d8cc0b01fc12084f0bd7a33e4290e9fb1ed043c.exe 29 PID 2368 wrote to memory of 2704 2368 426fb7b515cef8db65ef38980d8cc0b01fc12084f0bd7a33e4290e9fb1ed043c.exe 29 PID 2368 wrote to memory of 2704 2368 426fb7b515cef8db65ef38980d8cc0b01fc12084f0bd7a33e4290e9fb1ed043c.exe 29 PID 2368 wrote to memory of 2704 2368 426fb7b515cef8db65ef38980d8cc0b01fc12084f0bd7a33e4290e9fb1ed043c.exe 29 PID 2368 wrote to memory of 2736 2368 426fb7b515cef8db65ef38980d8cc0b01fc12084f0bd7a33e4290e9fb1ed043c.exe 31 PID 2368 wrote to memory of 2736 2368 426fb7b515cef8db65ef38980d8cc0b01fc12084f0bd7a33e4290e9fb1ed043c.exe 31 PID 2368 wrote to memory of 2736 2368 426fb7b515cef8db65ef38980d8cc0b01fc12084f0bd7a33e4290e9fb1ed043c.exe 31 PID 2368 wrote to memory of 2736 2368 426fb7b515cef8db65ef38980d8cc0b01fc12084f0bd7a33e4290e9fb1ed043c.exe 31 PID 2704 wrote to memory of 2472 2704 cmd.exe 34 PID 2704 wrote to memory of 2472 2704 cmd.exe 34 PID 2704 wrote to memory of 2472 2704 cmd.exe 34 PID 2704 wrote to memory of 2472 2704 cmd.exe 34 PID 1620 wrote to memory of 1712 1620 cmd.exe 35 PID 1620 wrote to memory of 1712 1620 cmd.exe 35 PID 1620 wrote to memory of 1712 1620 cmd.exe 35 PID 1620 wrote to memory of 1712 1620 cmd.exe 35 PID 2368 wrote to memory of 2584 2368 426fb7b515cef8db65ef38980d8cc0b01fc12084f0bd7a33e4290e9fb1ed043c.exe 36 PID 2368 wrote to memory of 2584 2368 426fb7b515cef8db65ef38980d8cc0b01fc12084f0bd7a33e4290e9fb1ed043c.exe 36 PID 2368 wrote to memory of 2584 2368 426fb7b515cef8db65ef38980d8cc0b01fc12084f0bd7a33e4290e9fb1ed043c.exe 36 PID 2368 wrote to memory of 2584 2368 426fb7b515cef8db65ef38980d8cc0b01fc12084f0bd7a33e4290e9fb1ed043c.exe 36 PID 2736 wrote to memory of 2732 2736 cmd.exe 37 PID 2736 wrote to memory of 2732 2736 cmd.exe 37 PID 2736 wrote to memory of 2732 2736 cmd.exe 37 PID 2736 wrote to memory of 2732 2736 cmd.exe 37 PID 2584 wrote to memory of 2588 2584 427fb8b616cef9db76ef39990d9cc0b01fc12094f0bd8a33e4290e9fb1ed043c.exe 38 PID 2584 wrote to memory of 2588 2584 427fb8b616cef9db76ef39990d9cc0b01fc12094f0bd8a33e4290e9fb1ed043c.exe 38 PID 2584 wrote to memory of 2588 2584 427fb8b616cef9db76ef39990d9cc0b01fc12094f0bd8a33e4290e9fb1ed043c.exe 38 PID 2584 wrote to memory of 2588 2584 427fb8b616cef9db76ef39990d9cc0b01fc12094f0bd8a33e4290e9fb1ed043c.exe 38 PID 2584 wrote to memory of 2588 2584 427fb8b616cef9db76ef39990d9cc0b01fc12094f0bd8a33e4290e9fb1ed043c.exe 38 PID 2584 wrote to memory of 2588 2584 427fb8b616cef9db76ef39990d9cc0b01fc12094f0bd8a33e4290e9fb1ed043c.exe 38 PID 2584 wrote to memory of 2588 2584 427fb8b616cef9db76ef39990d9cc0b01fc12094f0bd8a33e4290e9fb1ed043c.exe 38 PID 2584 wrote to memory of 2588 2584 427fb8b616cef9db76ef39990d9cc0b01fc12094f0bd8a33e4290e9fb1ed043c.exe 38 PID 2584 wrote to memory of 2588 2584 427fb8b616cef9db76ef39990d9cc0b01fc12094f0bd8a33e4290e9fb1ed043c.exe 38 PID 2584 wrote to memory of 2588 2584 427fb8b616cef9db76ef39990d9cc0b01fc12094f0bd8a33e4290e9fb1ed043c.exe 38 PID 2584 wrote to memory of 2588 2584 427fb8b616cef9db76ef39990d9cc0b01fc12094f0bd8a33e4290e9fb1ed043c.exe 38 PID 2584 wrote to memory of 2588 2584 427fb8b616cef9db76ef39990d9cc0b01fc12094f0bd8a33e4290e9fb1ed043c.exe 38 PID 2584 wrote to memory of 2588 2584 427fb8b616cef9db76ef39990d9cc0b01fc12094f0bd8a33e4290e9fb1ed043c.exe 38 PID 2584 wrote to memory of 2588 2584 427fb8b616cef9db76ef39990d9cc0b01fc12094f0bd8a33e4290e9fb1ed043c.exe 38 PID 2584 wrote to memory of 2588 2584 427fb8b616cef9db76ef39990d9cc0b01fc12094f0bd8a33e4290e9fb1ed043c.exe 38 PID 2584 wrote to memory of 2588 2584 427fb8b616cef9db76ef39990d9cc0b01fc12094f0bd8a33e4290e9fb1ed043c.exe 38 PID 2584 wrote to memory of 2588 2584 427fb8b616cef9db76ef39990d9cc0b01fc12094f0bd8a33e4290e9fb1ed043c.exe 38 PID 2584 wrote to memory of 2588 2584 427fb8b616cef9db76ef39990d9cc0b01fc12094f0bd8a33e4290e9fb1ed043c.exe 38 PID 2584 wrote to memory of 2588 2584 427fb8b616cef9db76ef39990d9cc0b01fc12094f0bd8a33e4290e9fb1ed043c.exe 38 PID 2584 wrote to memory of 2588 2584 427fb8b616cef9db76ef39990d9cc0b01fc12094f0bd8a33e4290e9fb1ed043c.exe 38 PID 2584 wrote to memory of 2588 2584 427fb8b616cef9db76ef39990d9cc0b01fc12094f0bd8a33e4290e9fb1ed043c.exe 38 PID 2584 wrote to memory of 2588 2584 427fb8b616cef9db76ef39990d9cc0b01fc12094f0bd8a33e4290e9fb1ed043c.exe 38 PID 2584 wrote to memory of 2588 2584 427fb8b616cef9db76ef39990d9cc0b01fc12094f0bd8a33e4290e9fb1ed043c.exe 38 PID 2584 wrote to memory of 2588 2584 427fb8b616cef9db76ef39990d9cc0b01fc12094f0bd8a33e4290e9fb1ed043c.exe 38 PID 2584 wrote to memory of 2588 2584 427fb8b616cef9db76ef39990d9cc0b01fc12094f0bd8a33e4290e9fb1ed043c.exe 38 PID 2584 wrote to memory of 2588 2584 427fb8b616cef9db76ef39990d9cc0b01fc12094f0bd8a33e4290e9fb1ed043c.exe 38 PID 2584 wrote to memory of 2588 2584 427fb8b616cef9db76ef39990d9cc0b01fc12094f0bd8a33e4290e9fb1ed043c.exe 38 PID 2584 wrote to memory of 2588 2584 427fb8b616cef9db76ef39990d9cc0b01fc12094f0bd8a33e4290e9fb1ed043c.exe 38 PID 2556 wrote to memory of 584 2556 taskeng.exe 42 PID 2556 wrote to memory of 584 2556 taskeng.exe 42 PID 2556 wrote to memory of 584 2556 taskeng.exe 42 PID 2556 wrote to memory of 584 2556 taskeng.exe 42 PID 584 wrote to memory of 2504 584 427fb8b616cef9db76ef39990d9cc0b01fc12094f0bd8a33e4290e9fb1ed043c.exe 43 PID 584 wrote to memory of 2504 584 427fb8b616cef9db76ef39990d9cc0b01fc12094f0bd8a33e4290e9fb1ed043c.exe 43 PID 584 wrote to memory of 2504 584 427fb8b616cef9db76ef39990d9cc0b01fc12094f0bd8a33e4290e9fb1ed043c.exe 43 PID 584 wrote to memory of 2504 584 427fb8b616cef9db76ef39990d9cc0b01fc12094f0bd8a33e4290e9fb1ed043c.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\426fb7b515cef8db65ef38980d8cc0b01fc12084f0bd7a33e4290e9fb1ed043c.exe"C:\Users\Admin\AppData\Local\Temp\426fb7b515cef8db65ef38980d8cc0b01fc12084f0bd7a33e4290e9fb1ed043c.exe"1⤵
- Loads dropped DLL
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2368 -
C:\Windows\SysWOW64\cmd.exe/c sc stop WinDefend2⤵
- Suspicious use of WriteProcessMemory
PID:1620 -
C:\Windows\SysWOW64\sc.exesc stop WinDefend3⤵
- Launches sc.exe
PID:1712
-
-
-
C:\Windows\SysWOW64\cmd.exe/c sc delete WinDefend2⤵
- Suspicious use of WriteProcessMemory
PID:2704 -
C:\Windows\SysWOW64\sc.exesc delete WinDefend3⤵
- Launches sc.exe
PID:2472
-
-
-
C:\Windows\SysWOW64\cmd.exe/c powershell Set-MpPreference -DisableRealtimeMonitoring $true2⤵
- Suspicious use of WriteProcessMemory
PID:2736 -
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:2732
-
-
-
C:\Users\Admin\AppData\Roaming\WinSocket\427fb8b616cef9db76ef39990d9cc0b01fc12094f0bd8a33e4290e9fb1ed043c.exeC:\Users\Admin\AppData\Roaming\WinSocket\427fb8b616cef9db76ef39990d9cc0b01fc12094f0bd8a33e4290e9fb1ed043c.exe2⤵
- Executes dropped EXE
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2584 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:2588
-
-
-
C:\Windows\system32\taskeng.exetaskeng.exe {797538DF-1040-48C0-B946-8B6CD7E676E7} S-1-5-18:NT AUTHORITY\System:Service:1⤵
- Suspicious use of WriteProcessMemory
PID:2556 -
C:\Users\Admin\AppData\Roaming\WinSocket\427fb8b616cef9db76ef39990d9cc0b01fc12094f0bd8a33e4290e9fb1ed043c.exeC:\Users\Admin\AppData\Roaming\WinSocket\427fb8b616cef9db76ef39990d9cc0b01fc12094f0bd8a33e4290e9fb1ed043c.exe2⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:584 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:2504
-
-
-
C:\Users\Admin\AppData\Roaming\WinSocket\427fb8b616cef9db76ef39990d9cc0b01fc12094f0bd8a33e4290e9fb1ed043c.exeC:\Users\Admin\AppData\Roaming\WinSocket\427fb8b616cef9db76ef39990d9cc0b01fc12094f0bd8a33e4290e9fb1ed043c.exe2⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
PID:2280 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:1780
-
-
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
-
C:\Users\Admin\AppData\Roaming\WinSocket\427fb8b616cef9db76ef39990d9cc0b01fc12094f0bd8a33e4290e9fb1ed043c.exe
Filesize1.0MB
MD52cc9e1d0e03ca6a0998f1361282ae394
SHA1e690dfceb4da060def5ff7f28d10c6652a1766e3
SHA256426fb7b515cef8db65ef38980d8cc0b01fc12084f0bd7a33e4290e9fb1ed043c
SHA512511fe4f163ac85f7c6fa4c8009c545313bdaf9519d7aabf12b805a9de0de40f13fbda760ab49f1daf0746d6e41592bbdf0388dca5a8e2437b71e5b7e2bd2715e