Analysis
-
max time kernel
120s -
max time network
121s -
platform
windows7_x64 -
resource
win7-20240220-en -
resource tags
arch:x64arch:x86image:win7-20240220-enlocale:en-usos:windows7-x64system -
submitted
04/06/2024, 01:59
Static task
static1
Behavioral task
behavioral1
Sample
d3f18f0a0b2c7b7f8e365b00f804f76f0b747824086c5a9530471efd1ebf5174.exe
Resource
win7-20240220-en
Behavioral task
behavioral2
Sample
d3f18f0a0b2c7b7f8e365b00f804f76f0b747824086c5a9530471efd1ebf5174.exe
Resource
win10v2004-20240508-en
General
-
Target
d3f18f0a0b2c7b7f8e365b00f804f76f0b747824086c5a9530471efd1ebf5174.exe
-
Size
959KB
-
MD5
f5b20b005cbb604eec709f984166ca68
-
SHA1
6dc9f3042ae2074c22e0aaf2e3e3219ff90e5e94
-
SHA256
d3f18f0a0b2c7b7f8e365b00f804f76f0b747824086c5a9530471efd1ebf5174
-
SHA512
3602275f7ac78d2535f46ad2be0654ff8f1d653e29a66a1d59c46c629a53172edb1788384df5baebfd30208a3e71f05e153463ba753bc4f8306a4177d8f371f1
-
SSDEEP
12288:DhX0D9CQStfAheg7w2PUXWkdzyeNaoURCReJKv0+OOt8PYuTBa7ds/VtbTUsvExU:h0DUY7TsfdHaoUR818CyPYA/bIzO9
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 1028 set thread context of 2600 1028 d3f18f0a0b2c7b7f8e365b00f804f76f0b747824086c5a9530471efd1ebf5174.exe 28 -
Program crash 1 IoCs
pid pid_target Process procid_target 2472 2600 WerFault.exe 28 -
Suspicious behavior: EnumeratesProcesses 3 IoCs
pid Process 1028 d3f18f0a0b2c7b7f8e365b00f804f76f0b747824086c5a9530471efd1ebf5174.exe 1028 d3f18f0a0b2c7b7f8e365b00f804f76f0b747824086c5a9530471efd1ebf5174.exe 2600 d3f18f0a0b2c7b7f8e365b00f804f76f0b747824086c5a9530471efd1ebf5174.exe -
Suspicious use of AdjustPrivilegeToken 1 IoCs
description pid Process Token: SeDebugPrivilege 1028 d3f18f0a0b2c7b7f8e365b00f804f76f0b747824086c5a9530471efd1ebf5174.exe -
Suspicious use of WriteProcessMemory 11 IoCs
description pid Process procid_target PID 1028 wrote to memory of 2600 1028 d3f18f0a0b2c7b7f8e365b00f804f76f0b747824086c5a9530471efd1ebf5174.exe 28 PID 1028 wrote to memory of 2600 1028 d3f18f0a0b2c7b7f8e365b00f804f76f0b747824086c5a9530471efd1ebf5174.exe 28 PID 1028 wrote to memory of 2600 1028 d3f18f0a0b2c7b7f8e365b00f804f76f0b747824086c5a9530471efd1ebf5174.exe 28 PID 1028 wrote to memory of 2600 1028 d3f18f0a0b2c7b7f8e365b00f804f76f0b747824086c5a9530471efd1ebf5174.exe 28 PID 1028 wrote to memory of 2600 1028 d3f18f0a0b2c7b7f8e365b00f804f76f0b747824086c5a9530471efd1ebf5174.exe 28 PID 1028 wrote to memory of 2600 1028 d3f18f0a0b2c7b7f8e365b00f804f76f0b747824086c5a9530471efd1ebf5174.exe 28 PID 1028 wrote to memory of 2600 1028 d3f18f0a0b2c7b7f8e365b00f804f76f0b747824086c5a9530471efd1ebf5174.exe 28 PID 2600 wrote to memory of 2472 2600 d3f18f0a0b2c7b7f8e365b00f804f76f0b747824086c5a9530471efd1ebf5174.exe 31 PID 2600 wrote to memory of 2472 2600 d3f18f0a0b2c7b7f8e365b00f804f76f0b747824086c5a9530471efd1ebf5174.exe 31 PID 2600 wrote to memory of 2472 2600 d3f18f0a0b2c7b7f8e365b00f804f76f0b747824086c5a9530471efd1ebf5174.exe 31 PID 2600 wrote to memory of 2472 2600 d3f18f0a0b2c7b7f8e365b00f804f76f0b747824086c5a9530471efd1ebf5174.exe 31
Processes
-
C:\Users\Admin\AppData\Local\Temp\d3f18f0a0b2c7b7f8e365b00f804f76f0b747824086c5a9530471efd1ebf5174.exe"C:\Users\Admin\AppData\Local\Temp\d3f18f0a0b2c7b7f8e365b00f804f76f0b747824086c5a9530471efd1ebf5174.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:1028 -
C:\Users\Admin\AppData\Local\Temp\d3f18f0a0b2c7b7f8e365b00f804f76f0b747824086c5a9530471efd1ebf5174.exe"C:\Users\Admin\AppData\Local\Temp\d3f18f0a0b2c7b7f8e365b00f804f76f0b747824086c5a9530471efd1ebf5174.exe"2⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:2600 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2600 -s 363⤵
- Program crash
PID:2472
-
-