Analysis
-
max time kernel
279s -
max time network
329s -
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 11:25
Static task
static1
Behavioral task
behavioral1
Sample
900c4cf2a785f3728ca2513ef05817461a6cd9e5f95b21f698564ff70bb24333.exe
Resource
win7-20221111-en
Behavioral task
behavioral2
Sample
900c4cf2a785f3728ca2513ef05817461a6cd9e5f95b21f698564ff70bb24333.exe
Resource
win10v2004-20221111-en
General
-
Target
900c4cf2a785f3728ca2513ef05817461a6cd9e5f95b21f698564ff70bb24333.exe
-
Size
1.3MB
-
MD5
54795769a568a3a3df21650ec9379151
-
SHA1
de2c8d7beed45cd5b953b93fa027634fe5c38f20
-
SHA256
900c4cf2a785f3728ca2513ef05817461a6cd9e5f95b21f698564ff70bb24333
-
SHA512
dcdb2316ce7ee92f526505a9f9ecbb31e238e86500f07702e5c648f844a62ab5e806d5cf4fae65740deed5cc527b86a86f1914212f99fbced793f84b43ce8ff2
-
SSDEEP
24576:zrKqlGCPcJKwybUDwEZZODYmR9G+gnbkk6XRJfe3DqYO/KpLwFfngWX4VmJPakg:zrKo4ZwCOnYjVmJPaj
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
Processes:
900c4cf2a785f3728ca2513ef05817461a6cd9e5f95b21f698564ff70bb24333.exedescription pid process target process PID 3100 set thread context of 2276 3100 900c4cf2a785f3728ca2513ef05817461a6cd9e5f95b21f698564ff70bb24333.exe 900c4cf2a785f3728ca2513ef05817461a6cd9e5f95b21f698564ff70bb24333.exe -
Suspicious use of SetWindowsHookEx 1 IoCs
Processes:
900c4cf2a785f3728ca2513ef05817461a6cd9e5f95b21f698564ff70bb24333.exepid process 2276 900c4cf2a785f3728ca2513ef05817461a6cd9e5f95b21f698564ff70bb24333.exe -
Suspicious use of WriteProcessMemory 10 IoCs
Processes:
900c4cf2a785f3728ca2513ef05817461a6cd9e5f95b21f698564ff70bb24333.exedescription pid process target process PID 3100 wrote to memory of 2276 3100 900c4cf2a785f3728ca2513ef05817461a6cd9e5f95b21f698564ff70bb24333.exe 900c4cf2a785f3728ca2513ef05817461a6cd9e5f95b21f698564ff70bb24333.exe PID 3100 wrote to memory of 2276 3100 900c4cf2a785f3728ca2513ef05817461a6cd9e5f95b21f698564ff70bb24333.exe 900c4cf2a785f3728ca2513ef05817461a6cd9e5f95b21f698564ff70bb24333.exe PID 3100 wrote to memory of 2276 3100 900c4cf2a785f3728ca2513ef05817461a6cd9e5f95b21f698564ff70bb24333.exe 900c4cf2a785f3728ca2513ef05817461a6cd9e5f95b21f698564ff70bb24333.exe PID 3100 wrote to memory of 2276 3100 900c4cf2a785f3728ca2513ef05817461a6cd9e5f95b21f698564ff70bb24333.exe 900c4cf2a785f3728ca2513ef05817461a6cd9e5f95b21f698564ff70bb24333.exe PID 3100 wrote to memory of 2276 3100 900c4cf2a785f3728ca2513ef05817461a6cd9e5f95b21f698564ff70bb24333.exe 900c4cf2a785f3728ca2513ef05817461a6cd9e5f95b21f698564ff70bb24333.exe PID 3100 wrote to memory of 2276 3100 900c4cf2a785f3728ca2513ef05817461a6cd9e5f95b21f698564ff70bb24333.exe 900c4cf2a785f3728ca2513ef05817461a6cd9e5f95b21f698564ff70bb24333.exe PID 3100 wrote to memory of 2276 3100 900c4cf2a785f3728ca2513ef05817461a6cd9e5f95b21f698564ff70bb24333.exe 900c4cf2a785f3728ca2513ef05817461a6cd9e5f95b21f698564ff70bb24333.exe PID 3100 wrote to memory of 2276 3100 900c4cf2a785f3728ca2513ef05817461a6cd9e5f95b21f698564ff70bb24333.exe 900c4cf2a785f3728ca2513ef05817461a6cd9e5f95b21f698564ff70bb24333.exe PID 3100 wrote to memory of 2276 3100 900c4cf2a785f3728ca2513ef05817461a6cd9e5f95b21f698564ff70bb24333.exe 900c4cf2a785f3728ca2513ef05817461a6cd9e5f95b21f698564ff70bb24333.exe PID 3100 wrote to memory of 2276 3100 900c4cf2a785f3728ca2513ef05817461a6cd9e5f95b21f698564ff70bb24333.exe 900c4cf2a785f3728ca2513ef05817461a6cd9e5f95b21f698564ff70bb24333.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\900c4cf2a785f3728ca2513ef05817461a6cd9e5f95b21f698564ff70bb24333.exe"C:\Users\Admin\AppData\Local\Temp\900c4cf2a785f3728ca2513ef05817461a6cd9e5f95b21f698564ff70bb24333.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:3100 -
C:\Users\Admin\AppData\Local\Temp\900c4cf2a785f3728ca2513ef05817461a6cd9e5f95b21f698564ff70bb24333.exe
- Suspicious use of SetWindowsHookEx
PID:2276