Analysis
-
max time kernel
150s -
max time network
152s -
platform
windows10-2004_x64 -
resource
win10v2004-20240226-en -
resource tags
arch:x64arch:x86image:win10v2004-20240226-enlocale:en-usos:windows10-2004-x64system -
submitted
05/05/2024, 06:19
Behavioral task
behavioral1
Sample
fd5d1e3f516d1954bd833d489de4024bce6197346a01b7453000654bf42cdb9e.exe
Resource
win7-20231129-en
General
-
Target
fd5d1e3f516d1954bd833d489de4024bce6197346a01b7453000654bf42cdb9e.exe
-
Size
1.3MB
-
MD5
75ed2db3311875af8e577edbcfd75ecd
-
SHA1
2a35e68ae943b5ca1ef38717423c537158184a4d
-
SHA256
fd5d1e3f516d1954bd833d489de4024bce6197346a01b7453000654bf42cdb9e
-
SHA512
0e80cf8f6357815401f50cc1862c1372bf7302822aef3aa0ec7c579d52b5c696870e0bcdae0126fb2f99cb798126cc136abf7e9c60b460cfacc096328f5fdac1
-
SSDEEP
24576:zQ5aILMCfmAUjzX6gfU1pjwjbsXhmvZssrD+nRgnf4NvlOSs:E5aIwC+Agr6g81p1vsrNis
Malware Config
Signatures
-
KPOT Core Executable 1 IoCs
resource yara_rule behavioral2/files/0x000800000002325f-21.dat family_kpot -
Trickbot x86 loader 1 IoCs
Detected Trickbot's x86 loader that unpacks the x86 payload.
resource yara_rule behavioral2/memory/2252-15-0x0000000002C00000-0x0000000002C29000-memory.dmp trickbot_loader32 -
Executes dropped EXE 3 IoCs
pid Process 1848 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 2300 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 2560 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe -
Suspicious use of AdjustPrivilegeToken 2 IoCs
description pid Process Token: SeTcbPrivilege 2300 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe Token: SeTcbPrivilege 2560 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe -
Suspicious use of SetWindowsHookEx 4 IoCs
pid Process 2252 fd5d1e3f516d1954bd833d489de4024bce6197346a01b7453000654bf42cdb9e.exe 1848 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 2300 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 2560 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe -
Suspicious use of WriteProcessMemory 64 IoCs
description pid Process procid_target PID 2252 wrote to memory of 1848 2252 fd5d1e3f516d1954bd833d489de4024bce6197346a01b7453000654bf42cdb9e.exe 93 PID 2252 wrote to memory of 1848 2252 fd5d1e3f516d1954bd833d489de4024bce6197346a01b7453000654bf42cdb9e.exe 93 PID 2252 wrote to memory of 1848 2252 fd5d1e3f516d1954bd833d489de4024bce6197346a01b7453000654bf42cdb9e.exe 93 PID 1848 wrote to memory of 1124 1848 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 94 PID 1848 wrote to memory of 1124 1848 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 94 PID 1848 wrote to memory of 1124 1848 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 94 PID 1848 wrote to memory of 1124 1848 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 94 PID 1848 wrote to memory of 1124 1848 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 94 PID 1848 wrote to memory of 1124 1848 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 94 PID 1848 wrote to memory of 1124 1848 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 94 PID 1848 wrote to memory of 1124 1848 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 94 PID 1848 wrote to memory of 1124 1848 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 94 PID 1848 wrote to memory of 1124 1848 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 94 PID 1848 wrote to memory of 1124 1848 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 94 PID 1848 wrote to memory of 1124 1848 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 94 PID 1848 wrote to memory of 1124 1848 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 94 PID 1848 wrote to memory of 1124 1848 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 94 PID 1848 wrote to memory of 1124 1848 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 94 PID 1848 wrote to memory of 1124 1848 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 94 PID 1848 wrote to memory of 1124 1848 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 94 PID 1848 wrote to memory of 1124 1848 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 94 PID 1848 wrote to memory of 1124 1848 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 94 PID 1848 wrote to memory of 1124 1848 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 94 PID 1848 wrote to memory of 1124 1848 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 94 PID 1848 wrote to memory of 1124 1848 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 94 PID 1848 wrote to memory of 1124 1848 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 94 PID 1848 wrote to memory of 1124 1848 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 94 PID 1848 wrote to memory of 1124 1848 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 94 PID 1848 wrote to memory of 1124 1848 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 94 PID 2300 wrote to memory of 2432 2300 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 105 PID 2300 wrote to memory of 2432 2300 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 105 PID 2300 wrote to memory of 2432 2300 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 105 PID 2300 wrote to memory of 2432 2300 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 105 PID 2300 wrote to memory of 2432 2300 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 105 PID 2300 wrote to memory of 2432 2300 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 105 PID 2300 wrote to memory of 2432 2300 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 105 PID 2300 wrote to memory of 2432 2300 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 105 PID 2300 wrote to memory of 2432 2300 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 105 PID 2300 wrote to memory of 2432 2300 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 105 PID 2300 wrote to memory of 2432 2300 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 105 PID 2300 wrote to memory of 2432 2300 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 105 PID 2300 wrote to memory of 2432 2300 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 105 PID 2300 wrote to memory of 2432 2300 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 105 PID 2300 wrote to memory of 2432 2300 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 105 PID 2300 wrote to memory of 2432 2300 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 105 PID 2300 wrote to memory of 2432 2300 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 105 PID 2300 wrote to memory of 2432 2300 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 105 PID 2300 wrote to memory of 2432 2300 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 105 PID 2300 wrote to memory of 2432 2300 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 105 PID 2300 wrote to memory of 2432 2300 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 105 PID 2300 wrote to memory of 2432 2300 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 105 PID 2300 wrote to memory of 2432 2300 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 105 PID 2300 wrote to memory of 2432 2300 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 105 PID 2300 wrote to memory of 2432 2300 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 105 PID 2300 wrote to memory of 2432 2300 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 105 PID 2560 wrote to memory of 2292 2560 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 107 PID 2560 wrote to memory of 2292 2560 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 107 PID 2560 wrote to memory of 2292 2560 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 107 PID 2560 wrote to memory of 2292 2560 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 107 PID 2560 wrote to memory of 2292 2560 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 107 PID 2560 wrote to memory of 2292 2560 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 107 PID 2560 wrote to memory of 2292 2560 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 107 PID 2560 wrote to memory of 2292 2560 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 107 PID 2560 wrote to memory of 2292 2560 fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe 107 -
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\fd5d1e3f516d1954bd833d489de4024bce6197346a01b7453000654bf42cdb9e.exe"C:\Users\Admin\AppData\Local\Temp\fd5d1e3f516d1954bd833d489de4024bce6197346a01b7453000654bf42cdb9e.exe"1⤵
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2252 -
C:\Users\Admin\AppData\Roaming\WinSocket\fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exeC:\Users\Admin\AppData\Roaming\WinSocket\fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe2⤵
- Executes dropped EXE
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:1848 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:1124
-
-
-
C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" --type=utility --utility-sub-type=asset_store.mojom.AssetStoreService --lang=en-US --service-sandbox-type=asset_store_service --no-appcompat-clear --mojo-platform-channel-handle=4120 --field-trial-handle=2280,i,4114443225282860369,4764091921472631035,262144 --variations-seed-version /prefetch:81⤵PID:3332
-
C:\Users\Admin\AppData\Roaming\WinSocket\fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exeC:\Users\Admin\AppData\Roaming\WinSocket\fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe1⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2300 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe2⤵PID:2432
-
-
C:\Users\Admin\AppData\Roaming\WinSocket\fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exeC:\Users\Admin\AppData\Roaming\WinSocket\fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe1⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2560 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe2⤵PID:2292
-
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
-
C:\Users\Admin\AppData\Roaming\WinSocket\fd6d1e3f617d1964bd933d499de4024bce7198347a01b8463000764bf42cdb9e.exe
Filesize1.3MB
MD575ed2db3311875af8e577edbcfd75ecd
SHA12a35e68ae943b5ca1ef38717423c537158184a4d
SHA256fd5d1e3f516d1954bd833d489de4024bce6197346a01b7453000654bf42cdb9e
SHA5120e80cf8f6357815401f50cc1862c1372bf7302822aef3aa0ec7c579d52b5c696870e0bcdae0126fb2f99cb798126cc136abf7e9c60b460cfacc096328f5fdac1
-
Filesize
73KB
MD58f8d61e4ce34ccde41f811b3c18755a2
SHA1be47b48fe388f3aa6f1ee23f4b983978b3031b25
SHA2565ed836b80ad2c55bae6add48d4329dfa9966057c425820d9db5e50455a5ff4d0
SHA512d2a08849c9b4cde8fedc153fbcecbdffebfb9576ca06ca94a3d929163b83c1dd5a971090e130210f8970c480fe840a822fa9628f0588927b47be4c807572a258