Analysis
-
max time kernel
306s -
max time network
328s -
platform
windows10-2004_x64 -
resource
win10v2004-20221111-en -
resource tags
arch:x64arch:x86image:win10v2004-20221111-enlocale:en-usos:windows10-2004-x64system -
submitted
23/11/2022, 17:31
Behavioral task
behavioral1
Sample
a9c8442965d5fda4de06075b0e306753341775fa0aa1450f8f4d71a68e358f3c.exe
Resource
win7-20221111-en
7 signatures
150 seconds
Behavioral task
behavioral2
Sample
a9c8442965d5fda4de06075b0e306753341775fa0aa1450f8f4d71a68e358f3c.exe
Resource
win10v2004-20221111-en
4 signatures
150 seconds
General
-
Target
a9c8442965d5fda4de06075b0e306753341775fa0aa1450f8f4d71a68e358f3c.exe
-
Size
122KB
-
MD5
54571cd1e4ada7d250f6f08c949df231
-
SHA1
c0935974b554c9e86d13913c16f16848e0bea4c7
-
SHA256
a9c8442965d5fda4de06075b0e306753341775fa0aa1450f8f4d71a68e358f3c
-
SHA512
ec0425202583726ebb257ace7e37818cee7d66812566a6c495a4e3844e154ca739ad8cff569a9cc2ee7af62b35696d062571b7cf3145f06ff4288914a89c49fd
-
SSDEEP
3072:dMiDIieBK1rtPsU2Dj6ZNKDoAAHUtJ12lD90d6fZh0szVkq:d4JBuEDkwDoALADi6fZhCq
Score
8/10
Malware Config
Signatures
-
resource yara_rule behavioral2/memory/216-132-0x0000000000400000-0x0000000000448000-memory.dmp upx behavioral2/memory/216-140-0x0000000000400000-0x0000000000448000-memory.dmp upx -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 216 set thread context of 4212 216 a9c8442965d5fda4de06075b0e306753341775fa0aa1450f8f4d71a68e358f3c.exe 83 -
Suspicious use of SetWindowsHookEx 2 IoCs
pid Process 216 a9c8442965d5fda4de06075b0e306753341775fa0aa1450f8f4d71a68e358f3c.exe 4212 a9c8442965d5fda4de06075b0e306753341775fa0aa1450f8f4d71a68e358f3c.exe -
Suspicious use of WriteProcessMemory 8 IoCs
description pid Process procid_target PID 216 wrote to memory of 4212 216 a9c8442965d5fda4de06075b0e306753341775fa0aa1450f8f4d71a68e358f3c.exe 83 PID 216 wrote to memory of 4212 216 a9c8442965d5fda4de06075b0e306753341775fa0aa1450f8f4d71a68e358f3c.exe 83 PID 216 wrote to memory of 4212 216 a9c8442965d5fda4de06075b0e306753341775fa0aa1450f8f4d71a68e358f3c.exe 83 PID 216 wrote to memory of 4212 216 a9c8442965d5fda4de06075b0e306753341775fa0aa1450f8f4d71a68e358f3c.exe 83 PID 216 wrote to memory of 4212 216 a9c8442965d5fda4de06075b0e306753341775fa0aa1450f8f4d71a68e358f3c.exe 83 PID 216 wrote to memory of 4212 216 a9c8442965d5fda4de06075b0e306753341775fa0aa1450f8f4d71a68e358f3c.exe 83 PID 216 wrote to memory of 4212 216 a9c8442965d5fda4de06075b0e306753341775fa0aa1450f8f4d71a68e358f3c.exe 83 PID 216 wrote to memory of 4212 216 a9c8442965d5fda4de06075b0e306753341775fa0aa1450f8f4d71a68e358f3c.exe 83
Processes
-
C:\Users\Admin\AppData\Local\Temp\a9c8442965d5fda4de06075b0e306753341775fa0aa1450f8f4d71a68e358f3c.exe"C:\Users\Admin\AppData\Local\Temp\a9c8442965d5fda4de06075b0e306753341775fa0aa1450f8f4d71a68e358f3c.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:216 -
C:\Users\Admin\AppData\Local\Temp\a9c8442965d5fda4de06075b0e306753341775fa0aa1450f8f4d71a68e358f3c.exe"C:\Users\Admin\AppData\Local\Temp\a9c8442965d5fda4de06075b0e306753341775fa0aa1450f8f4d71a68e358f3c.exe"2⤵
- Suspicious use of SetWindowsHookEx
PID:4212
-