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 14:08
Static task
static1
Behavioral task
behavioral1
Sample
2af4ea45dd4470da2228add550f5ef2dcb4a8c4bc5808d15e6c09e4c7c140e10_JC.exe
Resource
win7-20230831-en
windows7-x64
5 signatures
150 seconds
General
-
Target
2af4ea45dd4470da2228add550f5ef2dcb4a8c4bc5808d15e6c09e4c7c140e10_JC.exe
-
Size
364KB
-
MD5
f8308e5f788b1a3c15dd074701afd38d
-
SHA1
f5b88a757fb18c2f1c982832374bd43c147d7f8c
-
SHA256
2af4ea45dd4470da2228add550f5ef2dcb4a8c4bc5808d15e6c09e4c7c140e10
-
SHA512
e45ba036da450e2c128d0badfe2c3b60a9a6d5592986713fa3bf626dd6adf4542090b2de63a6c228cb6118fdc2ba1036746e3d15948e8eeb612e9280f1260607
-
SSDEEP
6144:QmXAxlt3fuPgyxhV5dAOPI4MT0diye9znjO13lPGCH:QHxltWTVI4gkwQGCH
Malware Config
Extracted
Family
mystic
C2
http://5.42.92.211/loghub/master
Signatures
-
Detect Mystic stealer payload 8 IoCs
resource yara_rule behavioral1/memory/2072-6-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2072-8-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2072-10-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2072-13-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2072-15-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2072-17-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2072-18-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2072-19-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2440 set thread context of 2072 2440 2af4ea45dd4470da2228add550f5ef2dcb4a8c4bc5808d15e6c09e4c7c140e10_JC.exe 29 -
Program crash 1 IoCs
pid pid_target Process procid_target 2796 2440 WerFault.exe 15 -
Suspicious use of WriteProcessMemory 25 IoCs
description pid Process procid_target PID 2440 wrote to memory of 1976 2440 2af4ea45dd4470da2228add550f5ef2dcb4a8c4bc5808d15e6c09e4c7c140e10_JC.exe 28 PID 2440 wrote to memory of 1976 2440 2af4ea45dd4470da2228add550f5ef2dcb4a8c4bc5808d15e6c09e4c7c140e10_JC.exe 28 PID 2440 wrote to memory of 1976 2440 2af4ea45dd4470da2228add550f5ef2dcb4a8c4bc5808d15e6c09e4c7c140e10_JC.exe 28 PID 2440 wrote to memory of 1976 2440 2af4ea45dd4470da2228add550f5ef2dcb4a8c4bc5808d15e6c09e4c7c140e10_JC.exe 28 PID 2440 wrote to memory of 1976 2440 2af4ea45dd4470da2228add550f5ef2dcb4a8c4bc5808d15e6c09e4c7c140e10_JC.exe 28 PID 2440 wrote to memory of 1976 2440 2af4ea45dd4470da2228add550f5ef2dcb4a8c4bc5808d15e6c09e4c7c140e10_JC.exe 28 PID 2440 wrote to memory of 1976 2440 2af4ea45dd4470da2228add550f5ef2dcb4a8c4bc5808d15e6c09e4c7c140e10_JC.exe 28 PID 2440 wrote to memory of 2072 2440 2af4ea45dd4470da2228add550f5ef2dcb4a8c4bc5808d15e6c09e4c7c140e10_JC.exe 29 PID 2440 wrote to memory of 2072 2440 2af4ea45dd4470da2228add550f5ef2dcb4a8c4bc5808d15e6c09e4c7c140e10_JC.exe 29 PID 2440 wrote to memory of 2072 2440 2af4ea45dd4470da2228add550f5ef2dcb4a8c4bc5808d15e6c09e4c7c140e10_JC.exe 29 PID 2440 wrote to memory of 2072 2440 2af4ea45dd4470da2228add550f5ef2dcb4a8c4bc5808d15e6c09e4c7c140e10_JC.exe 29 PID 2440 wrote to memory of 2072 2440 2af4ea45dd4470da2228add550f5ef2dcb4a8c4bc5808d15e6c09e4c7c140e10_JC.exe 29 PID 2440 wrote to memory of 2072 2440 2af4ea45dd4470da2228add550f5ef2dcb4a8c4bc5808d15e6c09e4c7c140e10_JC.exe 29 PID 2440 wrote to memory of 2072 2440 2af4ea45dd4470da2228add550f5ef2dcb4a8c4bc5808d15e6c09e4c7c140e10_JC.exe 29 PID 2440 wrote to memory of 2072 2440 2af4ea45dd4470da2228add550f5ef2dcb4a8c4bc5808d15e6c09e4c7c140e10_JC.exe 29 PID 2440 wrote to memory of 2072 2440 2af4ea45dd4470da2228add550f5ef2dcb4a8c4bc5808d15e6c09e4c7c140e10_JC.exe 29 PID 2440 wrote to memory of 2072 2440 2af4ea45dd4470da2228add550f5ef2dcb4a8c4bc5808d15e6c09e4c7c140e10_JC.exe 29 PID 2440 wrote to memory of 2072 2440 2af4ea45dd4470da2228add550f5ef2dcb4a8c4bc5808d15e6c09e4c7c140e10_JC.exe 29 PID 2440 wrote to memory of 2072 2440 2af4ea45dd4470da2228add550f5ef2dcb4a8c4bc5808d15e6c09e4c7c140e10_JC.exe 29 PID 2440 wrote to memory of 2072 2440 2af4ea45dd4470da2228add550f5ef2dcb4a8c4bc5808d15e6c09e4c7c140e10_JC.exe 29 PID 2440 wrote to memory of 2072 2440 2af4ea45dd4470da2228add550f5ef2dcb4a8c4bc5808d15e6c09e4c7c140e10_JC.exe 29 PID 2440 wrote to memory of 2796 2440 2af4ea45dd4470da2228add550f5ef2dcb4a8c4bc5808d15e6c09e4c7c140e10_JC.exe 30 PID 2440 wrote to memory of 2796 2440 2af4ea45dd4470da2228add550f5ef2dcb4a8c4bc5808d15e6c09e4c7c140e10_JC.exe 30 PID 2440 wrote to memory of 2796 2440 2af4ea45dd4470da2228add550f5ef2dcb4a8c4bc5808d15e6c09e4c7c140e10_JC.exe 30 PID 2440 wrote to memory of 2796 2440 2af4ea45dd4470da2228add550f5ef2dcb4a8c4bc5808d15e6c09e4c7c140e10_JC.exe 30
Processes
-
C:\Users\Admin\AppData\Local\Temp\2af4ea45dd4470da2228add550f5ef2dcb4a8c4bc5808d15e6c09e4c7c140e10_JC.exe"C:\Users\Admin\AppData\Local\Temp\2af4ea45dd4470da2228add550f5ef2dcb4a8c4bc5808d15e6c09e4c7c140e10_JC.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2440 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:1976
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:2072
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2440 -s 1002⤵
- Program crash
PID:2796
-