Analysis
-
max time kernel
92s -
max time network
156s -
platform
windows10-2004_x64 -
resource
win10v2004-20220901-en -
resource tags
arch:x64arch:x86image:win10v2004-20220901-enlocale:en-usos:windows10-2004-x64system -
submitted
23-11-2022 13:13
Static task
static1
Behavioral task
behavioral1
Sample
4f49c8f71bf27b5f2ba4d1182980eb2ef0d9639a5717b73cd8ba5faf043d40d9.exe
Resource
win7-20221111-en
Behavioral task
behavioral2
Sample
4f49c8f71bf27b5f2ba4d1182980eb2ef0d9639a5717b73cd8ba5faf043d40d9.exe
Resource
win10v2004-20220901-en
General
-
Target
4f49c8f71bf27b5f2ba4d1182980eb2ef0d9639a5717b73cd8ba5faf043d40d9.exe
-
Size
1.6MB
-
MD5
1f7f4bedd2e044bd8cbb5c1e6a7f2348
-
SHA1
beb9ebfb6a1bf0f9f302d08e01fa64d83c61c268
-
SHA256
4f49c8f71bf27b5f2ba4d1182980eb2ef0d9639a5717b73cd8ba5faf043d40d9
-
SHA512
e8ef7f7ed4820363f082dcec9fed5bb40d97ba8b0a3677a794db8c986c93236db0fb5bef201ef68e318baf504ea48f0e587d43dec08447b8d06f702f40f922ae
-
SSDEEP
24576:NzD5urNhRWx2Mk4JJQByw7Imlq3g495S0PwbphrpgXXOZuv/rTWeR5j4UwJZQUY:n6/ye0PIphrp9Zuvjqa0Uid
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
Processes:
4f49c8f71bf27b5f2ba4d1182980eb2ef0d9639a5717b73cd8ba5faf043d40d9.exedescription pid process target process PID 4180 set thread context of 3720 4180 4f49c8f71bf27b5f2ba4d1182980eb2ef0d9639a5717b73cd8ba5faf043d40d9.exe 4f49c8f71bf27b5f2ba4d1182980eb2ef0d9639a5717b73cd8ba5faf043d40d9.exe -
Suspicious use of SetWindowsHookEx 5 IoCs
Processes:
4f49c8f71bf27b5f2ba4d1182980eb2ef0d9639a5717b73cd8ba5faf043d40d9.exepid process 3720 4f49c8f71bf27b5f2ba4d1182980eb2ef0d9639a5717b73cd8ba5faf043d40d9.exe 3720 4f49c8f71bf27b5f2ba4d1182980eb2ef0d9639a5717b73cd8ba5faf043d40d9.exe 3720 4f49c8f71bf27b5f2ba4d1182980eb2ef0d9639a5717b73cd8ba5faf043d40d9.exe 3720 4f49c8f71bf27b5f2ba4d1182980eb2ef0d9639a5717b73cd8ba5faf043d40d9.exe 3720 4f49c8f71bf27b5f2ba4d1182980eb2ef0d9639a5717b73cd8ba5faf043d40d9.exe -
Suspicious use of WriteProcessMemory 10 IoCs
Processes:
4f49c8f71bf27b5f2ba4d1182980eb2ef0d9639a5717b73cd8ba5faf043d40d9.exedescription pid process target process PID 4180 wrote to memory of 3720 4180 4f49c8f71bf27b5f2ba4d1182980eb2ef0d9639a5717b73cd8ba5faf043d40d9.exe 4f49c8f71bf27b5f2ba4d1182980eb2ef0d9639a5717b73cd8ba5faf043d40d9.exe PID 4180 wrote to memory of 3720 4180 4f49c8f71bf27b5f2ba4d1182980eb2ef0d9639a5717b73cd8ba5faf043d40d9.exe 4f49c8f71bf27b5f2ba4d1182980eb2ef0d9639a5717b73cd8ba5faf043d40d9.exe PID 4180 wrote to memory of 3720 4180 4f49c8f71bf27b5f2ba4d1182980eb2ef0d9639a5717b73cd8ba5faf043d40d9.exe 4f49c8f71bf27b5f2ba4d1182980eb2ef0d9639a5717b73cd8ba5faf043d40d9.exe PID 4180 wrote to memory of 3720 4180 4f49c8f71bf27b5f2ba4d1182980eb2ef0d9639a5717b73cd8ba5faf043d40d9.exe 4f49c8f71bf27b5f2ba4d1182980eb2ef0d9639a5717b73cd8ba5faf043d40d9.exe PID 4180 wrote to memory of 3720 4180 4f49c8f71bf27b5f2ba4d1182980eb2ef0d9639a5717b73cd8ba5faf043d40d9.exe 4f49c8f71bf27b5f2ba4d1182980eb2ef0d9639a5717b73cd8ba5faf043d40d9.exe PID 4180 wrote to memory of 3720 4180 4f49c8f71bf27b5f2ba4d1182980eb2ef0d9639a5717b73cd8ba5faf043d40d9.exe 4f49c8f71bf27b5f2ba4d1182980eb2ef0d9639a5717b73cd8ba5faf043d40d9.exe PID 4180 wrote to memory of 3720 4180 4f49c8f71bf27b5f2ba4d1182980eb2ef0d9639a5717b73cd8ba5faf043d40d9.exe 4f49c8f71bf27b5f2ba4d1182980eb2ef0d9639a5717b73cd8ba5faf043d40d9.exe PID 4180 wrote to memory of 3720 4180 4f49c8f71bf27b5f2ba4d1182980eb2ef0d9639a5717b73cd8ba5faf043d40d9.exe 4f49c8f71bf27b5f2ba4d1182980eb2ef0d9639a5717b73cd8ba5faf043d40d9.exe PID 4180 wrote to memory of 3720 4180 4f49c8f71bf27b5f2ba4d1182980eb2ef0d9639a5717b73cd8ba5faf043d40d9.exe 4f49c8f71bf27b5f2ba4d1182980eb2ef0d9639a5717b73cd8ba5faf043d40d9.exe PID 4180 wrote to memory of 3720 4180 4f49c8f71bf27b5f2ba4d1182980eb2ef0d9639a5717b73cd8ba5faf043d40d9.exe 4f49c8f71bf27b5f2ba4d1182980eb2ef0d9639a5717b73cd8ba5faf043d40d9.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\4f49c8f71bf27b5f2ba4d1182980eb2ef0d9639a5717b73cd8ba5faf043d40d9.exe"C:\Users\Admin\AppData\Local\Temp\4f49c8f71bf27b5f2ba4d1182980eb2ef0d9639a5717b73cd8ba5faf043d40d9.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:4180 -
C:\Users\Admin\AppData\Local\Temp\4f49c8f71bf27b5f2ba4d1182980eb2ef0d9639a5717b73cd8ba5faf043d40d9.exe"C:\Users\Admin\AppData\Local\Temp\4f49c8f71bf27b5f2ba4d1182980eb2ef0d9639a5717b73cd8ba5faf043d40d9.exe"2⤵
- Suspicious use of SetWindowsHookEx
PID:3720
-