Analysis
-
max time kernel
294s -
max time network
326s -
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 13:33
Static task
static1
Behavioral task
behavioral1
Sample
435c3c457ae073644f7dcaf562de98b6eba6ae0f0883cfb5290a123dc3a422b0.exe
Resource
win7-20220901-en
Behavioral task
behavioral2
Sample
435c3c457ae073644f7dcaf562de98b6eba6ae0f0883cfb5290a123dc3a422b0.exe
Resource
win10v2004-20221111-en
General
-
Target
435c3c457ae073644f7dcaf562de98b6eba6ae0f0883cfb5290a123dc3a422b0.exe
-
Size
1.3MB
-
MD5
8fef485e9aae9c65a3fc5edf92b4126e
-
SHA1
ee48a6e850edf6ed4eef7facbfd1721e987481e2
-
SHA256
435c3c457ae073644f7dcaf562de98b6eba6ae0f0883cfb5290a123dc3a422b0
-
SHA512
3b0fb8fd7d3bb2220d634df3bb5e55e44429301a8ef5067766530b9c92eeb13bb05875b69ac0027f7e83f904adc5b056442bf9bb759e2723a54875c78de314bb
-
SSDEEP
24576:7rKqlGCPcJKwybUDwEZZODYmR9G+gnbkk6XRJfe3DqYO/KpLwFfngWX4VmJPakE:7rKo4ZwCOnYjVmJPab
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
Processes:
435c3c457ae073644f7dcaf562de98b6eba6ae0f0883cfb5290a123dc3a422b0.exedescription pid process target process PID 5052 set thread context of 4576 5052 435c3c457ae073644f7dcaf562de98b6eba6ae0f0883cfb5290a123dc3a422b0.exe 435c3c457ae073644f7dcaf562de98b6eba6ae0f0883cfb5290a123dc3a422b0.exe -
Suspicious use of WriteProcessMemory 10 IoCs
Processes:
435c3c457ae073644f7dcaf562de98b6eba6ae0f0883cfb5290a123dc3a422b0.exedescription pid process target process PID 5052 wrote to memory of 4576 5052 435c3c457ae073644f7dcaf562de98b6eba6ae0f0883cfb5290a123dc3a422b0.exe 435c3c457ae073644f7dcaf562de98b6eba6ae0f0883cfb5290a123dc3a422b0.exe PID 5052 wrote to memory of 4576 5052 435c3c457ae073644f7dcaf562de98b6eba6ae0f0883cfb5290a123dc3a422b0.exe 435c3c457ae073644f7dcaf562de98b6eba6ae0f0883cfb5290a123dc3a422b0.exe PID 5052 wrote to memory of 4576 5052 435c3c457ae073644f7dcaf562de98b6eba6ae0f0883cfb5290a123dc3a422b0.exe 435c3c457ae073644f7dcaf562de98b6eba6ae0f0883cfb5290a123dc3a422b0.exe PID 5052 wrote to memory of 4576 5052 435c3c457ae073644f7dcaf562de98b6eba6ae0f0883cfb5290a123dc3a422b0.exe 435c3c457ae073644f7dcaf562de98b6eba6ae0f0883cfb5290a123dc3a422b0.exe PID 5052 wrote to memory of 4576 5052 435c3c457ae073644f7dcaf562de98b6eba6ae0f0883cfb5290a123dc3a422b0.exe 435c3c457ae073644f7dcaf562de98b6eba6ae0f0883cfb5290a123dc3a422b0.exe PID 5052 wrote to memory of 4576 5052 435c3c457ae073644f7dcaf562de98b6eba6ae0f0883cfb5290a123dc3a422b0.exe 435c3c457ae073644f7dcaf562de98b6eba6ae0f0883cfb5290a123dc3a422b0.exe PID 5052 wrote to memory of 4576 5052 435c3c457ae073644f7dcaf562de98b6eba6ae0f0883cfb5290a123dc3a422b0.exe 435c3c457ae073644f7dcaf562de98b6eba6ae0f0883cfb5290a123dc3a422b0.exe PID 5052 wrote to memory of 4576 5052 435c3c457ae073644f7dcaf562de98b6eba6ae0f0883cfb5290a123dc3a422b0.exe 435c3c457ae073644f7dcaf562de98b6eba6ae0f0883cfb5290a123dc3a422b0.exe PID 5052 wrote to memory of 4576 5052 435c3c457ae073644f7dcaf562de98b6eba6ae0f0883cfb5290a123dc3a422b0.exe 435c3c457ae073644f7dcaf562de98b6eba6ae0f0883cfb5290a123dc3a422b0.exe PID 5052 wrote to memory of 4576 5052 435c3c457ae073644f7dcaf562de98b6eba6ae0f0883cfb5290a123dc3a422b0.exe 435c3c457ae073644f7dcaf562de98b6eba6ae0f0883cfb5290a123dc3a422b0.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\435c3c457ae073644f7dcaf562de98b6eba6ae0f0883cfb5290a123dc3a422b0.exe"C:\Users\Admin\AppData\Local\Temp\435c3c457ae073644f7dcaf562de98b6eba6ae0f0883cfb5290a123dc3a422b0.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:5052 -
C:\Users\Admin\AppData\Local\Temp\435c3c457ae073644f7dcaf562de98b6eba6ae0f0883cfb5290a123dc3a422b0.exePID:4576