Analysis
-
max time kernel
166s -
max time network
177s -
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:08
Static task
static1
Behavioral task
behavioral1
Sample
2585265cd021683f9b0d041e618d5b920de34aa0161eb04f9ad632877d6541d7.exe
Resource
win7-20230831-en
3 signatures
150 seconds
General
-
Target
2585265cd021683f9b0d041e618d5b920de34aa0161eb04f9ad632877d6541d7.exe
-
Size
365KB
-
MD5
4a0f1fa3d4dc02a898864d0060d71d08
-
SHA1
912b3dc6cb81d148341f58acf83d5d3be4d261ed
-
SHA256
2585265cd021683f9b0d041e618d5b920de34aa0161eb04f9ad632877d6541d7
-
SHA512
0df63bd9715a9d678eff0a3822d14adc69a543a7e7e7a87a438dd3f8a9e5a2a2dcaadd6260a495ef2dbfba5a0750bda42468570d28e3f9cc60b1c186182b6426
-
SSDEEP
6144:fn5frpxdonyq4zaG2u5AO8eKECRR9TubDvlwE5YYG5zuDquqp:fxrp0/9u5yeQRzgvecYuDquqp
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 2372 set thread context of 5076 2372 2585265cd021683f9b0d041e618d5b920de34aa0161eb04f9ad632877d6541d7.exe 88 -
Program crash 1 IoCs
pid pid_target Process procid_target 1420 2372 WerFault.exe 85 -
Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 2372 wrote to memory of 5076 2372 2585265cd021683f9b0d041e618d5b920de34aa0161eb04f9ad632877d6541d7.exe 88 PID 2372 wrote to memory of 5076 2372 2585265cd021683f9b0d041e618d5b920de34aa0161eb04f9ad632877d6541d7.exe 88 PID 2372 wrote to memory of 5076 2372 2585265cd021683f9b0d041e618d5b920de34aa0161eb04f9ad632877d6541d7.exe 88 PID 2372 wrote to memory of 5076 2372 2585265cd021683f9b0d041e618d5b920de34aa0161eb04f9ad632877d6541d7.exe 88 PID 2372 wrote to memory of 5076 2372 2585265cd021683f9b0d041e618d5b920de34aa0161eb04f9ad632877d6541d7.exe 88 PID 2372 wrote to memory of 5076 2372 2585265cd021683f9b0d041e618d5b920de34aa0161eb04f9ad632877d6541d7.exe 88 PID 2372 wrote to memory of 5076 2372 2585265cd021683f9b0d041e618d5b920de34aa0161eb04f9ad632877d6541d7.exe 88 PID 2372 wrote to memory of 5076 2372 2585265cd021683f9b0d041e618d5b920de34aa0161eb04f9ad632877d6541d7.exe 88 PID 2372 wrote to memory of 5076 2372 2585265cd021683f9b0d041e618d5b920de34aa0161eb04f9ad632877d6541d7.exe 88 PID 2372 wrote to memory of 5076 2372 2585265cd021683f9b0d041e618d5b920de34aa0161eb04f9ad632877d6541d7.exe 88
Processes
-
C:\Users\Admin\AppData\Local\Temp\2585265cd021683f9b0d041e618d5b920de34aa0161eb04f9ad632877d6541d7.exe"C:\Users\Admin\AppData\Local\Temp\2585265cd021683f9b0d041e618d5b920de34aa0161eb04f9ad632877d6541d7.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2372 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:5076
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2372 -s 2722⤵
- Program crash
PID:1420
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 472 -p 2372 -ip 23721⤵PID:2728