Analysis
-
max time kernel
118s -
max time network
125s -
platform
windows7_x64 -
resource
win7-20230831-en -
resource tags
arch:x64arch:x86image:win7-20230831-enlocale:en-usos:windows7-x64system -
submitted
12-10-2023 07:57
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
351a9e2df10af151c085ce665addefc16ddb6586eb6973389c898a4961ac354d.exe
Resource
win7-20230831-en
windows7-x64
4 signatures
150 seconds
General
-
Target
351a9e2df10af151c085ce665addefc16ddb6586eb6973389c898a4961ac354d.exe
-
Size
386KB
-
MD5
b73e5d6ddd728bcd4d212715a71982fb
-
SHA1
bf201ef4eff157be32ec313d686e06caf0ad8d3d
-
SHA256
351a9e2df10af151c085ce665addefc16ddb6586eb6973389c898a4961ac354d
-
SHA512
e705b76067b1c4415d72a5218d89d314cb9383c456357d4d6d6a374f8171a6bdc438c0de5ed07037dade3a097b87356d7f03aaeee55f5f689d76af93a16660e7
-
SSDEEP
6144:kOBa2/KMiCQy4bwSjQzL9ois436xMhAOyb76RtSLaiH3zCuhH5VQkGs:kd2SMiu4Ms436xMh8butiC6H/QT
Malware Config
Signatures
-
Detect Mystic stealer payload 8 IoCs
resource yara_rule behavioral1/memory/3044-9-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/3044-13-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/3044-11-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/3044-15-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/3044-8-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/3044-17-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/3044-16-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/3044-6-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 3028 set thread context of 3044 3028 351a9e2df10af151c085ce665addefc16ddb6586eb6973389c898a4961ac354d.exe 29 -
Suspicious use of WriteProcessMemory 14 IoCs
description pid Process procid_target PID 3028 wrote to memory of 3044 3028 351a9e2df10af151c085ce665addefc16ddb6586eb6973389c898a4961ac354d.exe 29 PID 3028 wrote to memory of 3044 3028 351a9e2df10af151c085ce665addefc16ddb6586eb6973389c898a4961ac354d.exe 29 PID 3028 wrote to memory of 3044 3028 351a9e2df10af151c085ce665addefc16ddb6586eb6973389c898a4961ac354d.exe 29 PID 3028 wrote to memory of 3044 3028 351a9e2df10af151c085ce665addefc16ddb6586eb6973389c898a4961ac354d.exe 29 PID 3028 wrote to memory of 3044 3028 351a9e2df10af151c085ce665addefc16ddb6586eb6973389c898a4961ac354d.exe 29 PID 3028 wrote to memory of 3044 3028 351a9e2df10af151c085ce665addefc16ddb6586eb6973389c898a4961ac354d.exe 29 PID 3028 wrote to memory of 3044 3028 351a9e2df10af151c085ce665addefc16ddb6586eb6973389c898a4961ac354d.exe 29 PID 3028 wrote to memory of 3044 3028 351a9e2df10af151c085ce665addefc16ddb6586eb6973389c898a4961ac354d.exe 29 PID 3028 wrote to memory of 3044 3028 351a9e2df10af151c085ce665addefc16ddb6586eb6973389c898a4961ac354d.exe 29 PID 3028 wrote to memory of 3044 3028 351a9e2df10af151c085ce665addefc16ddb6586eb6973389c898a4961ac354d.exe 29 PID 3028 wrote to memory of 3044 3028 351a9e2df10af151c085ce665addefc16ddb6586eb6973389c898a4961ac354d.exe 29 PID 3028 wrote to memory of 3044 3028 351a9e2df10af151c085ce665addefc16ddb6586eb6973389c898a4961ac354d.exe 29 PID 3028 wrote to memory of 3044 3028 351a9e2df10af151c085ce665addefc16ddb6586eb6973389c898a4961ac354d.exe 29 PID 3028 wrote to memory of 3044 3028 351a9e2df10af151c085ce665addefc16ddb6586eb6973389c898a4961ac354d.exe 29
Processes
-
C:\Users\Admin\AppData\Local\Temp\351a9e2df10af151c085ce665addefc16ddb6586eb6973389c898a4961ac354d.exe"C:\Users\Admin\AppData\Local\Temp\351a9e2df10af151c085ce665addefc16ddb6586eb6973389c898a4961ac354d.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:3028 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:3044
-