Analysis
-
max time kernel
118s -
max time network
140s -
platform
windows7_x64 -
resource
win7-20230831-en -
resource tags
arch:x64arch:x86image:win7-20230831-enlocale:en-usos:windows7-x64system -
submitted
12/10/2023, 07:55
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
8b07dadc2191178420f16d0379056f8e32b7f1a79485ed915aea3a055df47d8b.exe
Resource
win7-20230831-en
4 signatures
150 seconds
General
-
Target
8b07dadc2191178420f16d0379056f8e32b7f1a79485ed915aea3a055df47d8b.exe
-
Size
342KB
-
MD5
0b3df3a68c770085d4c6475f48435f85
-
SHA1
7c26eb54046265d77126def827b5daba99ad3f96
-
SHA256
8b07dadc2191178420f16d0379056f8e32b7f1a79485ed915aea3a055df47d8b
-
SHA512
8551a6af159b0919754d9cb8a7200f6b5598a724ff8252254dcc9c9f77c61f2b702a3ac6d5a6571d537f5734627471144d4b50c0ee54ed3457f6f04262b52abe
-
SSDEEP
6144:Cd/iKL/yfYb5B+BO99c0s0ZVtAO8g362ymmPn9jcZErsOiG7xMMZCE9:g///yfYb5BIQZVtOffPn1eOiCF9
Malware Config
Signatures
-
Detect Mystic stealer payload 8 IoCs
resource yara_rule behavioral1/memory/2900-5-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2900-6-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2900-7-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2900-9-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2900-11-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2900-13-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2900-14-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2900-15-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2972 set thread context of 2900 2972 8b07dadc2191178420f16d0379056f8e32b7f1a79485ed915aea3a055df47d8b.exe 29 -
Suspicious use of WriteProcessMemory 14 IoCs
description pid Process procid_target PID 2972 wrote to memory of 2900 2972 8b07dadc2191178420f16d0379056f8e32b7f1a79485ed915aea3a055df47d8b.exe 29 PID 2972 wrote to memory of 2900 2972 8b07dadc2191178420f16d0379056f8e32b7f1a79485ed915aea3a055df47d8b.exe 29 PID 2972 wrote to memory of 2900 2972 8b07dadc2191178420f16d0379056f8e32b7f1a79485ed915aea3a055df47d8b.exe 29 PID 2972 wrote to memory of 2900 2972 8b07dadc2191178420f16d0379056f8e32b7f1a79485ed915aea3a055df47d8b.exe 29 PID 2972 wrote to memory of 2900 2972 8b07dadc2191178420f16d0379056f8e32b7f1a79485ed915aea3a055df47d8b.exe 29 PID 2972 wrote to memory of 2900 2972 8b07dadc2191178420f16d0379056f8e32b7f1a79485ed915aea3a055df47d8b.exe 29 PID 2972 wrote to memory of 2900 2972 8b07dadc2191178420f16d0379056f8e32b7f1a79485ed915aea3a055df47d8b.exe 29 PID 2972 wrote to memory of 2900 2972 8b07dadc2191178420f16d0379056f8e32b7f1a79485ed915aea3a055df47d8b.exe 29 PID 2972 wrote to memory of 2900 2972 8b07dadc2191178420f16d0379056f8e32b7f1a79485ed915aea3a055df47d8b.exe 29 PID 2972 wrote to memory of 2900 2972 8b07dadc2191178420f16d0379056f8e32b7f1a79485ed915aea3a055df47d8b.exe 29 PID 2972 wrote to memory of 2900 2972 8b07dadc2191178420f16d0379056f8e32b7f1a79485ed915aea3a055df47d8b.exe 29 PID 2972 wrote to memory of 2900 2972 8b07dadc2191178420f16d0379056f8e32b7f1a79485ed915aea3a055df47d8b.exe 29 PID 2972 wrote to memory of 2900 2972 8b07dadc2191178420f16d0379056f8e32b7f1a79485ed915aea3a055df47d8b.exe 29 PID 2972 wrote to memory of 2900 2972 8b07dadc2191178420f16d0379056f8e32b7f1a79485ed915aea3a055df47d8b.exe 29
Processes
-
C:\Users\Admin\AppData\Local\Temp\8b07dadc2191178420f16d0379056f8e32b7f1a79485ed915aea3a055df47d8b.exe"C:\Users\Admin\AppData\Local\Temp\8b07dadc2191178420f16d0379056f8e32b7f1a79485ed915aea3a055df47d8b.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2972 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:2900
-