Analysis
-
max time kernel
117s -
max time network
119s -
platform
windows7_x64 -
resource
win7-20231129-en -
resource tags
arch:x64arch:x86image:win7-20231129-enlocale:en-usos:windows7-x64system -
submitted
11-03-2024 00:13
Behavioral task
behavioral1
Sample
18f17375402cffe877271fdeedb0e78ebf492ba954da3bfcbc742fd5fd567492.exe
Resource
win7-20231129-en
windows7-x64
5 signatures
300 seconds
General
-
Target
18f17375402cffe877271fdeedb0e78ebf492ba954da3bfcbc742fd5fd567492.exe
-
Size
468KB
-
MD5
40dd510795e82f9a51301896809c2d95
-
SHA1
5bc4f3a04dae16cd6c69dd442551a795c9caa9ef
-
SHA256
18f17375402cffe877271fdeedb0e78ebf492ba954da3bfcbc742fd5fd567492
-
SHA512
c2fa10356790136e1bacbf0bc26eb015d6ceae49d2fb953fc80cb3085375d050000b2672cf15bc97fd633a31e6012e0fe47e282f31a614192840f85624b693c8
-
SSDEEP
6144:sR0tQjTAMFGf1nAB9/huXDttKkDklFuktsferJ/f7UF3HfuXeZWquoQ:sRK1y5IDnKkDxkme5f6HfuurHQ
Malware Config
Signatures
-
Detect ZGRat V1 2 IoCs
Processes:
resource yara_rule behavioral1/memory/1884-0-0x0000000000D30000-0x0000000000DA6000-memory.dmp family_zgrat_v1 behavioral1/memory/1884-2-0x0000000000450000-0x0000000000490000-memory.dmp family_zgrat_v1 -
Suspicious use of SetThreadContext 1 IoCs
Processes:
18f17375402cffe877271fdeedb0e78ebf492ba954da3bfcbc742fd5fd567492.exedescription pid process target process PID 1884 set thread context of 3032 1884 18f17375402cffe877271fdeedb0e78ebf492ba954da3bfcbc742fd5fd567492.exe RegAsm.exe -
Program crash 1 IoCs
Processes:
WerFault.exepid pid_target process target process 2072 3032 WerFault.exe RegAsm.exe -
Suspicious use of WriteProcessMemory 17 IoCs
Processes:
18f17375402cffe877271fdeedb0e78ebf492ba954da3bfcbc742fd5fd567492.exeRegAsm.exedescription pid process target process PID 1884 wrote to memory of 3032 1884 18f17375402cffe877271fdeedb0e78ebf492ba954da3bfcbc742fd5fd567492.exe RegAsm.exe PID 1884 wrote to memory of 3032 1884 18f17375402cffe877271fdeedb0e78ebf492ba954da3bfcbc742fd5fd567492.exe RegAsm.exe PID 1884 wrote to memory of 3032 1884 18f17375402cffe877271fdeedb0e78ebf492ba954da3bfcbc742fd5fd567492.exe RegAsm.exe PID 1884 wrote to memory of 3032 1884 18f17375402cffe877271fdeedb0e78ebf492ba954da3bfcbc742fd5fd567492.exe RegAsm.exe PID 1884 wrote to memory of 3032 1884 18f17375402cffe877271fdeedb0e78ebf492ba954da3bfcbc742fd5fd567492.exe RegAsm.exe PID 1884 wrote to memory of 3032 1884 18f17375402cffe877271fdeedb0e78ebf492ba954da3bfcbc742fd5fd567492.exe RegAsm.exe PID 1884 wrote to memory of 3032 1884 18f17375402cffe877271fdeedb0e78ebf492ba954da3bfcbc742fd5fd567492.exe RegAsm.exe PID 1884 wrote to memory of 3032 1884 18f17375402cffe877271fdeedb0e78ebf492ba954da3bfcbc742fd5fd567492.exe RegAsm.exe PID 1884 wrote to memory of 3032 1884 18f17375402cffe877271fdeedb0e78ebf492ba954da3bfcbc742fd5fd567492.exe RegAsm.exe PID 1884 wrote to memory of 3032 1884 18f17375402cffe877271fdeedb0e78ebf492ba954da3bfcbc742fd5fd567492.exe RegAsm.exe PID 1884 wrote to memory of 3032 1884 18f17375402cffe877271fdeedb0e78ebf492ba954da3bfcbc742fd5fd567492.exe RegAsm.exe PID 1884 wrote to memory of 3032 1884 18f17375402cffe877271fdeedb0e78ebf492ba954da3bfcbc742fd5fd567492.exe RegAsm.exe PID 1884 wrote to memory of 3032 1884 18f17375402cffe877271fdeedb0e78ebf492ba954da3bfcbc742fd5fd567492.exe RegAsm.exe PID 3032 wrote to memory of 2072 3032 RegAsm.exe WerFault.exe PID 3032 wrote to memory of 2072 3032 RegAsm.exe WerFault.exe PID 3032 wrote to memory of 2072 3032 RegAsm.exe WerFault.exe PID 3032 wrote to memory of 2072 3032 RegAsm.exe WerFault.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\18f17375402cffe877271fdeedb0e78ebf492ba954da3bfcbc742fd5fd567492.exe"C:\Users\Admin\AppData\Local\Temp\18f17375402cffe877271fdeedb0e78ebf492ba954da3bfcbc742fd5fd567492.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:1884 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵
- Suspicious use of WriteProcessMemory
PID:3032 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3032 -s 2563⤵
- Program crash
PID:2072