Analysis
-
max time kernel
139s -
max time network
133s -
platform
windows10-2004_x64 -
resource
win10v2004-20240508-en -
resource tags
arch:x64arch:x86image:win10v2004-20240508-enlocale:en-usos:windows10-2004-x64system -
submitted
21-05-2024 02:45
Behavioral task
behavioral1
Sample
ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773.exe
Resource
win7-20240508-en
General
-
Target
ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773.exe
-
Size
1.6MB
-
MD5
309db6cee33cc2b6f29d73366f485524
-
SHA1
7af3deb5792f1ebefc663672b269655eec723ad6
-
SHA256
ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773
-
SHA512
0f81a3a3418da2a3807026e22d5968465f2db9cc6ac898a6282ec66cd611b68e5d1967fae2c2f6a5e0c63d9a0942fd7925e7384266fa157d608cd0a790d9dcaa
-
SSDEEP
24576:zQ5aILMCfmAUjzX6xQE4efQg3zNn+2jsvercPk9N4hVI3/BxL+XKHZjb//8ISgHa:E5aIwC+Agr6SqCPGC6HZkIT/S
Malware Config
Signatures
-
KPOT Core Executable 1 IoCs
Processes:
resource yara_rule C:\Users\Admin\AppData\Roaming\WinSocket\ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe family_kpot -
Trickbot x86 loader 1 IoCs
Detected Trickbot's x86 loader that unpacks the x86 payload.
Processes:
resource yara_rule behavioral2/memory/3168-15-0x0000000003110000-0x0000000003139000-memory.dmp trickbot_loader32 -
Executes dropped EXE 3 IoCs
Processes:
ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exead99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exead99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exepid process 624 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 5092 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 2704 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe -
Suspicious use of AdjustPrivilegeToken 2 IoCs
Processes:
ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exead99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exedescription pid process Token: SeTcbPrivilege 5092 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe Token: SeTcbPrivilege 2704 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe -
Suspicious use of SetWindowsHookEx 4 IoCs
Processes:
ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773.exead99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exead99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exead99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exepid process 3168 ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773.exe 624 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 5092 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 2704 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe -
Suspicious use of WriteProcessMemory 64 IoCs
Processes:
ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773.exead99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exead99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exead99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exedescription pid process target process PID 3168 wrote to memory of 624 3168 ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773.exe ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe PID 3168 wrote to memory of 624 3168 ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773.exe ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe PID 3168 wrote to memory of 624 3168 ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773.exe ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe PID 624 wrote to memory of 1444 624 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 624 wrote to memory of 1444 624 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 624 wrote to memory of 1444 624 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 624 wrote to memory of 1444 624 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 624 wrote to memory of 1444 624 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 624 wrote to memory of 1444 624 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 624 wrote to memory of 1444 624 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 624 wrote to memory of 1444 624 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 624 wrote to memory of 1444 624 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 624 wrote to memory of 1444 624 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 624 wrote to memory of 1444 624 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 624 wrote to memory of 1444 624 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 624 wrote to memory of 1444 624 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 624 wrote to memory of 1444 624 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 624 wrote to memory of 1444 624 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 624 wrote to memory of 1444 624 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 624 wrote to memory of 1444 624 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 624 wrote to memory of 1444 624 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 624 wrote to memory of 1444 624 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 624 wrote to memory of 1444 624 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 624 wrote to memory of 1444 624 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 624 wrote to memory of 1444 624 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 624 wrote to memory of 1444 624 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 624 wrote to memory of 1444 624 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 624 wrote to memory of 1444 624 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 624 wrote to memory of 1444 624 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 5092 wrote to memory of 1756 5092 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 5092 wrote to memory of 1756 5092 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 5092 wrote to memory of 1756 5092 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 5092 wrote to memory of 1756 5092 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 5092 wrote to memory of 1756 5092 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 5092 wrote to memory of 1756 5092 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 5092 wrote to memory of 1756 5092 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 5092 wrote to memory of 1756 5092 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 5092 wrote to memory of 1756 5092 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 5092 wrote to memory of 1756 5092 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 5092 wrote to memory of 1756 5092 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 5092 wrote to memory of 1756 5092 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 5092 wrote to memory of 1756 5092 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 5092 wrote to memory of 1756 5092 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 5092 wrote to memory of 1756 5092 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 5092 wrote to memory of 1756 5092 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 5092 wrote to memory of 1756 5092 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 5092 wrote to memory of 1756 5092 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 5092 wrote to memory of 1756 5092 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 5092 wrote to memory of 1756 5092 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 5092 wrote to memory of 1756 5092 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 5092 wrote to memory of 1756 5092 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 5092 wrote to memory of 1756 5092 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 5092 wrote to memory of 1756 5092 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 5092 wrote to memory of 1756 5092 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 5092 wrote to memory of 1756 5092 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 2704 wrote to memory of 2368 2704 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 2704 wrote to memory of 2368 2704 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 2704 wrote to memory of 2368 2704 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 2704 wrote to memory of 2368 2704 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 2704 wrote to memory of 2368 2704 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 2704 wrote to memory of 2368 2704 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 2704 wrote to memory of 2368 2704 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 2704 wrote to memory of 2368 2704 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 2704 wrote to memory of 2368 2704 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.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\ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773.exe"C:\Users\Admin\AppData\Local\Temp\ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773.exe"1⤵
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:3168 -
C:\Users\Admin\AppData\Roaming\WinSocket\ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exeC:\Users\Admin\AppData\Roaming\WinSocket\ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe2⤵
- Executes dropped EXE
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:624 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:1444
-
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 --field-trial-handle=4236,i,1067197275908310731,12785105794523264014,262144 --variations-seed-version --mojo-platform-channel-handle=3852 /prefetch:81⤵PID:4656
-
C:\Users\Admin\AppData\Roaming\WinSocket\ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exeC:\Users\Admin\AppData\Roaming\WinSocket\ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe1⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:5092 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe2⤵PID:1756
-
C:\Users\Admin\AppData\Roaming\WinSocket\ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exeC:\Users\Admin\AppData\Roaming\WinSocket\ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe1⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2704 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe2⤵PID:2368
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
-
C:\Users\Admin\AppData\Roaming\WinSocket\ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe
Filesize1.6MB
MD5309db6cee33cc2b6f29d73366f485524
SHA17af3deb5792f1ebefc663672b269655eec723ad6
SHA256ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773
SHA5120f81a3a3418da2a3807026e22d5968465f2db9cc6ac898a6282ec66cd611b68e5d1967fae2c2f6a5e0c63d9a0942fd7925e7384266fa157d608cd0a790d9dcaa
-
Filesize
52KB
MD55b195b7bada345e77dc649830763048c
SHA1249c23f9d5e231f9f5bb20f2b77508ff61866c3b
SHA256bc9e0b3cf8a8b7a63fcb921f674c53792028efc9e30e1d27464eddfbface1c52
SHA5123f0e52a45c103a2b8cb2ba14522f3117148f1dca36417781a3772b81db3d63977067c15e2ff0eff6f8393e87506ccbd8872ceafc183cce480286764adf8fc672