Analysis
-
max time kernel
129s -
max time network
132s -
platform
windows10-1703_x64 -
resource
win10-20230915-en -
resource tags
arch:x64arch:x86image:win10-20230915-enlocale:en-usos:windows10-1703-x64system -
submitted
05/10/2023, 22:10
Static task
static1
1 signatures
General
-
Target
1c3561efebff589b6868b992a2e3fc3ae24e2578e7e2f290cb0c54e5da4e33d7.exe
-
Size
1.7MB
-
MD5
1819c5ac223156a090a6a3219d2066d5
-
SHA1
8a3dce5b6ab47ea8c7dcfb8d89ed2cca2caed724
-
SHA256
1c3561efebff589b6868b992a2e3fc3ae24e2578e7e2f290cb0c54e5da4e33d7
-
SHA512
be51cf4d69eb31d4e694ce4d2c5fe8b71494943d66949d78794d45647140db6dea59e827a74b7935aba8f7a4614b453540010244ac189f2d18912bf1484e065e
-
SSDEEP
24576:PdxY5A0vimILMPcVZT6gH/A2Z46a9DhvhUFXeNf:PX0vimILMP4l6SAO46a3vAONf
Malware Config
Extracted
Family
mystic
C2
http://5.42.92.211/loghub/master
Signatures
-
Detect Mystic stealer payload 5 IoCs
resource yara_rule behavioral1/memory/4208-0-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/4208-3-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/4208-4-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/4208-5-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/4208-6-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 4136 set thread context of 4208 4136 1c3561efebff589b6868b992a2e3fc3ae24e2578e7e2f290cb0c54e5da4e33d7.exe 69 -
Program crash 1 IoCs
pid pid_target Process procid_target 4516 4136 WerFault.exe 68 -
Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 4136 wrote to memory of 4208 4136 1c3561efebff589b6868b992a2e3fc3ae24e2578e7e2f290cb0c54e5da4e33d7.exe 69 PID 4136 wrote to memory of 4208 4136 1c3561efebff589b6868b992a2e3fc3ae24e2578e7e2f290cb0c54e5da4e33d7.exe 69 PID 4136 wrote to memory of 4208 4136 1c3561efebff589b6868b992a2e3fc3ae24e2578e7e2f290cb0c54e5da4e33d7.exe 69 PID 4136 wrote to memory of 4208 4136 1c3561efebff589b6868b992a2e3fc3ae24e2578e7e2f290cb0c54e5da4e33d7.exe 69 PID 4136 wrote to memory of 4208 4136 1c3561efebff589b6868b992a2e3fc3ae24e2578e7e2f290cb0c54e5da4e33d7.exe 69 PID 4136 wrote to memory of 4208 4136 1c3561efebff589b6868b992a2e3fc3ae24e2578e7e2f290cb0c54e5da4e33d7.exe 69 PID 4136 wrote to memory of 4208 4136 1c3561efebff589b6868b992a2e3fc3ae24e2578e7e2f290cb0c54e5da4e33d7.exe 69 PID 4136 wrote to memory of 4208 4136 1c3561efebff589b6868b992a2e3fc3ae24e2578e7e2f290cb0c54e5da4e33d7.exe 69 PID 4136 wrote to memory of 4208 4136 1c3561efebff589b6868b992a2e3fc3ae24e2578e7e2f290cb0c54e5da4e33d7.exe 69 PID 4136 wrote to memory of 4208 4136 1c3561efebff589b6868b992a2e3fc3ae24e2578e7e2f290cb0c54e5da4e33d7.exe 69
Processes
-
C:\Users\Admin\AppData\Local\Temp\1c3561efebff589b6868b992a2e3fc3ae24e2578e7e2f290cb0c54e5da4e33d7.exe"C:\Users\Admin\AppData\Local\Temp\1c3561efebff589b6868b992a2e3fc3ae24e2578e7e2f290cb0c54e5da4e33d7.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:4136 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:4208
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4136 -s 3202⤵
- Program crash
PID:4516
-