Analysis
- max time kernel
149s - max time network
150s - 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:42
Behavioral task
behavioral1
Sample
ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773.exe
Resource
win7-20240221-en
14 signatures
150 seconds
General
- Target ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773.exe
- Size 1.6MB
- Sample240521-c7eblsfb88
- SHA256 ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773
- MD5 309db6cee33cc2b6f29d73366f485524
- SHA1 7af3deb5792f1ebefc663672b269655eec723ad6
- SHA512 0f81a3a3418da2a3807026e22d5968465f2db9cc6ac898a6282ec66cd611b68e5d1967fae2c2f6a5e0c63d9a0942fd7925e7384266fa157d608cd0a790d9dcaa
- SSDEEP 24576:zQ5aILMCfmAUjzX6xQE4efQg3zNn+2jsvercPk9N4hVI3/BxL+XKHZjb//8ISgHa:E5aIwC+Agr6SqCPGC6HZkIT/S
- MD5 SHA1 SHA512 SSDEEP
Malware Config
Signatures
- KPOT Core Executable 1 IoCs
resource yara_rule behavioral2/files/0x0007000000023421-21.dat family_kpot - Trickbot x86 loader 1 IoCs
Detected Trickbot's x86 loader that unpacks the x86 payload.
resource yara_rule behavioral2/memory/1892-15-0x0000000002FD0000-0x0000000002FF9000-memory.dmp trickbot_loader32 - Executes dropped EXE 3 IoCs
pid Process 1180 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 4300 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 3436 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe - Suspicious use of AdjustPrivilegeToken 2 IoCs
description pid Process Token: SeTcbPrivilege 4300 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe Token: SeTcbPrivilege 3436 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe - Suspicious use of SetWindowsHookEx 4 IoCs
pid Process 1892 ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773.exe 1180 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 4300 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 3436 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe - Suspicious use of WriteProcessMemory 64 IoCs
description pid Process procid_target PID 1892 wrote to memory of 1180 1892 ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773.exe 83 PID 1892 wrote to memory of 1180 1892 ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773.exe 83 PID 1892 wrote to memory of 1180 1892 ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773.exe 83 PID 1180 wrote to memory of 2464 1180 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 84 PID 1180 wrote to memory of 2464 1180 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 84 PID 1180 wrote to memory of 2464 1180 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 84 PID 1180 wrote to memory of 2464 1180 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 84 PID 1180 wrote to memory of 2464 1180 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 84 PID 1180 wrote to memory of 2464 1180 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 84 PID 1180 wrote to memory of 2464 1180 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 84 PID 1180 wrote to memory of 2464 1180 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 84 PID 1180 wrote to memory of 2464 1180 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 84 PID 1180 wrote to memory of 2464 1180 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 84 PID 1180 wrote to memory of 2464 1180 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 84 PID 1180 wrote to memory of 2464 1180 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 84 PID 1180 wrote to memory of 2464 1180 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 84 PID 1180 wrote to memory of 2464 1180 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 84 PID 1180 wrote to memory of 2464 1180 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 84 PID 1180 wrote to memory of 2464 1180 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 84 PID 1180 wrote to memory of 2464 1180 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 84 PID 1180 wrote to memory of 2464 1180 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 84 PID 1180 wrote to memory of 2464 1180 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 84 PID 1180 wrote to memory of 2464 1180 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 84 PID 1180 wrote to memory of 2464 1180 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 84 PID 1180 wrote to memory of 2464 1180 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 84 PID 1180 wrote to memory of 2464 1180 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 84 PID 1180 wrote to memory of 2464 1180 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 84 PID 1180 wrote to memory of 2464 1180 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 84 PID 1180 wrote to memory of 2464 1180 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 84 PID 4300 wrote to memory of 2904 4300 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 101 PID 4300 wrote to memory of 2904 4300 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 101 PID 4300 wrote to memory of 2904 4300 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 101 PID 4300 wrote to memory of 2904 4300 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 101 PID 4300 wrote to memory of 2904 4300 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 101 PID 4300 wrote to memory of 2904 4300 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 101 PID 4300 wrote to memory of 2904 4300 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 101 PID 4300 wrote to memory of 2904 4300 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 101 PID 4300 wrote to memory of 2904 4300 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 101 PID 4300 wrote to memory of 2904 4300 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 101 PID 4300 wrote to memory of 2904 4300 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 101 PID 4300 wrote to memory of 2904 4300 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 101 PID 4300 wrote to memory of 2904 4300 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 101 PID 4300 wrote to memory of 2904 4300 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 101 PID 4300 wrote to memory of 2904 4300 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 101 PID 4300 wrote to memory of 2904 4300 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 101 PID 4300 wrote to memory of 2904 4300 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 101 PID 4300 wrote to memory of 2904 4300 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 101 PID 4300 wrote to memory of 2904 4300 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 101 PID 4300 wrote to memory of 2904 4300 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 101 PID 4300 wrote to memory of 2904 4300 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 101 PID 4300 wrote to memory of 2904 4300 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 101 PID 4300 wrote to memory of 2904 4300 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 101 PID 4300 wrote to memory of 2904 4300 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 101 PID 4300 wrote to memory of 2904 4300 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 101 PID 4300 wrote to memory of 2904 4300 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 101 PID 3436 wrote to memory of 4144 3436 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 110 PID 3436 wrote to memory of 4144 3436 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 110 PID 3436 wrote to memory of 4144 3436 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 110 PID 3436 wrote to memory of 4144 3436 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 110 PID 3436 wrote to memory of 4144 3436 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 110 PID 3436 wrote to memory of 4144 3436 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 110 PID 3436 wrote to memory of 4144 3436 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 110 PID 3436 wrote to memory of 4144 3436 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 110 PID 3436 wrote to memory of 4144 3436 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 110 - 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:1892 -
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:1180 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:2464
-
-
-
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:4300 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe2⤵PID:2904
-
-
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:3436 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe2⤵PID:4144
-
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
- Path C:\Users\Admin\AppData\Roaming\WinSocket\ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe
- Size 1.6MB
- SHA256 ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773
- MD5 309db6cee33cc2b6f29d73366f485524
- SHA1 7af3deb5792f1ebefc663672b269655eec723ad6
- SHA512 0f81a3a3418da2a3807026e22d5968465f2db9cc6ac898a6282ec66cd611b68e5d1967fae2c2f6a5e0c63d9a0942fd7925e7384266fa157d608cd0a790d9dcaa
- SSDEEP 24576:zQ5aILMCfmAUjzX6xQE4efQg3zNn+2jsvercPk9N4hVI3/BxL+XKHZjb//8ISgHa:E5aIwC+Agr6SqCPGC6HZkIT/S
- MD5 SHA1 SHA512 SSDEEP
- Path C:\Users\Admin\AppData\Roaming\WinSocket\settings.ini
- Size 22KB
- SHA256 b28eab23d533efe5e2e65f0ac6883889614fed0f1560b7cdff1f2a3fd0adc86b
- MD5 1065533dec4c6e313e549be42f7caf05
- SHA1 f2fda04f0b6b237cf7f115669a8a6ac5febd8e18
- SHA512 8b1f49469839cda53bbec7628f40bfbd56bc6c5dac4a70ed4a5db1e727c95b7562d52f672d1e717d301e8c3832d7361bf4444da0657a1a98b622b188731e974c
- SSDEEP 384:r9pZOzQZLT6kAL8ZTqLL9HvuvTFNG2g5DvyTt9EPvuTG89PtZISqTg4yOzOnVSLX:r9pZOzQZLT6kAL8ZTqLL9HvuvTFNG2g7
- MD5 SHA1 SHA512 SSDEEP