Analysis
- max time kernel
148s - max time network
150s - platform
windows10-2004_x64 - resource
win10v2004-20240426-en - resource tags
arch:x64arch:x86image:win10v2004-20240426-enlocale:en-usos:windows10-2004-x64system - submitted
20/05/2024, 04:03
Behavioral task
behavioral1
Sample
e7407eebb60b679ec47f7cf86c8d072575f0921383b7e8fed2756e392f8f9646.exe
Resource
win7-20240508-en
14 signatures
150 seconds
General
- Target e7407eebb60b679ec47f7cf86c8d072575f0921383b7e8fed2756e392f8f9646.exe
- Size 1.0MB
- Sample240520-emdwfsbd8y
- SHA256 e7407eebb60b679ec47f7cf86c8d072575f0921383b7e8fed2756e392f8f9646
- MD5 d3601a6db7d9e3af2b5531d0ca496a02
- SHA1 be0862858aa3783fde3daeb8fd4c03161cfc08a3
- SHA512 dd2567bc229fb3753f7aefb72bae49630226423a7d212adca594a548c30feb167f1dc41b2242eafe9758e960fbb26f68d2ecf9f344f37bb0fb8633d53a14ca49
- SSDEEP 12288:zJB0lh5aILwtFPCfmAUtFC6NXbv+GEs1HzCHT4TlM9YmJ2Q97v54yKkvrarn1kyq:zQ5aILMCfmAUjzX6T0TlOnvPlOO1fVf
- MD5 SHA1 SHA512 SSDEEP
Malware Config
Signatures
- KPOT Core Executable 1 IoCs
resource yara_rule behavioral2/files/0x000700000002348e-21.dat family_kpot - Trickbot x86 loader 1 IoCs
Detected Trickbot's x86 loader that unpacks the x86 payload.
resource yara_rule behavioral2/memory/5012-15-0x00000000022E0000-0x0000000002309000-memory.dmp trickbot_loader32 - Executes dropped EXE 3 IoCs
pid Process 4140 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 1980 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 1376 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe - Suspicious use of AdjustPrivilegeToken 2 IoCs
description pid Process Token: SeTcbPrivilege 1980 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe Token: SeTcbPrivilege 1376 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe - Suspicious use of SetWindowsHookEx 4 IoCs
pid Process 5012 e7407eebb60b679ec47f7cf86c8d072575f0921383b7e8fed2756e392f8f9646.exe 4140 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 1980 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 1376 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe - Suspicious use of WriteProcessMemory 64 IoCs
description pid Process procid_target PID 5012 wrote to memory of 4140 5012 e7407eebb60b679ec47f7cf86c8d072575f0921383b7e8fed2756e392f8f9646.exe 83 PID 5012 wrote to memory of 4140 5012 e7407eebb60b679ec47f7cf86c8d072575f0921383b7e8fed2756e392f8f9646.exe 83 PID 5012 wrote to memory of 4140 5012 e7407eebb60b679ec47f7cf86c8d072575f0921383b7e8fed2756e392f8f9646.exe 83 PID 4140 wrote to memory of 1036 4140 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 84 PID 4140 wrote to memory of 1036 4140 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 84 PID 4140 wrote to memory of 1036 4140 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 84 PID 4140 wrote to memory of 1036 4140 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 84 PID 4140 wrote to memory of 1036 4140 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 84 PID 4140 wrote to memory of 1036 4140 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 84 PID 4140 wrote to memory of 1036 4140 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 84 PID 4140 wrote to memory of 1036 4140 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 84 PID 4140 wrote to memory of 1036 4140 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 84 PID 4140 wrote to memory of 1036 4140 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 84 PID 4140 wrote to memory of 1036 4140 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 84 PID 4140 wrote to memory of 1036 4140 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 84 PID 4140 wrote to memory of 1036 4140 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 84 PID 4140 wrote to memory of 1036 4140 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 84 PID 4140 wrote to memory of 1036 4140 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 84 PID 4140 wrote to memory of 1036 4140 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 84 PID 4140 wrote to memory of 1036 4140 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 84 PID 4140 wrote to memory of 1036 4140 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 84 PID 4140 wrote to memory of 1036 4140 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 84 PID 4140 wrote to memory of 1036 4140 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 84 PID 4140 wrote to memory of 1036 4140 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 84 PID 4140 wrote to memory of 1036 4140 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 84 PID 4140 wrote to memory of 1036 4140 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 84 PID 4140 wrote to memory of 1036 4140 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 84 PID 4140 wrote to memory of 1036 4140 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 84 PID 4140 wrote to memory of 1036 4140 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 84 PID 1980 wrote to memory of 2656 1980 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 101 PID 1980 wrote to memory of 2656 1980 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 101 PID 1980 wrote to memory of 2656 1980 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 101 PID 1980 wrote to memory of 2656 1980 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 101 PID 1980 wrote to memory of 2656 1980 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 101 PID 1980 wrote to memory of 2656 1980 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 101 PID 1980 wrote to memory of 2656 1980 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 101 PID 1980 wrote to memory of 2656 1980 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 101 PID 1980 wrote to memory of 2656 1980 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 101 PID 1980 wrote to memory of 2656 1980 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 101 PID 1980 wrote to memory of 2656 1980 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 101 PID 1980 wrote to memory of 2656 1980 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 101 PID 1980 wrote to memory of 2656 1980 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 101 PID 1980 wrote to memory of 2656 1980 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 101 PID 1980 wrote to memory of 2656 1980 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 101 PID 1980 wrote to memory of 2656 1980 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 101 PID 1980 wrote to memory of 2656 1980 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 101 PID 1980 wrote to memory of 2656 1980 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 101 PID 1980 wrote to memory of 2656 1980 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 101 PID 1980 wrote to memory of 2656 1980 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 101 PID 1980 wrote to memory of 2656 1980 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 101 PID 1980 wrote to memory of 2656 1980 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 101 PID 1980 wrote to memory of 2656 1980 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 101 PID 1980 wrote to memory of 2656 1980 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 101 PID 1980 wrote to memory of 2656 1980 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 101 PID 1980 wrote to memory of 2656 1980 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 101 PID 1376 wrote to memory of 5016 1376 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 110 PID 1376 wrote to memory of 5016 1376 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 110 PID 1376 wrote to memory of 5016 1376 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 110 PID 1376 wrote to memory of 5016 1376 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 110 PID 1376 wrote to memory of 5016 1376 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 110 PID 1376 wrote to memory of 5016 1376 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 110 PID 1376 wrote to memory of 5016 1376 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 110 PID 1376 wrote to memory of 5016 1376 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe 110 PID 1376 wrote to memory of 5016 1376 e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.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\e7407eebb60b679ec47f7cf86c8d072575f0921383b7e8fed2756e392f8f9646.exe"C:\Users\Admin\AppData\Local\Temp\e7407eebb60b679ec47f7cf86c8d072575f0921383b7e8fed2756e392f8f9646.exe"1⤵
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:5012 -
C:\Users\Admin\AppData\Roaming\WinSocket\e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exeC:\Users\Admin\AppData\Roaming\WinSocket\e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe2⤵
- Executes dropped EXE
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:4140 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:1036
-
-
-
C:\Users\Admin\AppData\Roaming\WinSocket\e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exeC:\Users\Admin\AppData\Roaming\WinSocket\e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe1⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:1980 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe2⤵PID:2656
-
-
C:\Users\Admin\AppData\Roaming\WinSocket\e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exeC:\Users\Admin\AppData\Roaming\WinSocket\e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe1⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:1376 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe2⤵PID:5016
-
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
- Path C:\Users\Admin\AppData\Roaming\WinSocket\e8408eebb70b789ec48f8cf97c9d082686f0921393b8e9fed2867e392f9f9747.exe
- Size 1.0MB
- SHA256 e7407eebb60b679ec47f7cf86c8d072575f0921383b7e8fed2756e392f8f9646
- MD5 d3601a6db7d9e3af2b5531d0ca496a02
- SHA1 be0862858aa3783fde3daeb8fd4c03161cfc08a3
- SHA512 dd2567bc229fb3753f7aefb72bae49630226423a7d212adca594a548c30feb167f1dc41b2242eafe9758e960fbb26f68d2ecf9f344f37bb0fb8633d53a14ca49
- SSDEEP 12288:zJB0lh5aILwtFPCfmAUtFC6NXbv+GEs1HzCHT4TlM9YmJ2Q97v54yKkvrarn1kyq:zQ5aILMCfmAUjzX6T0TlOnvPlOO1fVf
- MD5 SHA1 SHA512 SSDEEP
- Path C:\Users\Admin\AppData\Roaming\WinSocket\settings.ini
- Size 61KB
- SHA256 a0c228faea6acf4d5929570a06904a50fd87cb028fe0b14f9c9d8e4da35ddca9
- MD5 7955fa674564c6f75e66e2429c0673e8
- SHA1 0df1c37be398e624441a837bbf44a9b206209ea4
- SHA512 1a439cfceef33098cf37d36c2e4dff71ed15b99d73aaef50358227add430b2b0e9d07228f98cb7d2f03780c9791a01c9f5b752d401b621cc7475fe344d8670b0
- SSDEEP 1536:CnaiCz19XzWncTLDg5MsNAeSKFdU1ryIJ37tCW07OZZ6TNwRBAXsldwslicFQ55O:t8nDi6+bN3
- MD5 SHA1 SHA512 SSDEEP