Analysis
-
max time kernel
169s -
max time network
234s -
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, 05:33
Static task
static1
Behavioral task
behavioral1
Sample
9640f7421ebad9f591441d41a16fb910fac047c08faa4e9f8ce809905324ae56.exe
Resource
win7-20230831-en
4 signatures
150 seconds
General
-
Target
9640f7421ebad9f591441d41a16fb910fac047c08faa4e9f8ce809905324ae56.exe
-
Size
700KB
-
MD5
dfb628f39f67509654f6112c851be687
-
SHA1
4c39c7e7d0bf3b02473b38ef6a0cbcdf1ffc816d
-
SHA256
9640f7421ebad9f591441d41a16fb910fac047c08faa4e9f8ce809905324ae56
-
SHA512
711cc8d3b317d1d6fdb81183ac67092ded06dbe172c4e509097a5630945ffef91b78990ec44491ba10d5606c0f1210fa294227c893b0c075386d115660d55ee1
-
SSDEEP
6144:x6vGALXgBEIy8wluzNcq/PVucQpRGelJylH0WfYMvfr:sHXgFysVucQpRdlJmH/fFr
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 4988 set thread context of 1680 4988 9640f7421ebad9f591441d41a16fb910fac047c08faa4e9f8ce809905324ae56.exe 86 -
Program crash 1 IoCs
pid pid_target Process procid_target 1548 4988 WerFault.exe 39 -
Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 4988 wrote to memory of 1680 4988 9640f7421ebad9f591441d41a16fb910fac047c08faa4e9f8ce809905324ae56.exe 86 PID 4988 wrote to memory of 1680 4988 9640f7421ebad9f591441d41a16fb910fac047c08faa4e9f8ce809905324ae56.exe 86 PID 4988 wrote to memory of 1680 4988 9640f7421ebad9f591441d41a16fb910fac047c08faa4e9f8ce809905324ae56.exe 86 PID 4988 wrote to memory of 1680 4988 9640f7421ebad9f591441d41a16fb910fac047c08faa4e9f8ce809905324ae56.exe 86 PID 4988 wrote to memory of 1680 4988 9640f7421ebad9f591441d41a16fb910fac047c08faa4e9f8ce809905324ae56.exe 86 PID 4988 wrote to memory of 1680 4988 9640f7421ebad9f591441d41a16fb910fac047c08faa4e9f8ce809905324ae56.exe 86 PID 4988 wrote to memory of 1680 4988 9640f7421ebad9f591441d41a16fb910fac047c08faa4e9f8ce809905324ae56.exe 86 PID 4988 wrote to memory of 1680 4988 9640f7421ebad9f591441d41a16fb910fac047c08faa4e9f8ce809905324ae56.exe 86 PID 4988 wrote to memory of 1680 4988 9640f7421ebad9f591441d41a16fb910fac047c08faa4e9f8ce809905324ae56.exe 86 PID 4988 wrote to memory of 1680 4988 9640f7421ebad9f591441d41a16fb910fac047c08faa4e9f8ce809905324ae56.exe 86
Processes
-
C:\Users\Admin\AppData\Local\Temp\9640f7421ebad9f591441d41a16fb910fac047c08faa4e9f8ce809905324ae56.exe"C:\Users\Admin\AppData\Local\Temp\9640f7421ebad9f591441d41a16fb910fac047c08faa4e9f8ce809905324ae56.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:4988 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:1680
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4988 -s 1522⤵
- Program crash
PID:1548
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 456 -p 4988 -ip 49881⤵PID:2780