Analysis
-
max time kernel
119s -
max time network
123s -
platform
windows7_x64 -
resource
win7-20230831-en -
resource tags
arch:x64arch:x86image:win7-20230831-enlocale:en-usos:windows7-x64system -
submitted
11/10/2023, 20:26
Static task
static1
Behavioral task
behavioral1
Sample
fab788167c4a7649ab86c259aed26b2b21b6a8c576e41d26dba78c7659fc6465.exe
Resource
win7-20230831-en
5 signatures
150 seconds
General
-
Target
fab788167c4a7649ab86c259aed26b2b21b6a8c576e41d26dba78c7659fc6465.exe
-
Size
380KB
-
MD5
47a554afcbad97c3199a3663193ff29f
-
SHA1
fbd0a67f165fe458cc20b8f9e259d4eb5d0b8438
-
SHA256
fab788167c4a7649ab86c259aed26b2b21b6a8c576e41d26dba78c7659fc6465
-
SHA512
72f32f6d978f0ac3276502095e867b9a976e1ea25ce1dabf8e59273b55626e39c3630beb635e07c8532b70bb6af9060e2ac164b594914c7e656d5d06005c151d
-
SSDEEP
6144:AlPnhHX110KwTVSf3pOCq5b6uAO4wogYpk+kI2v4mgEqwm:AlPh3110dVaUcuOngYpkiU4mgVwm
Malware Config
Signatures
-
Detect Mystic stealer payload 6 IoCs
resource yara_rule behavioral1/memory/1236-3-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/1236-4-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/1236-5-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/1236-7-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/1236-9-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/1236-11-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2972 set thread context of 1236 2972 fab788167c4a7649ab86c259aed26b2b21b6a8c576e41d26dba78c7659fc6465.exe 28 -
Program crash 2 IoCs
pid pid_target Process procid_target 1668 2972 WerFault.exe 16 2652 1236 WerFault.exe 28 -
Suspicious use of WriteProcessMemory 25 IoCs
description pid Process procid_target PID 2972 wrote to memory of 1236 2972 fab788167c4a7649ab86c259aed26b2b21b6a8c576e41d26dba78c7659fc6465.exe 28 PID 2972 wrote to memory of 1236 2972 fab788167c4a7649ab86c259aed26b2b21b6a8c576e41d26dba78c7659fc6465.exe 28 PID 2972 wrote to memory of 1236 2972 fab788167c4a7649ab86c259aed26b2b21b6a8c576e41d26dba78c7659fc6465.exe 28 PID 2972 wrote to memory of 1236 2972 fab788167c4a7649ab86c259aed26b2b21b6a8c576e41d26dba78c7659fc6465.exe 28 PID 2972 wrote to memory of 1236 2972 fab788167c4a7649ab86c259aed26b2b21b6a8c576e41d26dba78c7659fc6465.exe 28 PID 2972 wrote to memory of 1236 2972 fab788167c4a7649ab86c259aed26b2b21b6a8c576e41d26dba78c7659fc6465.exe 28 PID 2972 wrote to memory of 1236 2972 fab788167c4a7649ab86c259aed26b2b21b6a8c576e41d26dba78c7659fc6465.exe 28 PID 2972 wrote to memory of 1236 2972 fab788167c4a7649ab86c259aed26b2b21b6a8c576e41d26dba78c7659fc6465.exe 28 PID 2972 wrote to memory of 1236 2972 fab788167c4a7649ab86c259aed26b2b21b6a8c576e41d26dba78c7659fc6465.exe 28 PID 2972 wrote to memory of 1236 2972 fab788167c4a7649ab86c259aed26b2b21b6a8c576e41d26dba78c7659fc6465.exe 28 PID 2972 wrote to memory of 1236 2972 fab788167c4a7649ab86c259aed26b2b21b6a8c576e41d26dba78c7659fc6465.exe 28 PID 2972 wrote to memory of 1236 2972 fab788167c4a7649ab86c259aed26b2b21b6a8c576e41d26dba78c7659fc6465.exe 28 PID 2972 wrote to memory of 1236 2972 fab788167c4a7649ab86c259aed26b2b21b6a8c576e41d26dba78c7659fc6465.exe 28 PID 2972 wrote to memory of 1236 2972 fab788167c4a7649ab86c259aed26b2b21b6a8c576e41d26dba78c7659fc6465.exe 28 PID 2972 wrote to memory of 1668 2972 fab788167c4a7649ab86c259aed26b2b21b6a8c576e41d26dba78c7659fc6465.exe 29 PID 2972 wrote to memory of 1668 2972 fab788167c4a7649ab86c259aed26b2b21b6a8c576e41d26dba78c7659fc6465.exe 29 PID 2972 wrote to memory of 1668 2972 fab788167c4a7649ab86c259aed26b2b21b6a8c576e41d26dba78c7659fc6465.exe 29 PID 2972 wrote to memory of 1668 2972 fab788167c4a7649ab86c259aed26b2b21b6a8c576e41d26dba78c7659fc6465.exe 29 PID 1236 wrote to memory of 2652 1236 AppLaunch.exe 30 PID 1236 wrote to memory of 2652 1236 AppLaunch.exe 30 PID 1236 wrote to memory of 2652 1236 AppLaunch.exe 30 PID 1236 wrote to memory of 2652 1236 AppLaunch.exe 30 PID 1236 wrote to memory of 2652 1236 AppLaunch.exe 30 PID 1236 wrote to memory of 2652 1236 AppLaunch.exe 30 PID 1236 wrote to memory of 2652 1236 AppLaunch.exe 30
Processes
-
C:\Users\Admin\AppData\Local\Temp\fab788167c4a7649ab86c259aed26b2b21b6a8c576e41d26dba78c7659fc6465.exe"C:\Users\Admin\AppData\Local\Temp\fab788167c4a7649ab86c259aed26b2b21b6a8c576e41d26dba78c7659fc6465.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2972 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵
- Suspicious use of WriteProcessMemory
PID:1236 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 1236 -s 1963⤵
- Program crash
PID:2652
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2972 -s 522⤵
- Program crash
PID:1668
-