Analysis
-
max time kernel
134s -
max time network
147s -
platform
windows10-2004_x64 -
resource
win10v2004-20230915-en -
resource tags
arch:x64arch:x86image:win10v2004-20230915-enlocale:en-usos:windows10-2004-x64system -
submitted
12-10-2023 04:57
Static task
static1
Behavioral task
behavioral1
Sample
3852ed3843fd500abf880ec525bf190281d80b78d58b25510fc166214b56dbaa.exe
Resource
win7-20230831-en
windows7-x64
3 signatures
150 seconds
General
-
Target
3852ed3843fd500abf880ec525bf190281d80b78d58b25510fc166214b56dbaa.exe
-
Size
700KB
-
MD5
3fa9577e900029040fa402dac02a7895
-
SHA1
961baff9331ac40dd9bc8d55fd420663fc78e935
-
SHA256
3852ed3843fd500abf880ec525bf190281d80b78d58b25510fc166214b56dbaa
-
SHA512
69f98ddfb9791ee512f0af21524e209f5a43fa57044c20676c9649b11ca7fd1d884308410dbe86e9fd1fc52d50568c4f2547b7366c833190430f3d502cca6624
-
SSDEEP
6144:MSvGAafgBMniUwluzlcy/XVucQ5d8tU25CbSyadSxbXuvfz:NGfg2i8VucQ5StybFad4Cz
Malware Config
Extracted
Family
mystic
C2
http://5.42.92.211/loghub/master
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 4624 set thread context of 3524 4624 3852ed3843fd500abf880ec525bf190281d80b78d58b25510fc166214b56dbaa.exe 95 -
Program crash 1 IoCs
pid pid_target Process procid_target 4392 4624 WerFault.exe 84 -
Suspicious use of WriteProcessMemory 13 IoCs
description pid Process procid_target PID 4624 wrote to memory of 2800 4624 3852ed3843fd500abf880ec525bf190281d80b78d58b25510fc166214b56dbaa.exe 94 PID 4624 wrote to memory of 2800 4624 3852ed3843fd500abf880ec525bf190281d80b78d58b25510fc166214b56dbaa.exe 94 PID 4624 wrote to memory of 2800 4624 3852ed3843fd500abf880ec525bf190281d80b78d58b25510fc166214b56dbaa.exe 94 PID 4624 wrote to memory of 3524 4624 3852ed3843fd500abf880ec525bf190281d80b78d58b25510fc166214b56dbaa.exe 95 PID 4624 wrote to memory of 3524 4624 3852ed3843fd500abf880ec525bf190281d80b78d58b25510fc166214b56dbaa.exe 95 PID 4624 wrote to memory of 3524 4624 3852ed3843fd500abf880ec525bf190281d80b78d58b25510fc166214b56dbaa.exe 95 PID 4624 wrote to memory of 3524 4624 3852ed3843fd500abf880ec525bf190281d80b78d58b25510fc166214b56dbaa.exe 95 PID 4624 wrote to memory of 3524 4624 3852ed3843fd500abf880ec525bf190281d80b78d58b25510fc166214b56dbaa.exe 95 PID 4624 wrote to memory of 3524 4624 3852ed3843fd500abf880ec525bf190281d80b78d58b25510fc166214b56dbaa.exe 95 PID 4624 wrote to memory of 3524 4624 3852ed3843fd500abf880ec525bf190281d80b78d58b25510fc166214b56dbaa.exe 95 PID 4624 wrote to memory of 3524 4624 3852ed3843fd500abf880ec525bf190281d80b78d58b25510fc166214b56dbaa.exe 95 PID 4624 wrote to memory of 3524 4624 3852ed3843fd500abf880ec525bf190281d80b78d58b25510fc166214b56dbaa.exe 95 PID 4624 wrote to memory of 3524 4624 3852ed3843fd500abf880ec525bf190281d80b78d58b25510fc166214b56dbaa.exe 95
Processes
-
C:\Users\Admin\AppData\Local\Temp\3852ed3843fd500abf880ec525bf190281d80b78d58b25510fc166214b56dbaa.exe"C:\Users\Admin\AppData\Local\Temp\3852ed3843fd500abf880ec525bf190281d80b78d58b25510fc166214b56dbaa.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:4624 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:2800
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:3524
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4624 -s 2962⤵
- Program crash
PID:4392
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 460 -p 4624 -ip 46241⤵PID:940