Analysis
-
max time kernel
150s -
max time network
155s -
platform
windows10-2004_x64 -
resource
win10v2004-20220812-en -
resource tags
arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system -
submitted
29/11/2022, 04:20
Static task
static1
Behavioral task
behavioral1
Sample
a16b4a834cce5f6078682dd5d51fd80505705368616bb6fedc69e5e7f20055e9.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
a16b4a834cce5f6078682dd5d51fd80505705368616bb6fedc69e5e7f20055e9.exe
Resource
win10v2004-20220812-en
General
-
Target
a16b4a834cce5f6078682dd5d51fd80505705368616bb6fedc69e5e7f20055e9.exe
-
Size
146KB
-
MD5
4c780698442ecc24f55df7a587a38d68
-
SHA1
9596b5886cbffb484d963d20c1de2a04a21490d3
-
SHA256
a16b4a834cce5f6078682dd5d51fd80505705368616bb6fedc69e5e7f20055e9
-
SHA512
7aabcf0a7a328d1fe1b5941b5bcffa5a314ce4e0de5801522eb16c384e5ffa8a1ae92e6fc8df9f8068b59f7595f32d643b39b96433deab5b7acf07971795776b
-
SSDEEP
3072:rNsJHOLmAfVIYckg86upr8TW/qEqa4f9zr2prDw8taw:yHOvfVoN1uwWita4f9zqnwhw
Malware Config
Signatures
-
resource yara_rule behavioral2/memory/1764-133-0x0000000000400000-0x000000000044C000-memory.dmp upx behavioral2/memory/1764-135-0x0000000000400000-0x000000000044C000-memory.dmp upx behavioral2/memory/1764-136-0x0000000000400000-0x000000000042A000-memory.dmp upx -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 4260 set thread context of 1764 4260 a16b4a834cce5f6078682dd5d51fd80505705368616bb6fedc69e5e7f20055e9.exe 80 -
Program crash 1 IoCs
pid pid_target Process procid_target 4928 1764 WerFault.exe 80 -
Suspicious use of UnmapMainImage 1 IoCs
pid Process 4260 a16b4a834cce5f6078682dd5d51fd80505705368616bb6fedc69e5e7f20055e9.exe -
Suspicious use of WriteProcessMemory 7 IoCs
description pid Process procid_target PID 4260 wrote to memory of 1764 4260 a16b4a834cce5f6078682dd5d51fd80505705368616bb6fedc69e5e7f20055e9.exe 80 PID 4260 wrote to memory of 1764 4260 a16b4a834cce5f6078682dd5d51fd80505705368616bb6fedc69e5e7f20055e9.exe 80 PID 4260 wrote to memory of 1764 4260 a16b4a834cce5f6078682dd5d51fd80505705368616bb6fedc69e5e7f20055e9.exe 80 PID 4260 wrote to memory of 1764 4260 a16b4a834cce5f6078682dd5d51fd80505705368616bb6fedc69e5e7f20055e9.exe 80 PID 4260 wrote to memory of 1764 4260 a16b4a834cce5f6078682dd5d51fd80505705368616bb6fedc69e5e7f20055e9.exe 80 PID 4260 wrote to memory of 1764 4260 a16b4a834cce5f6078682dd5d51fd80505705368616bb6fedc69e5e7f20055e9.exe 80 PID 4260 wrote to memory of 1764 4260 a16b4a834cce5f6078682dd5d51fd80505705368616bb6fedc69e5e7f20055e9.exe 80
Processes
-
C:\Users\Admin\AppData\Local\Temp\a16b4a834cce5f6078682dd5d51fd80505705368616bb6fedc69e5e7f20055e9.exe"C:\Users\Admin\AppData\Local\Temp\a16b4a834cce5f6078682dd5d51fd80505705368616bb6fedc69e5e7f20055e9.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of UnmapMainImage
- Suspicious use of WriteProcessMemory
PID:4260 -
C:\Users\Admin\AppData\Local\Temp\a16b4a834cce5f6078682dd5d51fd80505705368616bb6fedc69e5e7f20055e9.exe"C:\Users\Admin\AppData\Local\Temp\a16b4a834cce5f6078682dd5d51fd80505705368616bb6fedc69e5e7f20055e9.exe"2⤵PID:1764
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 1764 -s 3323⤵
- Program crash
PID:4928
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 440 -p 1764 -ip 17641⤵PID:4948