Analysis
-
max time kernel
143s -
max time network
150s -
platform
windows10-2004_x64 -
resource
win10v2004-20220812-en -
resource tags
arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system -
submitted
29/10/2022, 23:55
Static task
static1
Behavioral task
behavioral1
Sample
e05366fa2ff255fd52ebea19a4c21ae1e9b8df320e8373e79e4584fde1803cdc.exe
Resource
win7-20220901-en
Behavioral task
behavioral2
Sample
e05366fa2ff255fd52ebea19a4c21ae1e9b8df320e8373e79e4584fde1803cdc.exe
Resource
win10v2004-20220812-en
General
-
Target
e05366fa2ff255fd52ebea19a4c21ae1e9b8df320e8373e79e4584fde1803cdc.exe
-
Size
126KB
-
MD5
52c1275a62d61ed71cc557774453fd46
-
SHA1
a829afc50b44c4a839b3c23a3e64e5df94c67eab
-
SHA256
e05366fa2ff255fd52ebea19a4c21ae1e9b8df320e8373e79e4584fde1803cdc
-
SHA512
c4bce480da29436734853ed929c0a58c4a5b5c91bf11b20fdc164946c2bb3f470a7287492f4737a071767bab98599106c056bd554e3d32bcd1c7fe3ad4ca18c4
-
SSDEEP
3072:UMYTJzp0fk7we/WGAcZ29lZBmSIENNw21mo4o0OQ+pmviqHQYP:UMYT70fkURYZ2ZxL1mozpgiqw2
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 3252 set thread context of 4964 3252 e05366fa2ff255fd52ebea19a4c21ae1e9b8df320e8373e79e4584fde1803cdc.exe 85 -
Suspicious behavior: EnumeratesProcesses 4 IoCs
pid Process 4964 e05366fa2ff255fd52ebea19a4c21ae1e9b8df320e8373e79e4584fde1803cdc.exe 4964 e05366fa2ff255fd52ebea19a4c21ae1e9b8df320e8373e79e4584fde1803cdc.exe 4964 e05366fa2ff255fd52ebea19a4c21ae1e9b8df320e8373e79e4584fde1803cdc.exe 4964 e05366fa2ff255fd52ebea19a4c21ae1e9b8df320e8373e79e4584fde1803cdc.exe -
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 3252 e05366fa2ff255fd52ebea19a4c21ae1e9b8df320e8373e79e4584fde1803cdc.exe -
Suspicious use of WriteProcessMemory 11 IoCs
description pid Process procid_target PID 3252 wrote to memory of 4964 3252 e05366fa2ff255fd52ebea19a4c21ae1e9b8df320e8373e79e4584fde1803cdc.exe 85 PID 3252 wrote to memory of 4964 3252 e05366fa2ff255fd52ebea19a4c21ae1e9b8df320e8373e79e4584fde1803cdc.exe 85 PID 3252 wrote to memory of 4964 3252 e05366fa2ff255fd52ebea19a4c21ae1e9b8df320e8373e79e4584fde1803cdc.exe 85 PID 3252 wrote to memory of 4964 3252 e05366fa2ff255fd52ebea19a4c21ae1e9b8df320e8373e79e4584fde1803cdc.exe 85 PID 3252 wrote to memory of 4964 3252 e05366fa2ff255fd52ebea19a4c21ae1e9b8df320e8373e79e4584fde1803cdc.exe 85 PID 3252 wrote to memory of 4964 3252 e05366fa2ff255fd52ebea19a4c21ae1e9b8df320e8373e79e4584fde1803cdc.exe 85 PID 3252 wrote to memory of 4964 3252 e05366fa2ff255fd52ebea19a4c21ae1e9b8df320e8373e79e4584fde1803cdc.exe 85 PID 4964 wrote to memory of 744 4964 e05366fa2ff255fd52ebea19a4c21ae1e9b8df320e8373e79e4584fde1803cdc.exe 27 PID 4964 wrote to memory of 744 4964 e05366fa2ff255fd52ebea19a4c21ae1e9b8df320e8373e79e4584fde1803cdc.exe 27 PID 4964 wrote to memory of 744 4964 e05366fa2ff255fd52ebea19a4c21ae1e9b8df320e8373e79e4584fde1803cdc.exe 27 PID 4964 wrote to memory of 744 4964 e05366fa2ff255fd52ebea19a4c21ae1e9b8df320e8373e79e4584fde1803cdc.exe 27
Processes
-
C:\Windows\Explorer.EXEC:\Windows\Explorer.EXE1⤵PID:744
-
C:\Users\Admin\AppData\Local\Temp\e05366fa2ff255fd52ebea19a4c21ae1e9b8df320e8373e79e4584fde1803cdc.exe"C:\Users\Admin\AppData\Local\Temp\e05366fa2ff255fd52ebea19a4c21ae1e9b8df320e8373e79e4584fde1803cdc.exe"2⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:3252 -
C:\Users\Admin\AppData\Local\Temp\e05366fa2ff255fd52ebea19a4c21ae1e9b8df320e8373e79e4584fde1803cdc.exeC:\Users\Admin\AppData\Local\Temp\e05366fa2ff255fd52ebea19a4c21ae1e9b8df320e8373e79e4584fde1803cdc.exe3⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:4964
-
-