Analysis
-
max time kernel
119s -
max time network
123s -
platform
windows7_x64 -
resource
win7-20230831-en -
resource tags
arch:x64arch:x86image:win7-20230831-enlocale:en-usos:windows7-x64system -
submitted
12/10/2023, 22:15
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
e7e385b0761449320a03f0d6eb5880e710a3b5367bba3ba1cbff7b89636242af.exe
Resource
win7-20230831-en
5 signatures
150 seconds
General
-
Target
e7e385b0761449320a03f0d6eb5880e710a3b5367bba3ba1cbff7b89636242af.exe
-
Size
359KB
-
MD5
a3efd42c7f0b8e98df84103f3a3e0fd8
-
SHA1
8b7d5de25e7a5dd8287c36464a839f7bf2796ba9
-
SHA256
e7e385b0761449320a03f0d6eb5880e710a3b5367bba3ba1cbff7b89636242af
-
SHA512
7e59554e8d3654019a8347db62e4b4ed902ed19690c486f4c3b0cfd8a02fe95927ff22271c3b50cc7975735363494dc1481c26443f5a43dc829e5a94a914746e
-
SSDEEP
6144:g13aNJ/tWwk8XhkeP+jUPwVAOGlRBBZVMnE/EF2D+WWqW778v1WGPnL/98Ey:g1q//tWpJRgdBZi5qW3kHzF8Ey
Malware Config
Signatures
-
Detect Mystic stealer payload 6 IoCs
resource yara_rule behavioral1/memory/2396-3-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2396-4-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2396-5-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2396-7-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2396-9-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2396-11-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2440 set thread context of 2396 2440 e7e385b0761449320a03f0d6eb5880e710a3b5367bba3ba1cbff7b89636242af.exe 30 -
Program crash 1 IoCs
pid pid_target Process procid_target 2852 2396 WerFault.exe 30 -
Suspicious use of WriteProcessMemory 28 IoCs
description pid Process procid_target PID 2440 wrote to memory of 2604 2440 e7e385b0761449320a03f0d6eb5880e710a3b5367bba3ba1cbff7b89636242af.exe 29 PID 2440 wrote to memory of 2604 2440 e7e385b0761449320a03f0d6eb5880e710a3b5367bba3ba1cbff7b89636242af.exe 29 PID 2440 wrote to memory of 2604 2440 e7e385b0761449320a03f0d6eb5880e710a3b5367bba3ba1cbff7b89636242af.exe 29 PID 2440 wrote to memory of 2604 2440 e7e385b0761449320a03f0d6eb5880e710a3b5367bba3ba1cbff7b89636242af.exe 29 PID 2440 wrote to memory of 2604 2440 e7e385b0761449320a03f0d6eb5880e710a3b5367bba3ba1cbff7b89636242af.exe 29 PID 2440 wrote to memory of 2604 2440 e7e385b0761449320a03f0d6eb5880e710a3b5367bba3ba1cbff7b89636242af.exe 29 PID 2440 wrote to memory of 2604 2440 e7e385b0761449320a03f0d6eb5880e710a3b5367bba3ba1cbff7b89636242af.exe 29 PID 2440 wrote to memory of 2396 2440 e7e385b0761449320a03f0d6eb5880e710a3b5367bba3ba1cbff7b89636242af.exe 30 PID 2440 wrote to memory of 2396 2440 e7e385b0761449320a03f0d6eb5880e710a3b5367bba3ba1cbff7b89636242af.exe 30 PID 2440 wrote to memory of 2396 2440 e7e385b0761449320a03f0d6eb5880e710a3b5367bba3ba1cbff7b89636242af.exe 30 PID 2440 wrote to memory of 2396 2440 e7e385b0761449320a03f0d6eb5880e710a3b5367bba3ba1cbff7b89636242af.exe 30 PID 2440 wrote to memory of 2396 2440 e7e385b0761449320a03f0d6eb5880e710a3b5367bba3ba1cbff7b89636242af.exe 30 PID 2440 wrote to memory of 2396 2440 e7e385b0761449320a03f0d6eb5880e710a3b5367bba3ba1cbff7b89636242af.exe 30 PID 2440 wrote to memory of 2396 2440 e7e385b0761449320a03f0d6eb5880e710a3b5367bba3ba1cbff7b89636242af.exe 30 PID 2440 wrote to memory of 2396 2440 e7e385b0761449320a03f0d6eb5880e710a3b5367bba3ba1cbff7b89636242af.exe 30 PID 2440 wrote to memory of 2396 2440 e7e385b0761449320a03f0d6eb5880e710a3b5367bba3ba1cbff7b89636242af.exe 30 PID 2440 wrote to memory of 2396 2440 e7e385b0761449320a03f0d6eb5880e710a3b5367bba3ba1cbff7b89636242af.exe 30 PID 2440 wrote to memory of 2396 2440 e7e385b0761449320a03f0d6eb5880e710a3b5367bba3ba1cbff7b89636242af.exe 30 PID 2440 wrote to memory of 2396 2440 e7e385b0761449320a03f0d6eb5880e710a3b5367bba3ba1cbff7b89636242af.exe 30 PID 2440 wrote to memory of 2396 2440 e7e385b0761449320a03f0d6eb5880e710a3b5367bba3ba1cbff7b89636242af.exe 30 PID 2440 wrote to memory of 2396 2440 e7e385b0761449320a03f0d6eb5880e710a3b5367bba3ba1cbff7b89636242af.exe 30 PID 2396 wrote to memory of 2852 2396 AppLaunch.exe 31 PID 2396 wrote to memory of 2852 2396 AppLaunch.exe 31 PID 2396 wrote to memory of 2852 2396 AppLaunch.exe 31 PID 2396 wrote to memory of 2852 2396 AppLaunch.exe 31 PID 2396 wrote to memory of 2852 2396 AppLaunch.exe 31 PID 2396 wrote to memory of 2852 2396 AppLaunch.exe 31 PID 2396 wrote to memory of 2852 2396 AppLaunch.exe 31
Processes
-
C:\Users\Admin\AppData\Local\Temp\e7e385b0761449320a03f0d6eb5880e710a3b5367bba3ba1cbff7b89636242af.exe"C:\Users\Admin\AppData\Local\Temp\e7e385b0761449320a03f0d6eb5880e710a3b5367bba3ba1cbff7b89636242af.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2440 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:2604
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵
- Suspicious use of WriteProcessMemory
PID:2396 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2396 -s 1963⤵
- Program crash
PID:2852
-
-