Analysis
-
max time kernel
166s -
max time network
183s -
platform
windows10-2004_x64 -
resource
win10v2004-20230915-en -
resource tags
arch:x64arch:x86image:win10v2004-20230915-enlocale:en-usos:windows10-2004-x64system -
submitted
10-10-2023 22:49
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
2bac97e041d224004b702ce070e3fb88c1c67efeeea7642260ad0da4c5de7261.exe
Resource
win7-20230831-en
windows7-x64
5 signatures
150 seconds
General
-
Target
2bac97e041d224004b702ce070e3fb88c1c67efeeea7642260ad0da4c5de7261.exe
-
Size
356KB
-
MD5
3305bb5496a51b98452378b305d10190
-
SHA1
130a00bda7f967f4c770e9cc9982399c0f6d5681
-
SHA256
2bac97e041d224004b702ce070e3fb88c1c67efeeea7642260ad0da4c5de7261
-
SHA512
dd1ebfd66e241ff9a4b6cd8079dc31d2e6b69284ec271abe0d71dd62a45ae219ec279ce341e478c6abfa559094effbcc57151c5da8712bc76803c68ea6c7f8df
-
SSDEEP
6144:urTeW/s5GqrO5aXnfEGIXWPvZAOpyl7xxpc1JtZap90rMsvGPrZvSDnfW7aq1c9k:FmcGqrOk86x+rFGFSFKDueWs0BC+
Malware Config
Extracted
Family
mystic
C2
http://5.42.92.211/loghub/master
Signatures
-
Detect Mystic stealer payload 6 IoCs
resource yara_rule behavioral2/memory/1800-0-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral2/memory/1800-1-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral2/memory/1800-2-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral2/memory/1800-3-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral2/memory/1800-4-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral2/memory/1800-5-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 3532 set thread context of 1800 3532 2bac97e041d224004b702ce070e3fb88c1c67efeeea7642260ad0da4c5de7261.exe 92 -
Program crash 1 IoCs
pid pid_target Process procid_target 4668 3532 WerFault.exe 84 -
Suspicious use of WriteProcessMemory 13 IoCs
description pid Process procid_target PID 3532 wrote to memory of 3644 3532 2bac97e041d224004b702ce070e3fb88c1c67efeeea7642260ad0da4c5de7261.exe 91 PID 3532 wrote to memory of 3644 3532 2bac97e041d224004b702ce070e3fb88c1c67efeeea7642260ad0da4c5de7261.exe 91 PID 3532 wrote to memory of 3644 3532 2bac97e041d224004b702ce070e3fb88c1c67efeeea7642260ad0da4c5de7261.exe 91 PID 3532 wrote to memory of 1800 3532 2bac97e041d224004b702ce070e3fb88c1c67efeeea7642260ad0da4c5de7261.exe 92 PID 3532 wrote to memory of 1800 3532 2bac97e041d224004b702ce070e3fb88c1c67efeeea7642260ad0da4c5de7261.exe 92 PID 3532 wrote to memory of 1800 3532 2bac97e041d224004b702ce070e3fb88c1c67efeeea7642260ad0da4c5de7261.exe 92 PID 3532 wrote to memory of 1800 3532 2bac97e041d224004b702ce070e3fb88c1c67efeeea7642260ad0da4c5de7261.exe 92 PID 3532 wrote to memory of 1800 3532 2bac97e041d224004b702ce070e3fb88c1c67efeeea7642260ad0da4c5de7261.exe 92 PID 3532 wrote to memory of 1800 3532 2bac97e041d224004b702ce070e3fb88c1c67efeeea7642260ad0da4c5de7261.exe 92 PID 3532 wrote to memory of 1800 3532 2bac97e041d224004b702ce070e3fb88c1c67efeeea7642260ad0da4c5de7261.exe 92 PID 3532 wrote to memory of 1800 3532 2bac97e041d224004b702ce070e3fb88c1c67efeeea7642260ad0da4c5de7261.exe 92 PID 3532 wrote to memory of 1800 3532 2bac97e041d224004b702ce070e3fb88c1c67efeeea7642260ad0da4c5de7261.exe 92 PID 3532 wrote to memory of 1800 3532 2bac97e041d224004b702ce070e3fb88c1c67efeeea7642260ad0da4c5de7261.exe 92
Processes
-
C:\Users\Admin\AppData\Local\Temp\2bac97e041d224004b702ce070e3fb88c1c67efeeea7642260ad0da4c5de7261.exe"C:\Users\Admin\AppData\Local\Temp\2bac97e041d224004b702ce070e3fb88c1c67efeeea7642260ad0da4c5de7261.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:3532 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:3644
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:1800
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3532 -s 2602⤵
- Program crash
PID:4668
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 436 -p 3532 -ip 35321⤵PID:3816