Analysis
-
max time kernel
145s -
max time network
148s -
platform
windows10-2004_x64 -
resource
win10v2004-20220812-en -
resource tags
arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system -
submitted
03/12/2022, 11:09
Static task
static1
Behavioral task
behavioral1
Sample
ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe
Resource
win7-20220812-en
windows7-x64
5 signatures
150 seconds
Behavioral task
behavioral2
Sample
ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe
Resource
win10v2004-20220812-en
windows10-2004-x64
5 signatures
150 seconds
General
-
Target
ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe
-
Size
1.5MB
-
MD5
06660f57b34bc27558b11d9ff37dba5b
-
SHA1
060b8229a1f1f8bf790261a172016ca945f98ac3
-
SHA256
ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138
-
SHA512
012571f1a51e426a70b6ad7d56ea31f97addae9537b2892ad730092d1e5192baee522b0d973c2e1d7e130f6f3d55a63b6c6f26fd55be6e6fa9aa133a3d6ae989
-
SSDEEP
49152:o1m5tQq+n4ZmtcCX16zVcEQqgm5tQq+I56c:o1mjQq+n4+rXIVc/mjQq+IV
Score
5/10
Malware Config
Signatures
-
Suspicious use of SetThreadContext 6 IoCs
description pid Process procid_target PID 4532 set thread context of 5024 4532 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 80 PID 5024 set thread context of 3540 5024 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 81 PID 3540 set thread context of 3304 3540 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 82 PID 3304 set thread context of 4280 3304 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 83 PID 4280 set thread context of 1124 4280 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 84 PID 1124 set thread context of 5012 1124 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 85 -
Program crash 1 IoCs
pid pid_target Process procid_target 1720 5012 WerFault.exe 85 -
Suspicious behavior: EnumeratesProcesses 2 IoCs
pid Process 4532 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 4532 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe -
Suspicious use of SetWindowsHookEx 6 IoCs
pid Process 4532 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 5024 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 3540 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 3304 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 4280 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 1124 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe -
Suspicious use of WriteProcessMemory 64 IoCs
description pid Process procid_target PID 4532 wrote to memory of 5024 4532 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 80 PID 4532 wrote to memory of 5024 4532 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 80 PID 4532 wrote to memory of 5024 4532 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 80 PID 4532 wrote to memory of 5024 4532 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 80 PID 4532 wrote to memory of 5024 4532 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 80 PID 4532 wrote to memory of 5024 4532 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 80 PID 4532 wrote to memory of 5024 4532 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 80 PID 4532 wrote to memory of 5024 4532 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 80 PID 5024 wrote to memory of 3540 5024 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 81 PID 5024 wrote to memory of 3540 5024 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 81 PID 5024 wrote to memory of 3540 5024 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 81 PID 5024 wrote to memory of 3540 5024 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 81 PID 5024 wrote to memory of 3540 5024 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 81 PID 5024 wrote to memory of 3540 5024 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 81 PID 5024 wrote to memory of 3540 5024 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 81 PID 5024 wrote to memory of 3540 5024 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 81 PID 3540 wrote to memory of 3304 3540 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 82 PID 3540 wrote to memory of 3304 3540 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 82 PID 3540 wrote to memory of 3304 3540 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 82 PID 3540 wrote to memory of 3304 3540 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 82 PID 3540 wrote to memory of 3304 3540 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 82 PID 3540 wrote to memory of 3304 3540 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 82 PID 3540 wrote to memory of 3304 3540 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 82 PID 3540 wrote to memory of 3304 3540 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 82 PID 3304 wrote to memory of 4280 3304 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 83 PID 3304 wrote to memory of 4280 3304 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 83 PID 3304 wrote to memory of 4280 3304 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 83 PID 3304 wrote to memory of 4280 3304 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 83 PID 3304 wrote to memory of 4280 3304 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 83 PID 3304 wrote to memory of 4280 3304 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 83 PID 3304 wrote to memory of 4280 3304 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 83 PID 3304 wrote to memory of 4280 3304 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 83 PID 4280 wrote to memory of 1124 4280 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 84 PID 4280 wrote to memory of 1124 4280 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 84 PID 4280 wrote to memory of 1124 4280 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 84 PID 4280 wrote to memory of 1124 4280 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 84 PID 4280 wrote to memory of 1124 4280 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 84 PID 4280 wrote to memory of 1124 4280 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 84 PID 4280 wrote to memory of 1124 4280 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 84 PID 4280 wrote to memory of 1124 4280 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 84 PID 1124 wrote to memory of 5012 1124 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 85 PID 1124 wrote to memory of 5012 1124 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 85 PID 1124 wrote to memory of 5012 1124 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 85 PID 1124 wrote to memory of 5012 1124 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 85 PID 1124 wrote to memory of 5012 1124 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 85 PID 1124 wrote to memory of 5012 1124 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 85 PID 1124 wrote to memory of 5012 1124 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 85 PID 1124 wrote to memory of 5012 1124 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 85 PID 1124 wrote to memory of 5012 1124 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 85 PID 1124 wrote to memory of 5012 1124 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 85 PID 1124 wrote to memory of 5012 1124 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 85 PID 1124 wrote to memory of 5012 1124 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 85 PID 1124 wrote to memory of 5012 1124 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 85 PID 1124 wrote to memory of 5012 1124 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 85 PID 1124 wrote to memory of 5012 1124 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 85 PID 1124 wrote to memory of 5012 1124 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 85 PID 1124 wrote to memory of 5012 1124 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 85 PID 1124 wrote to memory of 5012 1124 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 85 PID 1124 wrote to memory of 5012 1124 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 85 PID 1124 wrote to memory of 5012 1124 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 85 PID 1124 wrote to memory of 5012 1124 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 85 PID 1124 wrote to memory of 5012 1124 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 85 PID 1124 wrote to memory of 5012 1124 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 85 PID 1124 wrote to memory of 5012 1124 ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 85
Processes
-
C:\Users\Admin\AppData\Local\Temp\ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe"C:\Users\Admin\AppData\Local\Temp\ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:4532 -
C:\Users\Admin\AppData\Local\Temp\ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exeC:\Users\Admin\AppData\Local\Temp\ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 000681000068112⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:5024 -
C:\Users\Admin\AppData\Local\Temp\ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exeC:\Users\Admin\AppData\Local\Temp\ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 00068100006811000694800069503⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:3540 -
C:\Users\Admin\AppData\Local\Temp\ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exeC:\Users\Admin\AppData\Local\Temp\ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 0006810000681100069480006950000708600070894⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:3304 -
C:\Users\Admin\AppData\Local\Temp\ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exeC:\Users\Admin\AppData\Local\Temp\ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 000681000068110006948000695000070860007089000722400072285⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:4280 -
C:\Users\Admin\AppData\Local\Temp\ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exeC:\Users\Admin\AppData\Local\Temp\ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe 000681000068110006948000695000070860007089000722400072286⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:1124 -
C:\Users\Admin\AppData\Local\Temp\ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exeC:\Users\Admin\AppData\Local\Temp\ec7bd4051b23a4b808e18ebd343162932eb1d322fe64c01398c4dd6a6deaf138.exe7⤵PID:5012
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 5012 -s 5008⤵
- Program crash
PID:1720
-
-
-
-
-
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 184 -p 5012 -ip 50121⤵PID:560