Analysis
-
max time kernel
140s -
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, 01:37
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
5a1a02d278ac73bbc7b471e75318d0dff20e85b99c03b8312abc52fce0f6aa1d.exe
Resource
win7-20230831-en
3 signatures
150 seconds
General
-
Target
5a1a02d278ac73bbc7b471e75318d0dff20e85b99c03b8312abc52fce0f6aa1d.exe
-
Size
364KB
-
MD5
b3cc16b5685073e255cf46c2c319e261
-
SHA1
a007ced8d28a812782a4ffb3a2c69e20951f3be2
-
SHA256
5a1a02d278ac73bbc7b471e75318d0dff20e85b99c03b8312abc52fce0f6aa1d
-
SHA512
cb8012eacdde0356cf7d6af3de46282b60034ed63f7696b6f5fad2a0f9181ae85d1d758747bb8cbe0c6c0e9207f5e3fec791df2c0f0d1496834bfd45ef3bb510
-
SSDEEP
6144:n246fuYXChoQTjlFgLuCY1dRuAOvNL6zHcsl02URzdnv0w8y0:nDYzXChdTbv1buLLGPl02URzp0w8y
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 348 set thread context of 1264 348 5a1a02d278ac73bbc7b471e75318d0dff20e85b99c03b8312abc52fce0f6aa1d.exe 88 -
Program crash 1 IoCs
pid pid_target Process procid_target 4940 348 WerFault.exe 81 -
Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 348 wrote to memory of 1264 348 5a1a02d278ac73bbc7b471e75318d0dff20e85b99c03b8312abc52fce0f6aa1d.exe 88 PID 348 wrote to memory of 1264 348 5a1a02d278ac73bbc7b471e75318d0dff20e85b99c03b8312abc52fce0f6aa1d.exe 88 PID 348 wrote to memory of 1264 348 5a1a02d278ac73bbc7b471e75318d0dff20e85b99c03b8312abc52fce0f6aa1d.exe 88 PID 348 wrote to memory of 1264 348 5a1a02d278ac73bbc7b471e75318d0dff20e85b99c03b8312abc52fce0f6aa1d.exe 88 PID 348 wrote to memory of 1264 348 5a1a02d278ac73bbc7b471e75318d0dff20e85b99c03b8312abc52fce0f6aa1d.exe 88 PID 348 wrote to memory of 1264 348 5a1a02d278ac73bbc7b471e75318d0dff20e85b99c03b8312abc52fce0f6aa1d.exe 88 PID 348 wrote to memory of 1264 348 5a1a02d278ac73bbc7b471e75318d0dff20e85b99c03b8312abc52fce0f6aa1d.exe 88 PID 348 wrote to memory of 1264 348 5a1a02d278ac73bbc7b471e75318d0dff20e85b99c03b8312abc52fce0f6aa1d.exe 88 PID 348 wrote to memory of 1264 348 5a1a02d278ac73bbc7b471e75318d0dff20e85b99c03b8312abc52fce0f6aa1d.exe 88 PID 348 wrote to memory of 1264 348 5a1a02d278ac73bbc7b471e75318d0dff20e85b99c03b8312abc52fce0f6aa1d.exe 88
Processes
-
C:\Users\Admin\AppData\Local\Temp\5a1a02d278ac73bbc7b471e75318d0dff20e85b99c03b8312abc52fce0f6aa1d.exe"C:\Users\Admin\AppData\Local\Temp\5a1a02d278ac73bbc7b471e75318d0dff20e85b99c03b8312abc52fce0f6aa1d.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:348 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:1264
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 348 -s 2522⤵
- Program crash
PID:4940
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 480 -p 348 -ip 3481⤵PID:3856