Analysis
- max time kernel
149s - max time network
153s - platform
windows10-2004_x64 - resource
win10v2004-20240426-en - resource tags
arch:x64arch:x86image:win10v2004-20240426-enlocale:en-usos:windows10-2004-x64system - submitted
19/05/2024, 23:24
Behavioral task
behavioral1
Sample
76d43a949850783754f7c37b334a14ab9cf1b5d36bc8cb9da62ef411621f919a.exe
Resource
win7-20240508-en
14 signatures
150 seconds
General
- Target 76d43a949850783754f7c37b334a14ab9cf1b5d36bc8cb9da62ef411621f919a.exe
- Size 1.2MB
- Sample240519-3d5jtagg8x
- SHA256 76d43a949850783754f7c37b334a14ab9cf1b5d36bc8cb9da62ef411621f919a
- MD5 354d303c7b9191c883969c97bf60dc06
- SHA1 467285c178564283665ad7b72337af9cb6cdcb46
- SHA512 174abb4008bace3bfbfae6bbc99da383d00004b0f079c1ed4549369c642428bad6388be2ec088cf08c763a0ea4dd39bd1f5399f2bfa8ba4f3198e5f9c45d1986
- SSDEEP 24576:zQ5aILMCfmAUjzX6xQt+4En+bcMAOxA5zYlU+jcTWSRe98r16g:E5aIwC+Agr6StVEnmcKxYj+ITWSMg1B
- MD5 SHA1 SHA512 SSDEEP
Malware Config
Signatures
- KPOT Core Executable 1 IoCs
resource yara_rule behavioral2/files/0x0007000000023405-21.dat family_kpot - Trickbot x86 loader 1 IoCs
Detected Trickbot's x86 loader that unpacks the x86 payload.
resource yara_rule behavioral2/memory/3692-15-0x0000000003010000-0x0000000003039000-memory.dmp trickbot_loader32 - Executes dropped EXE 3 IoCs
pid Process 4176 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 3348 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 3744 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe - Suspicious use of AdjustPrivilegeToken 2 IoCs
description pid Process Token: SeTcbPrivilege 3348 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe Token: SeTcbPrivilege 3744 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe - Suspicious use of SetWindowsHookEx 4 IoCs
pid Process 3692 76d43a949850783754f7c37b334a14ab9cf1b5d36bc8cb9da62ef411621f919a.exe 4176 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 3348 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 3744 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe - Suspicious use of WriteProcessMemory 64 IoCs
description pid Process procid_target PID 3692 wrote to memory of 4176 3692 76d43a949850783754f7c37b334a14ab9cf1b5d36bc8cb9da62ef411621f919a.exe 83 PID 3692 wrote to memory of 4176 3692 76d43a949850783754f7c37b334a14ab9cf1b5d36bc8cb9da62ef411621f919a.exe 83 PID 3692 wrote to memory of 4176 3692 76d43a949850783754f7c37b334a14ab9cf1b5d36bc8cb9da62ef411621f919a.exe 83 PID 4176 wrote to memory of 2448 4176 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 84 PID 4176 wrote to memory of 2448 4176 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 84 PID 4176 wrote to memory of 2448 4176 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 84 PID 4176 wrote to memory of 2448 4176 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 84 PID 4176 wrote to memory of 2448 4176 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 84 PID 4176 wrote to memory of 2448 4176 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 84 PID 4176 wrote to memory of 2448 4176 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 84 PID 4176 wrote to memory of 2448 4176 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 84 PID 4176 wrote to memory of 2448 4176 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 84 PID 4176 wrote to memory of 2448 4176 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 84 PID 4176 wrote to memory of 2448 4176 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 84 PID 4176 wrote to memory of 2448 4176 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 84 PID 4176 wrote to memory of 2448 4176 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 84 PID 4176 wrote to memory of 2448 4176 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 84 PID 4176 wrote to memory of 2448 4176 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 84 PID 4176 wrote to memory of 2448 4176 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 84 PID 4176 wrote to memory of 2448 4176 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 84 PID 4176 wrote to memory of 2448 4176 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 84 PID 4176 wrote to memory of 2448 4176 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 84 PID 4176 wrote to memory of 2448 4176 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 84 PID 4176 wrote to memory of 2448 4176 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 84 PID 4176 wrote to memory of 2448 4176 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 84 PID 4176 wrote to memory of 2448 4176 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 84 PID 4176 wrote to memory of 2448 4176 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 84 PID 4176 wrote to memory of 2448 4176 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 84 PID 4176 wrote to memory of 2448 4176 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 84 PID 3348 wrote to memory of 1048 3348 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 99 PID 3348 wrote to memory of 1048 3348 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 99 PID 3348 wrote to memory of 1048 3348 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 99 PID 3348 wrote to memory of 1048 3348 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 99 PID 3348 wrote to memory of 1048 3348 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 99 PID 3348 wrote to memory of 1048 3348 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 99 PID 3348 wrote to memory of 1048 3348 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 99 PID 3348 wrote to memory of 1048 3348 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 99 PID 3348 wrote to memory of 1048 3348 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 99 PID 3348 wrote to memory of 1048 3348 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 99 PID 3348 wrote to memory of 1048 3348 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 99 PID 3348 wrote to memory of 1048 3348 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 99 PID 3348 wrote to memory of 1048 3348 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 99 PID 3348 wrote to memory of 1048 3348 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 99 PID 3348 wrote to memory of 1048 3348 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 99 PID 3348 wrote to memory of 1048 3348 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 99 PID 3348 wrote to memory of 1048 3348 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 99 PID 3348 wrote to memory of 1048 3348 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 99 PID 3348 wrote to memory of 1048 3348 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 99 PID 3348 wrote to memory of 1048 3348 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 99 PID 3348 wrote to memory of 1048 3348 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 99 PID 3348 wrote to memory of 1048 3348 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 99 PID 3348 wrote to memory of 1048 3348 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 99 PID 3348 wrote to memory of 1048 3348 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 99 PID 3348 wrote to memory of 1048 3348 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 99 PID 3348 wrote to memory of 1048 3348 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 99 PID 3744 wrote to memory of 4572 3744 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 108 PID 3744 wrote to memory of 4572 3744 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 108 PID 3744 wrote to memory of 4572 3744 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 108 PID 3744 wrote to memory of 4572 3744 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 108 PID 3744 wrote to memory of 4572 3744 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 108 PID 3744 wrote to memory of 4572 3744 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 108 PID 3744 wrote to memory of 4572 3744 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 108 PID 3744 wrote to memory of 4572 3744 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 108 PID 3744 wrote to memory of 4572 3744 87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe 108 - 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\76d43a949850783754f7c37b334a14ab9cf1b5d36bc8cb9da62ef411621f919a.exe"C:\Users\Admin\AppData\Local\Temp\76d43a949850783754f7c37b334a14ab9cf1b5d36bc8cb9da62ef411621f919a.exe"1⤵
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:3692 -
C:\Users\Admin\AppData\Roaming\WinSocket\87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exeC:\Users\Admin\AppData\Roaming\WinSocket\87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe2⤵
- Executes dropped EXE
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:4176 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:2448
-
-
-
C:\Users\Admin\AppData\Roaming\WinSocket\87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exeC:\Users\Admin\AppData\Roaming\WinSocket\87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe1⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:3348 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe2⤵PID:1048
-
-
C:\Users\Admin\AppData\Roaming\WinSocket\87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exeC:\Users\Admin\AppData\Roaming\WinSocket\87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe1⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:3744 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe2⤵PID:4572
-
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
- Path C:\Users\Admin\AppData\Roaming\WinSocket\87d43a949960893864f8c38b334a14ab9cf1b6d37bc9cb9da72ef411721f919a.exe
- Size 1.2MB
- SHA256 76d43a949850783754f7c37b334a14ab9cf1b5d36bc8cb9da62ef411621f919a
- MD5 354d303c7b9191c883969c97bf60dc06
- SHA1 467285c178564283665ad7b72337af9cb6cdcb46
- SHA512 174abb4008bace3bfbfae6bbc99da383d00004b0f079c1ed4549369c642428bad6388be2ec088cf08c763a0ea4dd39bd1f5399f2bfa8ba4f3198e5f9c45d1986
- SSDEEP 24576:zQ5aILMCfmAUjzX6xQt+4En+bcMAOxA5zYlU+jcTWSRe98r16g:E5aIwC+Agr6StVEnmcKxYj+ITWSMg1B
- MD5 SHA1 SHA512 SSDEEP
- Path C:\Users\Admin\AppData\Roaming\WinSocket\settings.ini
- Size 25KB
- SHA256 c540f9c9f913065d5d537f42ea6b254137287111967485f680b29e9a6b07b021
- MD5 ad4172b9e073d4cd5fec146f9939b750
- SHA1 46e889ceff53e99199cb584b4076ab6e758622fa
- SHA512 1aad948b74d225be5f89065c6c67b2247fd69d5c6e4f67d5231262de3c4a8d19eb9e6f3f304a35a7a14cab4232c2ade580bfef12f76774c0d0d4ed8e9f9af7fd
- SSDEEP 768:2iJBGfMbGtz2B3wkWXAm3XtIdYYQ257Fe8y5ApzED35Iqa5gjuAjrj7lWNxQUlQ4:P2oWrs
- MD5 SHA1 SHA512 SSDEEP