Analysis
-
max time kernel
119s -
max time network
176s -
platform
windows10-2004_x64 -
resource
win10v2004-20220812-en -
resource tags
arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system -
submitted
07/11/2022, 17:57
Static task
static1
Behavioral task
behavioral1
Sample
59b2926d6552cd929ba4fec5aaad782ad43b87d46e0874d086e71bf82598841b.exe
Resource
win7-20220901-en
Behavioral task
behavioral2
Sample
59b2926d6552cd929ba4fec5aaad782ad43b87d46e0874d086e71bf82598841b.exe
Resource
win10v2004-20220812-en
General
-
Target
59b2926d6552cd929ba4fec5aaad782ad43b87d46e0874d086e71bf82598841b.exe
-
Size
100KB
-
MD5
02789cc78fbf4af362c7b36ab13f7e37
-
SHA1
4c80363fb2ed43734c0b5bd36b5e58f664a55d63
-
SHA256
59b2926d6552cd929ba4fec5aaad782ad43b87d46e0874d086e71bf82598841b
-
SHA512
554428f94d1cde9cf045d4ae3487ce09bee04178256f9e9f7f4119db66fa87dc5a213f1ad7c97491de5b5425d0a00aacf29e1a37d6de4766fa92ac5874e8ecd9
-
SSDEEP
768:ACfIXbo8pDrkdFuNhkj85KcmONBmP8Xbay9nksgQ7U+DBSCkKhFzsrISR/Do:2Xbo8XkXAN8PcaIO80kg8UU
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 400 set thread context of 3992 400 59b2926d6552cd929ba4fec5aaad782ad43b87d46e0874d086e71bf82598841b.exe 80 -
Program crash 2 IoCs
pid pid_target Process procid_target 864 3992 WerFault.exe 80 1580 3992 WerFault.exe 80 -
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 400 59b2926d6552cd929ba4fec5aaad782ad43b87d46e0874d086e71bf82598841b.exe -
Suspicious use of WriteProcessMemory 9 IoCs
description pid Process procid_target PID 400 wrote to memory of 3992 400 59b2926d6552cd929ba4fec5aaad782ad43b87d46e0874d086e71bf82598841b.exe 80 PID 400 wrote to memory of 3992 400 59b2926d6552cd929ba4fec5aaad782ad43b87d46e0874d086e71bf82598841b.exe 80 PID 400 wrote to memory of 3992 400 59b2926d6552cd929ba4fec5aaad782ad43b87d46e0874d086e71bf82598841b.exe 80 PID 400 wrote to memory of 3992 400 59b2926d6552cd929ba4fec5aaad782ad43b87d46e0874d086e71bf82598841b.exe 80 PID 400 wrote to memory of 3992 400 59b2926d6552cd929ba4fec5aaad782ad43b87d46e0874d086e71bf82598841b.exe 80 PID 400 wrote to memory of 3992 400 59b2926d6552cd929ba4fec5aaad782ad43b87d46e0874d086e71bf82598841b.exe 80 PID 3992 wrote to memory of 864 3992 59b2926d6552cd929ba4fec5aaad782ad43b87d46e0874d086e71bf82598841b.exe 83 PID 3992 wrote to memory of 864 3992 59b2926d6552cd929ba4fec5aaad782ad43b87d46e0874d086e71bf82598841b.exe 83 PID 3992 wrote to memory of 864 3992 59b2926d6552cd929ba4fec5aaad782ad43b87d46e0874d086e71bf82598841b.exe 83
Processes
-
C:\Users\Admin\AppData\Local\Temp\59b2926d6552cd929ba4fec5aaad782ad43b87d46e0874d086e71bf82598841b.exe"C:\Users\Admin\AppData\Local\Temp\59b2926d6552cd929ba4fec5aaad782ad43b87d46e0874d086e71bf82598841b.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:400 -
C:\Users\Admin\AppData\Local\Temp\59b2926d6552cd929ba4fec5aaad782ad43b87d46e0874d086e71bf82598841b.exe"C:\Users\Admin\AppData\Local\Temp\59b2926d6552cd929ba4fec5aaad782ad43b87d46e0874d086e71bf82598841b.exe"2⤵
- Suspicious use of WriteProcessMemory
PID:3992 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3992 -s 1883⤵
- Program crash
PID:864
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3992 -s 1883⤵
- Program crash
PID:1580
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 408 -p 3992 -ip 39921⤵PID:1816