Windows 7 deprecation
Windows 7 will be removed from tria.ge on 2025-03-31
Analysis
-
max time kernel
141s -
max time network
149s -
platform
windows10-2004_x64 -
resource
win10v2004-20240226-en -
resource tags
arch:x64arch:x86image:win10v2004-20240226-enlocale:en-usos:windows10-2004-x64system -
submitted
09/04/2024, 18:57
Behavioral task
behavioral1
Sample
24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe
Resource
win7-20240221-en
Behavioral task
behavioral2
Sample
24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe
Resource
win10v2004-20240226-en
General
-
Target
24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe
-
Size
477KB
-
MD5
d56f6219a261d4738c459aea2c5a86e9
-
SHA1
7c0bbd32d14fcc7dc99a9fd004c761d1a12290f5
-
SHA256
24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226
-
SHA512
cda623f402d468cbbf1ecc30df563d4f3c56697cb71f5093de6a37d392adecc32f2771c538c097ea108c1bbbc5f6caf191387e9ef9664a5cc2005f4611f71efd
-
SSDEEP
12288:mCYtNDwqkXJAe4Q5oWqZPVyGDEQPJlhPVMq9QbPF7Nw:v8Dpte4Q9gtyGIkvhtMbU
Malware Config
Extracted
cobaltstrike
http://:0
Signatures
-
Cobaltstrike
Detected malicious payload which is part of Cobaltstrike.
-
UPX dump on OEP (original entry point) 2 IoCs
resource yara_rule behavioral2/memory/2680-0-0x00007FF7B01C0000-0x00007FF7B0284000-memory.dmp UPX behavioral2/memory/2680-16453-0x00007FF7B01C0000-0x00007FF7B0284000-memory.dmp UPX -
resource yara_rule behavioral2/memory/2680-0-0x00007FF7B01C0000-0x00007FF7B0284000-memory.dmp upx behavioral2/memory/2680-16453-0x00007FF7B01C0000-0x00007FF7B0284000-memory.dmp upx -
Suspicious use of WriteProcessMemory 64 IoCs
description pid Process procid_target PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84 PID 2680 wrote to memory of 208 2680 24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe 84
Processes
-
C:\Users\Admin\AppData\Local\Temp\24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe"C:\Users\Admin\AppData\Local\Temp\24bc3419ed40e5dcc4b96bc41e6bf43763ec5442d465b681e19a32686d025226.exe"1⤵
- Suspicious use of WriteProcessMemory
PID:2680 -
C:\Windows\System32\wusa.exeC:\Windows\System32\wusa.exe2⤵PID:208
-