Analysis
-
max time kernel
120s -
max time network
128s -
platform
windows7_x64 -
resource
win7-20230831-en -
resource tags
arch:x64arch:x86image:win7-20230831-enlocale:en-usos:windows7-x64system -
submitted
14-10-2023 03:35
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
5239eee0e6f62d978e7362bb8ca5f864ae34cbdeef47d3ddc67d5aba71afa5c5.exe
Resource
win7-20230831-en
windows7-x64
4 signatures
150 seconds
General
-
Target
5239eee0e6f62d978e7362bb8ca5f864ae34cbdeef47d3ddc67d5aba71afa5c5.exe
-
Size
342KB
-
MD5
3bec2a4893d6c249bd11e39bdf34b6b4
-
SHA1
eed6f8cea90185e187f7913aaeadc7a109f7943f
-
SHA256
5239eee0e6f62d978e7362bb8ca5f864ae34cbdeef47d3ddc67d5aba71afa5c5
-
SHA512
ed45a4228ff26e7631b55cbf9f5526eeb646463ac134f2e0b573912cec55d048dd17c761371c1c6e1a3a592cf8b3f84c22b94cb4e4b617d3a32c1ae72c2606d3
-
SSDEEP
6144:qCkiKL/yfYb5B+BO99c0s0ZVtAOigJlRiviX5XJ6nMJ2eCUE9:7k//yfYb5BIQZVts1ipsi2eCB9
Malware Config
Signatures
-
Detect Mystic stealer payload 8 IoCs
resource yara_rule behavioral1/memory/2104-5-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2104-6-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2104-7-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2104-9-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2104-11-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2104-13-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2104-14-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2104-15-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 1976 set thread context of 2104 1976 5239eee0e6f62d978e7362bb8ca5f864ae34cbdeef47d3ddc67d5aba71afa5c5.exe 29 -
Suspicious use of WriteProcessMemory 14 IoCs
description pid Process procid_target PID 1976 wrote to memory of 2104 1976 5239eee0e6f62d978e7362bb8ca5f864ae34cbdeef47d3ddc67d5aba71afa5c5.exe 29 PID 1976 wrote to memory of 2104 1976 5239eee0e6f62d978e7362bb8ca5f864ae34cbdeef47d3ddc67d5aba71afa5c5.exe 29 PID 1976 wrote to memory of 2104 1976 5239eee0e6f62d978e7362bb8ca5f864ae34cbdeef47d3ddc67d5aba71afa5c5.exe 29 PID 1976 wrote to memory of 2104 1976 5239eee0e6f62d978e7362bb8ca5f864ae34cbdeef47d3ddc67d5aba71afa5c5.exe 29 PID 1976 wrote to memory of 2104 1976 5239eee0e6f62d978e7362bb8ca5f864ae34cbdeef47d3ddc67d5aba71afa5c5.exe 29 PID 1976 wrote to memory of 2104 1976 5239eee0e6f62d978e7362bb8ca5f864ae34cbdeef47d3ddc67d5aba71afa5c5.exe 29 PID 1976 wrote to memory of 2104 1976 5239eee0e6f62d978e7362bb8ca5f864ae34cbdeef47d3ddc67d5aba71afa5c5.exe 29 PID 1976 wrote to memory of 2104 1976 5239eee0e6f62d978e7362bb8ca5f864ae34cbdeef47d3ddc67d5aba71afa5c5.exe 29 PID 1976 wrote to memory of 2104 1976 5239eee0e6f62d978e7362bb8ca5f864ae34cbdeef47d3ddc67d5aba71afa5c5.exe 29 PID 1976 wrote to memory of 2104 1976 5239eee0e6f62d978e7362bb8ca5f864ae34cbdeef47d3ddc67d5aba71afa5c5.exe 29 PID 1976 wrote to memory of 2104 1976 5239eee0e6f62d978e7362bb8ca5f864ae34cbdeef47d3ddc67d5aba71afa5c5.exe 29 PID 1976 wrote to memory of 2104 1976 5239eee0e6f62d978e7362bb8ca5f864ae34cbdeef47d3ddc67d5aba71afa5c5.exe 29 PID 1976 wrote to memory of 2104 1976 5239eee0e6f62d978e7362bb8ca5f864ae34cbdeef47d3ddc67d5aba71afa5c5.exe 29 PID 1976 wrote to memory of 2104 1976 5239eee0e6f62d978e7362bb8ca5f864ae34cbdeef47d3ddc67d5aba71afa5c5.exe 29
Processes
-
C:\Users\Admin\AppData\Local\Temp\5239eee0e6f62d978e7362bb8ca5f864ae34cbdeef47d3ddc67d5aba71afa5c5.exe"C:\Users\Admin\AppData\Local\Temp\5239eee0e6f62d978e7362bb8ca5f864ae34cbdeef47d3ddc67d5aba71afa5c5.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:1976 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:2104
-