Analysis
-
max time kernel
57s -
max time network
34s -
platform
windows7_x64 -
resource
win7-20221111-en -
resource tags
arch:x64arch:x86image:win7-20221111-enlocale:en-usos:windows7-x64system -
submitted
06-12-2022 16:50
Static task
static1
Behavioral task
behavioral1
Sample
8f1cf8b66e26d0bfbef1d12ae94fb4851b1664b45e1791c016592b3f9b78632f.exe
Resource
win7-20221111-en
Behavioral task
behavioral2
Sample
8f1cf8b66e26d0bfbef1d12ae94fb4851b1664b45e1791c016592b3f9b78632f.exe
Resource
win10v2004-20220812-en
General
-
Target
8f1cf8b66e26d0bfbef1d12ae94fb4851b1664b45e1791c016592b3f9b78632f.exe
-
Size
76KB
-
MD5
032e0bdef8c28cbb807774f0b0557852
-
SHA1
25cee0f1796d7c17f29d1b25e68b51051acb1bab
-
SHA256
8f1cf8b66e26d0bfbef1d12ae94fb4851b1664b45e1791c016592b3f9b78632f
-
SHA512
e107a108728d060e3809b5fc51f6ee15cfe905ed74ad00c430b1fc7c48c2d51dd415b398cfc657775b0d39b884d8fa4c804ca175ab279d8b622a47a53f953027
-
SSDEEP
1536:GBx77D6OCvpMc99BB9DD6OCn8FFPHODY2kuhws+/zGYBGo51:i7eOCCq9pDeOCn8F9qklz1Go51
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 1672 set thread context of 576 1672 8f1cf8b66e26d0bfbef1d12ae94fb4851b1664b45e1791c016592b3f9b78632f.exe 28 -
Suspicious use of SetWindowsHookEx 2 IoCs
pid Process 1672 8f1cf8b66e26d0bfbef1d12ae94fb4851b1664b45e1791c016592b3f9b78632f.exe 576 8f1cf8b66e26d0bfbef1d12ae94fb4851b1664b45e1791c016592b3f9b78632f.exe -
Suspicious use of WriteProcessMemory 9 IoCs
description pid Process procid_target PID 1672 wrote to memory of 576 1672 8f1cf8b66e26d0bfbef1d12ae94fb4851b1664b45e1791c016592b3f9b78632f.exe 28 PID 1672 wrote to memory of 576 1672 8f1cf8b66e26d0bfbef1d12ae94fb4851b1664b45e1791c016592b3f9b78632f.exe 28 PID 1672 wrote to memory of 576 1672 8f1cf8b66e26d0bfbef1d12ae94fb4851b1664b45e1791c016592b3f9b78632f.exe 28 PID 1672 wrote to memory of 576 1672 8f1cf8b66e26d0bfbef1d12ae94fb4851b1664b45e1791c016592b3f9b78632f.exe 28 PID 1672 wrote to memory of 576 1672 8f1cf8b66e26d0bfbef1d12ae94fb4851b1664b45e1791c016592b3f9b78632f.exe 28 PID 1672 wrote to memory of 576 1672 8f1cf8b66e26d0bfbef1d12ae94fb4851b1664b45e1791c016592b3f9b78632f.exe 28 PID 1672 wrote to memory of 576 1672 8f1cf8b66e26d0bfbef1d12ae94fb4851b1664b45e1791c016592b3f9b78632f.exe 28 PID 1672 wrote to memory of 576 1672 8f1cf8b66e26d0bfbef1d12ae94fb4851b1664b45e1791c016592b3f9b78632f.exe 28 PID 1672 wrote to memory of 576 1672 8f1cf8b66e26d0bfbef1d12ae94fb4851b1664b45e1791c016592b3f9b78632f.exe 28
Processes
-
C:\Users\Admin\AppData\Local\Temp\8f1cf8b66e26d0bfbef1d12ae94fb4851b1664b45e1791c016592b3f9b78632f.exe"C:\Users\Admin\AppData\Local\Temp\8f1cf8b66e26d0bfbef1d12ae94fb4851b1664b45e1791c016592b3f9b78632f.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:1672 -
C:\Users\Admin\AppData\Local\Temp\8f1cf8b66e26d0bfbef1d12ae94fb4851b1664b45e1791c016592b3f9b78632f.exe"C:\Users\Admin\AppData\Local\Temp\8f1cf8b66e26d0bfbef1d12ae94fb4851b1664b45e1791c016592b3f9b78632f.exe"2⤵
- Suspicious use of SetWindowsHookEx
PID:576
-