Analysis
-
max time kernel
117s -
max time network
122s -
platform
windows7_x64 -
resource
win7-20230831-en -
resource tags
arch:x64arch:x86image:win7-20230831-enlocale:en-usos:windows7-x64system -
submitted
11-10-2023 06:58
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
4153d2b1cb476033ed0382be3027083b5f91fcd4eee4c831b6d31f1d86a02b36.exe
Resource
win7-20230831-en
windows7-x64
5 signatures
150 seconds
General
-
Target
4153d2b1cb476033ed0382be3027083b5f91fcd4eee4c831b6d31f1d86a02b36.exe
-
Size
1016KB
-
MD5
a8633acae1c192b00929eed57f24ed86
-
SHA1
5c05004269ee5e44fad3076ab987a9c11b14b5b8
-
SHA256
4153d2b1cb476033ed0382be3027083b5f91fcd4eee4c831b6d31f1d86a02b36
-
SHA512
09f76b3f6d1ae3bc71b1a6e491ea70326ac1a77326c5fa8f51ec38c82e3f40c5d605ccbf5550c5b47e35d35fbeb7399cb49be9b4f923875fdc1af2c4ed25a699
-
SSDEEP
12288:z+WAo5YaBYDKzcx9jkmP8bey7/0RDMmZZxnyUuyyulvbG8VmNQVR/9:zxVYDKzcx9jkmPe/knxykG09
Malware Config
Signatures
-
Detect Mystic stealer payload 6 IoCs
resource yara_rule behavioral1/memory/2104-3-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2104-4-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2104-5-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2104-7-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2104-9-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2104-11-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2416 set thread context of 2104 2416 4153d2b1cb476033ed0382be3027083b5f91fcd4eee4c831b6d31f1d86a02b36.exe 29 -
Program crash 2 IoCs
pid pid_target Process procid_target 2744 2416 WerFault.exe 27 2804 2104 WerFault.exe 29 -
Suspicious use of WriteProcessMemory 25 IoCs
description pid Process procid_target PID 2416 wrote to memory of 2104 2416 4153d2b1cb476033ed0382be3027083b5f91fcd4eee4c831b6d31f1d86a02b36.exe 29 PID 2416 wrote to memory of 2104 2416 4153d2b1cb476033ed0382be3027083b5f91fcd4eee4c831b6d31f1d86a02b36.exe 29 PID 2416 wrote to memory of 2104 2416 4153d2b1cb476033ed0382be3027083b5f91fcd4eee4c831b6d31f1d86a02b36.exe 29 PID 2416 wrote to memory of 2104 2416 4153d2b1cb476033ed0382be3027083b5f91fcd4eee4c831b6d31f1d86a02b36.exe 29 PID 2416 wrote to memory of 2104 2416 4153d2b1cb476033ed0382be3027083b5f91fcd4eee4c831b6d31f1d86a02b36.exe 29 PID 2416 wrote to memory of 2104 2416 4153d2b1cb476033ed0382be3027083b5f91fcd4eee4c831b6d31f1d86a02b36.exe 29 PID 2416 wrote to memory of 2104 2416 4153d2b1cb476033ed0382be3027083b5f91fcd4eee4c831b6d31f1d86a02b36.exe 29 PID 2416 wrote to memory of 2104 2416 4153d2b1cb476033ed0382be3027083b5f91fcd4eee4c831b6d31f1d86a02b36.exe 29 PID 2416 wrote to memory of 2104 2416 4153d2b1cb476033ed0382be3027083b5f91fcd4eee4c831b6d31f1d86a02b36.exe 29 PID 2416 wrote to memory of 2104 2416 4153d2b1cb476033ed0382be3027083b5f91fcd4eee4c831b6d31f1d86a02b36.exe 29 PID 2416 wrote to memory of 2104 2416 4153d2b1cb476033ed0382be3027083b5f91fcd4eee4c831b6d31f1d86a02b36.exe 29 PID 2416 wrote to memory of 2104 2416 4153d2b1cb476033ed0382be3027083b5f91fcd4eee4c831b6d31f1d86a02b36.exe 29 PID 2416 wrote to memory of 2104 2416 4153d2b1cb476033ed0382be3027083b5f91fcd4eee4c831b6d31f1d86a02b36.exe 29 PID 2416 wrote to memory of 2104 2416 4153d2b1cb476033ed0382be3027083b5f91fcd4eee4c831b6d31f1d86a02b36.exe 29 PID 2416 wrote to memory of 2744 2416 4153d2b1cb476033ed0382be3027083b5f91fcd4eee4c831b6d31f1d86a02b36.exe 30 PID 2416 wrote to memory of 2744 2416 4153d2b1cb476033ed0382be3027083b5f91fcd4eee4c831b6d31f1d86a02b36.exe 30 PID 2416 wrote to memory of 2744 2416 4153d2b1cb476033ed0382be3027083b5f91fcd4eee4c831b6d31f1d86a02b36.exe 30 PID 2416 wrote to memory of 2744 2416 4153d2b1cb476033ed0382be3027083b5f91fcd4eee4c831b6d31f1d86a02b36.exe 30 PID 2104 wrote to memory of 2804 2104 AppLaunch.exe 31 PID 2104 wrote to memory of 2804 2104 AppLaunch.exe 31 PID 2104 wrote to memory of 2804 2104 AppLaunch.exe 31 PID 2104 wrote to memory of 2804 2104 AppLaunch.exe 31 PID 2104 wrote to memory of 2804 2104 AppLaunch.exe 31 PID 2104 wrote to memory of 2804 2104 AppLaunch.exe 31 PID 2104 wrote to memory of 2804 2104 AppLaunch.exe 31
Processes
-
C:\Users\Admin\AppData\Local\Temp\4153d2b1cb476033ed0382be3027083b5f91fcd4eee4c831b6d31f1d86a02b36.exe"C:\Users\Admin\AppData\Local\Temp\4153d2b1cb476033ed0382be3027083b5f91fcd4eee4c831b6d31f1d86a02b36.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2416 -
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:2104 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2104 -s 1963⤵
- Program crash
PID:2804
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2416 -s 922⤵
- Program crash
PID:2744
-