Analysis
-
max time kernel
135s -
max time network
122s -
platform
windows7_x64 -
resource
win7-20240221-en -
resource tags
arch:x64arch:x86image:win7-20240221-enlocale:en-usos:windows7-x64system -
submitted
20-05-2024 04:00
Behavioral task
behavioral1
Sample
e694529f958905b8295f709f12595a177f6905ae5519c007232aa715d02b6190.exe
Resource
win7-20240221-en
General
-
Target
e694529f958905b8295f709f12595a177f6905ae5519c007232aa715d02b6190.exe
-
Size
1.0MB
-
MD5
a04be63a0f8001136cbc6de67152c221
-
SHA1
93eef82de026008c7b2339e00a00e6ecabbb9569
-
SHA256
e694529f958905b8295f709f12595a177f6905ae5519c007232aa715d02b6190
-
SHA512
003cca043614e6bea198fb938e2d0319c98c5a6847ea68a564f955eaa8eac5c0dad85d6c0b346e798a0f3421213654bb706292effe5902e46a6a964d8d0469f3
-
SSDEEP
24576:zQ5aILMCfmAUjzX6xQ0+wCIygDsAUkhmZ9skLez:E5aIwC+Agr6SNbFs
Malware Config
Signatures
-
KPOT Core Executable 1 IoCs
resource yara_rule behavioral1/files/0x0007000000014aa2-20.dat family_kpot -
Trickbot x86 loader 1 IoCs
Detected Trickbot's x86 loader that unpacks the x86 payload.
resource yara_rule behavioral1/memory/2212-15-0x0000000001BB0000-0x0000000001BD9000-memory.dmp trickbot_loader32 -
Executes dropped EXE 3 IoCs
pid Process 2568 e794629f969906b9296f809f12696a188f7906ae6619c008232aa816d02b7190.exe 884 e794629f969906b9296f809f12696a188f7906ae6619c008232aa816d02b7190.exe 2200 e794629f969906b9296f809f12696a188f7906ae6619c008232aa816d02b7190.exe -
Loads dropped DLL 2 IoCs
pid Process 2212 e694529f958905b8295f709f12595a177f6905ae5519c007232aa715d02b6190.exe 2212 e694529f958905b8295f709f12595a177f6905ae5519c007232aa715d02b6190.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 2448 sc.exe 2484 sc.exe -
Suspicious behavior: EnumeratesProcesses 4 IoCs
pid Process 2212 e694529f958905b8295f709f12595a177f6905ae5519c007232aa715d02b6190.exe 2212 e694529f958905b8295f709f12595a177f6905ae5519c007232aa715d02b6190.exe 2212 e694529f958905b8295f709f12595a177f6905ae5519c007232aa715d02b6190.exe 3032 powershell.exe -
Suspicious use of AdjustPrivilegeToken 3 IoCs
description pid Process Token: SeDebugPrivilege 3032 powershell.exe Token: SeTcbPrivilege 884 e794629f969906b9296f809f12696a188f7906ae6619c008232aa816d02b7190.exe Token: SeTcbPrivilege 2200 e794629f969906b9296f809f12696a188f7906ae6619c008232aa816d02b7190.exe -
Suspicious use of SetWindowsHookEx 4 IoCs
pid Process 2212 e694529f958905b8295f709f12595a177f6905ae5519c007232aa715d02b6190.exe 2568 e794629f969906b9296f809f12696a188f7906ae6619c008232aa816d02b7190.exe 884 e794629f969906b9296f809f12696a188f7906ae6619c008232aa816d02b7190.exe 2200 e794629f969906b9296f809f12696a188f7906ae6619c008232aa816d02b7190.exe -
Suspicious use of WriteProcessMemory 64 IoCs
description pid Process procid_target PID 2212 wrote to memory of 3020 2212 e694529f958905b8295f709f12595a177f6905ae5519c007232aa715d02b6190.exe 28 PID 2212 wrote to memory of 3020 2212 e694529f958905b8295f709f12595a177f6905ae5519c007232aa715d02b6190.exe 28 PID 2212 wrote to memory of 3020 2212 e694529f958905b8295f709f12595a177f6905ae5519c007232aa715d02b6190.exe 28 PID 2212 wrote to memory of 3020 2212 e694529f958905b8295f709f12595a177f6905ae5519c007232aa715d02b6190.exe 28 PID 2212 wrote to memory of 2580 2212 e694529f958905b8295f709f12595a177f6905ae5519c007232aa715d02b6190.exe 29 PID 2212 wrote to memory of 2580 2212 e694529f958905b8295f709f12595a177f6905ae5519c007232aa715d02b6190.exe 29 PID 2212 wrote to memory of 2580 2212 e694529f958905b8295f709f12595a177f6905ae5519c007232aa715d02b6190.exe 29 PID 2212 wrote to memory of 2580 2212 e694529f958905b8295f709f12595a177f6905ae5519c007232aa715d02b6190.exe 29 PID 2212 wrote to memory of 2652 2212 e694529f958905b8295f709f12595a177f6905ae5519c007232aa715d02b6190.exe 31 PID 2212 wrote to memory of 2652 2212 e694529f958905b8295f709f12595a177f6905ae5519c007232aa715d02b6190.exe 31 PID 2212 wrote to memory of 2652 2212 e694529f958905b8295f709f12595a177f6905ae5519c007232aa715d02b6190.exe 31 PID 2212 wrote to memory of 2652 2212 e694529f958905b8295f709f12595a177f6905ae5519c007232aa715d02b6190.exe 31 PID 2212 wrote to memory of 2568 2212 e694529f958905b8295f709f12595a177f6905ae5519c007232aa715d02b6190.exe 34 PID 2212 wrote to memory of 2568 2212 e694529f958905b8295f709f12595a177f6905ae5519c007232aa715d02b6190.exe 34 PID 2212 wrote to memory of 2568 2212 e694529f958905b8295f709f12595a177f6905ae5519c007232aa715d02b6190.exe 34 PID 2212 wrote to memory of 2568 2212 e694529f958905b8295f709f12595a177f6905ae5519c007232aa715d02b6190.exe 34 PID 3020 wrote to memory of 2448 3020 cmd.exe 35 PID 3020 wrote to memory of 2448 3020 cmd.exe 35 PID 3020 wrote to memory of 2448 3020 cmd.exe 35 PID 3020 wrote to memory of 2448 3020 cmd.exe 35 PID 2652 wrote to memory of 3032 2652 cmd.exe 36 PID 2652 wrote to memory of 3032 2652 cmd.exe 36 PID 2652 wrote to memory of 3032 2652 cmd.exe 36 PID 2652 wrote to memory of 3032 2652 cmd.exe 36 PID 2580 wrote to memory of 2484 2580 cmd.exe 37 PID 2580 wrote to memory of 2484 2580 cmd.exe 37 PID 2580 wrote to memory of 2484 2580 cmd.exe 37 PID 2580 wrote to memory of 2484 2580 cmd.exe 37 PID 2568 wrote to memory of 2452 2568 e794629f969906b9296f809f12696a188f7906ae6619c008232aa816d02b7190.exe 38 PID 2568 wrote to memory of 2452 2568 e794629f969906b9296f809f12696a188f7906ae6619c008232aa816d02b7190.exe 38 PID 2568 wrote to memory of 2452 2568 e794629f969906b9296f809f12696a188f7906ae6619c008232aa816d02b7190.exe 38 PID 2568 wrote to memory of 2452 2568 e794629f969906b9296f809f12696a188f7906ae6619c008232aa816d02b7190.exe 38 PID 2568 wrote to memory of 2452 2568 e794629f969906b9296f809f12696a188f7906ae6619c008232aa816d02b7190.exe 38 PID 2568 wrote to memory of 2452 2568 e794629f969906b9296f809f12696a188f7906ae6619c008232aa816d02b7190.exe 38 PID 2568 wrote to memory of 2452 2568 e794629f969906b9296f809f12696a188f7906ae6619c008232aa816d02b7190.exe 38 PID 2568 wrote to memory of 2452 2568 e794629f969906b9296f809f12696a188f7906ae6619c008232aa816d02b7190.exe 38 PID 2568 wrote to memory of 2452 2568 e794629f969906b9296f809f12696a188f7906ae6619c008232aa816d02b7190.exe 38 PID 2568 wrote to memory of 2452 2568 e794629f969906b9296f809f12696a188f7906ae6619c008232aa816d02b7190.exe 38 PID 2568 wrote to memory of 2452 2568 e794629f969906b9296f809f12696a188f7906ae6619c008232aa816d02b7190.exe 38 PID 2568 wrote to memory of 2452 2568 e794629f969906b9296f809f12696a188f7906ae6619c008232aa816d02b7190.exe 38 PID 2568 wrote to memory of 2452 2568 e794629f969906b9296f809f12696a188f7906ae6619c008232aa816d02b7190.exe 38 PID 2568 wrote to memory of 2452 2568 e794629f969906b9296f809f12696a188f7906ae6619c008232aa816d02b7190.exe 38 PID 2568 wrote to memory of 2452 2568 e794629f969906b9296f809f12696a188f7906ae6619c008232aa816d02b7190.exe 38 PID 2568 wrote to memory of 2452 2568 e794629f969906b9296f809f12696a188f7906ae6619c008232aa816d02b7190.exe 38 PID 2568 wrote to memory of 2452 2568 e794629f969906b9296f809f12696a188f7906ae6619c008232aa816d02b7190.exe 38 PID 2568 wrote to memory of 2452 2568 e794629f969906b9296f809f12696a188f7906ae6619c008232aa816d02b7190.exe 38 PID 2568 wrote to memory of 2452 2568 e794629f969906b9296f809f12696a188f7906ae6619c008232aa816d02b7190.exe 38 PID 2568 wrote to memory of 2452 2568 e794629f969906b9296f809f12696a188f7906ae6619c008232aa816d02b7190.exe 38 PID 2568 wrote to memory of 2452 2568 e794629f969906b9296f809f12696a188f7906ae6619c008232aa816d02b7190.exe 38 PID 2568 wrote to memory of 2452 2568 e794629f969906b9296f809f12696a188f7906ae6619c008232aa816d02b7190.exe 38 PID 2568 wrote to memory of 2452 2568 e794629f969906b9296f809f12696a188f7906ae6619c008232aa816d02b7190.exe 38 PID 2568 wrote to memory of 2452 2568 e794629f969906b9296f809f12696a188f7906ae6619c008232aa816d02b7190.exe 38 PID 2568 wrote to memory of 2452 2568 e794629f969906b9296f809f12696a188f7906ae6619c008232aa816d02b7190.exe 38 PID 2568 wrote to memory of 2452 2568 e794629f969906b9296f809f12696a188f7906ae6619c008232aa816d02b7190.exe 38 PID 2568 wrote to memory of 2452 2568 e794629f969906b9296f809f12696a188f7906ae6619c008232aa816d02b7190.exe 38 PID 2568 wrote to memory of 2452 2568 e794629f969906b9296f809f12696a188f7906ae6619c008232aa816d02b7190.exe 38 PID 296 wrote to memory of 884 296 taskeng.exe 42 PID 296 wrote to memory of 884 296 taskeng.exe 42 PID 296 wrote to memory of 884 296 taskeng.exe 42 PID 296 wrote to memory of 884 296 taskeng.exe 42 PID 884 wrote to memory of 2424 884 e794629f969906b9296f809f12696a188f7906ae6619c008232aa816d02b7190.exe 43 PID 884 wrote to memory of 2424 884 e794629f969906b9296f809f12696a188f7906ae6619c008232aa816d02b7190.exe 43 PID 884 wrote to memory of 2424 884 e794629f969906b9296f809f12696a188f7906ae6619c008232aa816d02b7190.exe 43 PID 884 wrote to memory of 2424 884 e794629f969906b9296f809f12696a188f7906ae6619c008232aa816d02b7190.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\e694529f958905b8295f709f12595a177f6905ae5519c007232aa715d02b6190.exe"C:\Users\Admin\AppData\Local\Temp\e694529f958905b8295f709f12595a177f6905ae5519c007232aa715d02b6190.exe"1⤵
- Loads dropped DLL
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2212 -
C:\Windows\SysWOW64\cmd.exe/c sc stop WinDefend2⤵
- Suspicious use of WriteProcessMemory
PID:3020 -
C:\Windows\SysWOW64\sc.exesc stop WinDefend3⤵
- Launches sc.exe
PID:2448
-
-
-
C:\Windows\SysWOW64\cmd.exe/c sc delete WinDefend2⤵
- Suspicious use of WriteProcessMemory
PID:2580 -
C:\Windows\SysWOW64\sc.exesc delete WinDefend3⤵
- Launches sc.exe
PID:2484
-
-
-
C:\Windows\SysWOW64\cmd.exe/c powershell Set-MpPreference -DisableRealtimeMonitoring $true2⤵
- Suspicious use of WriteProcessMemory
PID:2652 -
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:3032
-
-
-
C:\Users\Admin\AppData\Roaming\WinSocket\e794629f969906b9296f809f12696a188f7906ae6619c008232aa816d02b7190.exeC:\Users\Admin\AppData\Roaming\WinSocket\e794629f969906b9296f809f12696a188f7906ae6619c008232aa816d02b7190.exe2⤵
- Executes dropped EXE
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2568 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:2452
-
-
-
C:\Windows\system32\taskeng.exetaskeng.exe {CB07F937-C490-4188-9806-383F7B666C71} S-1-5-18:NT AUTHORITY\System:Service:1⤵
- Suspicious use of WriteProcessMemory
PID:296 -
C:\Users\Admin\AppData\Roaming\WinSocket\e794629f969906b9296f809f12696a188f7906ae6619c008232aa816d02b7190.exeC:\Users\Admin\AppData\Roaming\WinSocket\e794629f969906b9296f809f12696a188f7906ae6619c008232aa816d02b7190.exe2⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:884 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:2424
-
-
-
C:\Users\Admin\AppData\Roaming\WinSocket\e794629f969906b9296f809f12696a188f7906ae6619c008232aa816d02b7190.exeC:\Users\Admin\AppData\Roaming\WinSocket\e794629f969906b9296f809f12696a188f7906ae6619c008232aa816d02b7190.exe2⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
PID:2200 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:1792
-
-
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
-
\Users\Admin\AppData\Roaming\WinSocket\e794629f969906b9296f809f12696a188f7906ae6619c008232aa816d02b7190.exe
Filesize1.0MB
MD5a04be63a0f8001136cbc6de67152c221
SHA193eef82de026008c7b2339e00a00e6ecabbb9569
SHA256e694529f958905b8295f709f12595a177f6905ae5519c007232aa715d02b6190
SHA512003cca043614e6bea198fb938e2d0319c98c5a6847ea68a564f955eaa8eac5c0dad85d6c0b346e798a0f3421213654bb706292effe5902e46a6a964d8d0469f3