Analysis
-
max time kernel
153s -
max time network
154s -
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, 03:40
Static task
static1
Behavioral task
behavioral1
Sample
54cca46adda2d261c5e3586cfb8f3bc547da46add6d924ada554fd5d9ddb6c15.exe
Resource
win7-20230831-en
3 signatures
150 seconds
General
-
Target
54cca46adda2d261c5e3586cfb8f3bc547da46add6d924ada554fd5d9ddb6c15.exe
-
Size
365KB
-
MD5
a0448f673e7a2eb3882fae3135a8371d
-
SHA1
5771f62bb64ed8c627c86f8cdde84ad1abcac440
-
SHA256
54cca46adda2d261c5e3586cfb8f3bc547da46add6d924ada554fd5d9ddb6c15
-
SHA512
498d2b3b37928539de75db0167434dc62498d8a8644af47f8aaefbb3f8ce2bc2af21798a90857550969793d3ed4c32ad32853d0c4e26ac260bd4865a9073c8d1
-
SSDEEP
6144:2a5frpxdonyq4zaG2u5AOfeKQKAhj7I4HdwvBL7Dquqp:28rp0/9u5JeJKAhj6quqp
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 4060 set thread context of 1496 4060 54cca46adda2d261c5e3586cfb8f3bc547da46add6d924ada554fd5d9ddb6c15.exe 88 -
Program crash 1 IoCs
pid pid_target Process procid_target 1712 4060 WerFault.exe 85 -
Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 4060 wrote to memory of 1496 4060 54cca46adda2d261c5e3586cfb8f3bc547da46add6d924ada554fd5d9ddb6c15.exe 88 PID 4060 wrote to memory of 1496 4060 54cca46adda2d261c5e3586cfb8f3bc547da46add6d924ada554fd5d9ddb6c15.exe 88 PID 4060 wrote to memory of 1496 4060 54cca46adda2d261c5e3586cfb8f3bc547da46add6d924ada554fd5d9ddb6c15.exe 88 PID 4060 wrote to memory of 1496 4060 54cca46adda2d261c5e3586cfb8f3bc547da46add6d924ada554fd5d9ddb6c15.exe 88 PID 4060 wrote to memory of 1496 4060 54cca46adda2d261c5e3586cfb8f3bc547da46add6d924ada554fd5d9ddb6c15.exe 88 PID 4060 wrote to memory of 1496 4060 54cca46adda2d261c5e3586cfb8f3bc547da46add6d924ada554fd5d9ddb6c15.exe 88 PID 4060 wrote to memory of 1496 4060 54cca46adda2d261c5e3586cfb8f3bc547da46add6d924ada554fd5d9ddb6c15.exe 88 PID 4060 wrote to memory of 1496 4060 54cca46adda2d261c5e3586cfb8f3bc547da46add6d924ada554fd5d9ddb6c15.exe 88 PID 4060 wrote to memory of 1496 4060 54cca46adda2d261c5e3586cfb8f3bc547da46add6d924ada554fd5d9ddb6c15.exe 88 PID 4060 wrote to memory of 1496 4060 54cca46adda2d261c5e3586cfb8f3bc547da46add6d924ada554fd5d9ddb6c15.exe 88
Processes
-
C:\Users\Admin\AppData\Local\Temp\54cca46adda2d261c5e3586cfb8f3bc547da46add6d924ada554fd5d9ddb6c15.exe"C:\Users\Admin\AppData\Local\Temp\54cca46adda2d261c5e3586cfb8f3bc547da46add6d924ada554fd5d9ddb6c15.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:4060 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:1496
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4060 -s 2762⤵
- Program crash
PID:1712
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 460 -p 4060 -ip 40601⤵PID:4312