Analysis
-
max time kernel
103s -
max time network
148s -
platform
windows10-2004_x64 -
resource
win10v2004-20220901-en -
resource tags
arch:x64arch:x86image:win10v2004-20220901-enlocale:en-usos:windows10-2004-x64system -
submitted
19/09/2022, 07:26
Static task
static1
Behavioral task
behavioral1
Sample
f02497d0edf733c043b49ff140c8b927f7e64f97a102b1151c50810765a96075.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
f02497d0edf733c043b49ff140c8b927f7e64f97a102b1151c50810765a96075.exe
Resource
win10v2004-20220901-en
General
-
Target
f02497d0edf733c043b49ff140c8b927f7e64f97a102b1151c50810765a96075.exe
-
Size
92KB
-
MD5
359d450bdc140a2007bd58f7a1b2dad0
-
SHA1
6279b9d2b5ad82bebae05721aac0a7e09911d35e
-
SHA256
f02497d0edf733c043b49ff140c8b927f7e64f97a102b1151c50810765a96075
-
SHA512
4131a66167c69e6c85c8c789f48a8ee571db8143800f806ec84dfda6e824b11e4092cd91106b127553a9cc97459f96f9ea847fabbbbf146ec45b343ec054515b
-
SSDEEP
1536:bMlBAlkop/d2w8yAPnuy6FwkLQF18I86xlV9r32FV0+MFVPHUYZwake:bMlBA3/8y+uy4wz7NSV0+qVHGake
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 3168 set thread context of 3116 3168 f02497d0edf733c043b49ff140c8b927f7e64f97a102b1151c50810765a96075.exe 84 -
Suspicious behavior: EnumeratesProcesses 4 IoCs
pid Process 3116 f02497d0edf733c043b49ff140c8b927f7e64f97a102b1151c50810765a96075.exe 3116 f02497d0edf733c043b49ff140c8b927f7e64f97a102b1151c50810765a96075.exe 3116 f02497d0edf733c043b49ff140c8b927f7e64f97a102b1151c50810765a96075.exe 3116 f02497d0edf733c043b49ff140c8b927f7e64f97a102b1151c50810765a96075.exe -
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 3168 f02497d0edf733c043b49ff140c8b927f7e64f97a102b1151c50810765a96075.exe -
Suspicious use of WriteProcessMemory 11 IoCs
description pid Process procid_target PID 3168 wrote to memory of 3116 3168 f02497d0edf733c043b49ff140c8b927f7e64f97a102b1151c50810765a96075.exe 84 PID 3168 wrote to memory of 3116 3168 f02497d0edf733c043b49ff140c8b927f7e64f97a102b1151c50810765a96075.exe 84 PID 3168 wrote to memory of 3116 3168 f02497d0edf733c043b49ff140c8b927f7e64f97a102b1151c50810765a96075.exe 84 PID 3168 wrote to memory of 3116 3168 f02497d0edf733c043b49ff140c8b927f7e64f97a102b1151c50810765a96075.exe 84 PID 3168 wrote to memory of 3116 3168 f02497d0edf733c043b49ff140c8b927f7e64f97a102b1151c50810765a96075.exe 84 PID 3168 wrote to memory of 3116 3168 f02497d0edf733c043b49ff140c8b927f7e64f97a102b1151c50810765a96075.exe 84 PID 3168 wrote to memory of 3116 3168 f02497d0edf733c043b49ff140c8b927f7e64f97a102b1151c50810765a96075.exe 84 PID 3116 wrote to memory of 2932 3116 f02497d0edf733c043b49ff140c8b927f7e64f97a102b1151c50810765a96075.exe 36 PID 3116 wrote to memory of 2932 3116 f02497d0edf733c043b49ff140c8b927f7e64f97a102b1151c50810765a96075.exe 36 PID 3116 wrote to memory of 2932 3116 f02497d0edf733c043b49ff140c8b927f7e64f97a102b1151c50810765a96075.exe 36 PID 3116 wrote to memory of 2932 3116 f02497d0edf733c043b49ff140c8b927f7e64f97a102b1151c50810765a96075.exe 36
Processes
-
C:\Windows\Explorer.EXEC:\Windows\Explorer.EXE1⤵PID:2932
-
C:\Users\Admin\AppData\Local\Temp\f02497d0edf733c043b49ff140c8b927f7e64f97a102b1151c50810765a96075.exe"C:\Users\Admin\AppData\Local\Temp\f02497d0edf733c043b49ff140c8b927f7e64f97a102b1151c50810765a96075.exe"2⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:3168 -
C:\Users\Admin\AppData\Local\Temp\f02497d0edf733c043b49ff140c8b927f7e64f97a102b1151c50810765a96075.exe"C:\Users\Admin\AppData\Local\Temp\f02497d0edf733c043b49ff140c8b927f7e64f97a102b1151c50810765a96075.exe"3⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:3116
-
-