Analysis
-
max time kernel
161s -
max time network
174s -
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, 02:30
Static task
static1
Behavioral task
behavioral1
Sample
7493ca2b51cbbcfaaa6ca5a10b8b7aeae467903da00d3fbaf620a8b2aa9ab3ce.exe
Resource
win7-20230831-en
3 signatures
150 seconds
General
-
Target
7493ca2b51cbbcfaaa6ca5a10b8b7aeae467903da00d3fbaf620a8b2aa9ab3ce.exe
-
Size
365KB
-
MD5
a401ce0f4173138b2bfb420c4a66902d
-
SHA1
3d6bf8e8114ade7bef81ef41c6d1650687b730db
-
SHA256
7493ca2b51cbbcfaaa6ca5a10b8b7aeae467903da00d3fbaf620a8b2aa9ab3ce
-
SHA512
4a24309ec6a1f370c5ba553cb5b483c1ac63dad05563b4fcdb845750a2b0dbcd78538c3ae94da7e94c587ea0fcce40450f1f4be79af40adca5e0b3bb8f63163c
-
SSDEEP
6144:eK5frpxdonyq4zaG2u5AOHeK5LmmyFeimnIzkpnFEH1IPZPgaMquqp:esrp0/9u5Be9NNmIzkl6eMquqp
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 3784 set thread context of 3380 3784 7493ca2b51cbbcfaaa6ca5a10b8b7aeae467903da00d3fbaf620a8b2aa9ab3ce.exe 91 -
Program crash 1 IoCs
pid pid_target Process procid_target 4748 3784 WerFault.exe 86 -
Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 3784 wrote to memory of 3380 3784 7493ca2b51cbbcfaaa6ca5a10b8b7aeae467903da00d3fbaf620a8b2aa9ab3ce.exe 91 PID 3784 wrote to memory of 3380 3784 7493ca2b51cbbcfaaa6ca5a10b8b7aeae467903da00d3fbaf620a8b2aa9ab3ce.exe 91 PID 3784 wrote to memory of 3380 3784 7493ca2b51cbbcfaaa6ca5a10b8b7aeae467903da00d3fbaf620a8b2aa9ab3ce.exe 91 PID 3784 wrote to memory of 3380 3784 7493ca2b51cbbcfaaa6ca5a10b8b7aeae467903da00d3fbaf620a8b2aa9ab3ce.exe 91 PID 3784 wrote to memory of 3380 3784 7493ca2b51cbbcfaaa6ca5a10b8b7aeae467903da00d3fbaf620a8b2aa9ab3ce.exe 91 PID 3784 wrote to memory of 3380 3784 7493ca2b51cbbcfaaa6ca5a10b8b7aeae467903da00d3fbaf620a8b2aa9ab3ce.exe 91 PID 3784 wrote to memory of 3380 3784 7493ca2b51cbbcfaaa6ca5a10b8b7aeae467903da00d3fbaf620a8b2aa9ab3ce.exe 91 PID 3784 wrote to memory of 3380 3784 7493ca2b51cbbcfaaa6ca5a10b8b7aeae467903da00d3fbaf620a8b2aa9ab3ce.exe 91 PID 3784 wrote to memory of 3380 3784 7493ca2b51cbbcfaaa6ca5a10b8b7aeae467903da00d3fbaf620a8b2aa9ab3ce.exe 91 PID 3784 wrote to memory of 3380 3784 7493ca2b51cbbcfaaa6ca5a10b8b7aeae467903da00d3fbaf620a8b2aa9ab3ce.exe 91
Processes
-
C:\Users\Admin\AppData\Local\Temp\7493ca2b51cbbcfaaa6ca5a10b8b7aeae467903da00d3fbaf620a8b2aa9ab3ce.exe"C:\Users\Admin\AppData\Local\Temp\7493ca2b51cbbcfaaa6ca5a10b8b7aeae467903da00d3fbaf620a8b2aa9ab3ce.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:3784 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:3380
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3784 -s 2722⤵
- Program crash
PID:4748
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 476 -p 3784 -ip 37841⤵PID:440