Analysis
-
max time kernel
149s -
max time network
153s -
platform
windows10-2004_x64 -
resource
win10v2004-20220812-en -
resource tags
arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system -
submitted
06-11-2022 07:03
Static task
static1
Behavioral task
behavioral1
Sample
e783d0d036639308569b816f91e1c6e8832260b2e1bb975cbab2bb298596976d.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
e783d0d036639308569b816f91e1c6e8832260b2e1bb975cbab2bb298596976d.exe
Resource
win10v2004-20220812-en
General
-
Target
e783d0d036639308569b816f91e1c6e8832260b2e1bb975cbab2bb298596976d.exe
-
Size
192KB
-
MD5
153ad4ec11954fd6a56f61ef646a59c4
-
SHA1
8019d20790ceddd568dfbfafb8225477b6e45be9
-
SHA256
e783d0d036639308569b816f91e1c6e8832260b2e1bb975cbab2bb298596976d
-
SHA512
f404627af82cd4b398211559193649a9d4f1e65e05ce7316aab44a1c8bb95e67510d73298d740adbf855e38422ee2daef754da4505d0cd5dbcbb4adf498dcd6c
-
SSDEEP
384:QLgbZ8uUOaiqMUVBp+xlyT25aB4CLTdkZzCfFLGDQszWJyrJYjKn4xV6/SM2qHdc:OYKmqM0O15rYkcFL5jK4jsASwwSZ
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2668 set thread context of 3392 2668 e783d0d036639308569b816f91e1c6e8832260b2e1bb975cbab2bb298596976d.exe 81 -
Program crash 1 IoCs
pid pid_target Process procid_target 4844 3392 WerFault.exe 81 -
Suspicious use of AdjustPrivilegeToken 1 IoCs
description pid Process Token: SeDebugPrivilege 2668 e783d0d036639308569b816f91e1c6e8832260b2e1bb975cbab2bb298596976d.exe -
Suspicious use of UnmapMainImage 1 IoCs
pid Process 3392 e783d0d036639308569b816f91e1c6e8832260b2e1bb975cbab2bb298596976d.exe -
Suspicious use of WriteProcessMemory 8 IoCs
description pid Process procid_target PID 2668 wrote to memory of 3392 2668 e783d0d036639308569b816f91e1c6e8832260b2e1bb975cbab2bb298596976d.exe 81 PID 2668 wrote to memory of 3392 2668 e783d0d036639308569b816f91e1c6e8832260b2e1bb975cbab2bb298596976d.exe 81 PID 2668 wrote to memory of 3392 2668 e783d0d036639308569b816f91e1c6e8832260b2e1bb975cbab2bb298596976d.exe 81 PID 2668 wrote to memory of 3392 2668 e783d0d036639308569b816f91e1c6e8832260b2e1bb975cbab2bb298596976d.exe 81 PID 2668 wrote to memory of 3392 2668 e783d0d036639308569b816f91e1c6e8832260b2e1bb975cbab2bb298596976d.exe 81 PID 2668 wrote to memory of 3392 2668 e783d0d036639308569b816f91e1c6e8832260b2e1bb975cbab2bb298596976d.exe 81 PID 2668 wrote to memory of 3392 2668 e783d0d036639308569b816f91e1c6e8832260b2e1bb975cbab2bb298596976d.exe 81 PID 2668 wrote to memory of 3392 2668 e783d0d036639308569b816f91e1c6e8832260b2e1bb975cbab2bb298596976d.exe 81
Processes
-
C:\Users\Admin\AppData\Local\Temp\e783d0d036639308569b816f91e1c6e8832260b2e1bb975cbab2bb298596976d.exe"C:\Users\Admin\AppData\Local\Temp\e783d0d036639308569b816f91e1c6e8832260b2e1bb975cbab2bb298596976d.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:2668 -
C:\Users\Admin\AppData\Local\Temp\e783d0d036639308569b816f91e1c6e8832260b2e1bb975cbab2bb298596976d.exeC:\Users\Admin\AppData\Local\Temp\e783d0d036639308569b816f91e1c6e8832260b2e1bb975cbab2bb298596976d.exe2⤵
- Suspicious use of UnmapMainImage
PID:3392 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3392 -s 123⤵
- Program crash
PID:4844
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 420 -p 3392 -ip 33921⤵PID:4968