Analysis
-
max time kernel
207s -
max time network
244s -
platform
windows10-2004_x64 -
resource
win10v2004-20221111-en -
resource tags
arch:x64arch:x86image:win10v2004-20221111-enlocale:en-usos:windows10-2004-x64system -
submitted
24-11-2022 12:10
Behavioral task
behavioral1
Sample
c88b8c05e627c0ffd19c1b2d5fec92e119a9b3558e00b99962babb68f48e43f9.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
c88b8c05e627c0ffd19c1b2d5fec92e119a9b3558e00b99962babb68f48e43f9.exe
Resource
win10v2004-20221111-en
General
-
Target
c88b8c05e627c0ffd19c1b2d5fec92e119a9b3558e00b99962babb68f48e43f9.exe
-
Size
394KB
-
MD5
ce9bc973a53472c1d8d18c244a3b254b
-
SHA1
c056bd544a3d6620b6ccb190f524aa7c81d5056f
-
SHA256
c88b8c05e627c0ffd19c1b2d5fec92e119a9b3558e00b99962babb68f48e43f9
-
SHA512
80318d5fd976cd28008abdbbbcb5d8a1493cd8edc0cbd0f79a3eff1053fa7a1cf270a74357fa37c02630c7ab176caf0408583dc14664611c3847b404b6da0315
-
SSDEEP
12288:aUVlArRr2hamUEzHSTLWGFL3gpvePSFjy:aUVk92UEDOtFL3gsPSFjy
Malware Config
Signatures
-
Processes:
resource yara_rule behavioral2/memory/1096-132-0x0000000000400000-0x0000000000488000-memory.dmp upx behavioral2/memory/384-138-0x0000000000400000-0x000000000044F000-memory.dmp upx behavioral2/memory/1096-139-0x0000000000400000-0x0000000000488000-memory.dmp upx -
Suspicious use of SetThreadContext 1 IoCs
Processes:
c88b8c05e627c0ffd19c1b2d5fec92e119a9b3558e00b99962babb68f48e43f9.exedescription pid process target process PID 1096 set thread context of 384 1096 c88b8c05e627c0ffd19c1b2d5fec92e119a9b3558e00b99962babb68f48e43f9.exe svchost.exe -
Program crash 1 IoCs
Processes:
WerFault.exepid pid_target process target process 4208 384 WerFault.exe svchost.exe -
Suspicious behavior: EnumeratesProcesses 2 IoCs
Processes:
c88b8c05e627c0ffd19c1b2d5fec92e119a9b3558e00b99962babb68f48e43f9.exepid process 1096 c88b8c05e627c0ffd19c1b2d5fec92e119a9b3558e00b99962babb68f48e43f9.exe 1096 c88b8c05e627c0ffd19c1b2d5fec92e119a9b3558e00b99962babb68f48e43f9.exe -
Suspicious use of SetWindowsHookEx 2 IoCs
Processes:
c88b8c05e627c0ffd19c1b2d5fec92e119a9b3558e00b99962babb68f48e43f9.exepid process 1096 c88b8c05e627c0ffd19c1b2d5fec92e119a9b3558e00b99962babb68f48e43f9.exe 1096 c88b8c05e627c0ffd19c1b2d5fec92e119a9b3558e00b99962babb68f48e43f9.exe -
Suspicious use of WriteProcessMemory 5 IoCs
Processes:
c88b8c05e627c0ffd19c1b2d5fec92e119a9b3558e00b99962babb68f48e43f9.exedescription pid process target process PID 1096 wrote to memory of 384 1096 c88b8c05e627c0ffd19c1b2d5fec92e119a9b3558e00b99962babb68f48e43f9.exe svchost.exe PID 1096 wrote to memory of 384 1096 c88b8c05e627c0ffd19c1b2d5fec92e119a9b3558e00b99962babb68f48e43f9.exe svchost.exe PID 1096 wrote to memory of 384 1096 c88b8c05e627c0ffd19c1b2d5fec92e119a9b3558e00b99962babb68f48e43f9.exe svchost.exe PID 1096 wrote to memory of 384 1096 c88b8c05e627c0ffd19c1b2d5fec92e119a9b3558e00b99962babb68f48e43f9.exe svchost.exe PID 1096 wrote to memory of 384 1096 c88b8c05e627c0ffd19c1b2d5fec92e119a9b3558e00b99962babb68f48e43f9.exe svchost.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\c88b8c05e627c0ffd19c1b2d5fec92e119a9b3558e00b99962babb68f48e43f9.exe"C:\Users\Admin\AppData\Local\Temp\c88b8c05e627c0ffd19c1b2d5fec92e119a9b3558e00b99962babb68f48e43f9.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:1096 -
C:\Windows\SysWOW64\svchost.exesvchost.exe2⤵PID:384
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 384 -s 123⤵
- Program crash
PID:4208
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 404 -p 384 -ip 3841⤵PID:4084