Analysis
-
max time kernel
120s -
max time network
126s -
platform
windows7_x64 -
resource
win7-20230831-en -
resource tags
arch:x64arch:x86image:win7-20230831-enlocale:en-usos:windows7-x64system -
submitted
14-10-2023 02:43
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
d3de8fc7e2e1bb766bb064e49681f4ecaac0e8c110111dcd324c16e3d69461a5.exe
Resource
win7-20230831-en
windows7-x64
5 signatures
150 seconds
General
-
Target
d3de8fc7e2e1bb766bb064e49681f4ecaac0e8c110111dcd324c16e3d69461a5.exe
-
Size
342KB
-
MD5
d3dbf76c5158bd95a05463f7e01bd983
-
SHA1
e32c2c57d818f42d733dbd573f405db3dd0b40c2
-
SHA256
d3de8fc7e2e1bb766bb064e49681f4ecaac0e8c110111dcd324c16e3d69461a5
-
SHA512
bab60a1d860c078aebb4322819c7528832433b908cd8fb86f5e0c1febbafc79483551361f599f03fa00e7fe4fe93c47f44556cbd41ef6bd69a5730f7daccaeec
-
SSDEEP
6144:f/4iKL/yfYb5B+BO99c0s0ZVtAOMgdn8+pdOPD5js5vH5j3gqE9:n4//yfYb5BIQZVteyoZs5vH5bQ9
Malware Config
Signatures
-
Detect Mystic stealer payload 6 IoCs
resource yara_rule behavioral1/memory/2584-7-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2584-5-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2584-4-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2584-3-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2584-9-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2584-11-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 1564 set thread context of 2584 1564 d3de8fc7e2e1bb766bb064e49681f4ecaac0e8c110111dcd324c16e3d69461a5.exe 30 -
Program crash 1 IoCs
pid pid_target Process procid_target 2592 2584 WerFault.exe 30 -
Suspicious use of WriteProcessMemory 28 IoCs
description pid Process procid_target PID 1564 wrote to memory of 1728 1564 d3de8fc7e2e1bb766bb064e49681f4ecaac0e8c110111dcd324c16e3d69461a5.exe 29 PID 1564 wrote to memory of 1728 1564 d3de8fc7e2e1bb766bb064e49681f4ecaac0e8c110111dcd324c16e3d69461a5.exe 29 PID 1564 wrote to memory of 1728 1564 d3de8fc7e2e1bb766bb064e49681f4ecaac0e8c110111dcd324c16e3d69461a5.exe 29 PID 1564 wrote to memory of 1728 1564 d3de8fc7e2e1bb766bb064e49681f4ecaac0e8c110111dcd324c16e3d69461a5.exe 29 PID 1564 wrote to memory of 1728 1564 d3de8fc7e2e1bb766bb064e49681f4ecaac0e8c110111dcd324c16e3d69461a5.exe 29 PID 1564 wrote to memory of 1728 1564 d3de8fc7e2e1bb766bb064e49681f4ecaac0e8c110111dcd324c16e3d69461a5.exe 29 PID 1564 wrote to memory of 1728 1564 d3de8fc7e2e1bb766bb064e49681f4ecaac0e8c110111dcd324c16e3d69461a5.exe 29 PID 1564 wrote to memory of 2584 1564 d3de8fc7e2e1bb766bb064e49681f4ecaac0e8c110111dcd324c16e3d69461a5.exe 30 PID 1564 wrote to memory of 2584 1564 d3de8fc7e2e1bb766bb064e49681f4ecaac0e8c110111dcd324c16e3d69461a5.exe 30 PID 1564 wrote to memory of 2584 1564 d3de8fc7e2e1bb766bb064e49681f4ecaac0e8c110111dcd324c16e3d69461a5.exe 30 PID 1564 wrote to memory of 2584 1564 d3de8fc7e2e1bb766bb064e49681f4ecaac0e8c110111dcd324c16e3d69461a5.exe 30 PID 1564 wrote to memory of 2584 1564 d3de8fc7e2e1bb766bb064e49681f4ecaac0e8c110111dcd324c16e3d69461a5.exe 30 PID 1564 wrote to memory of 2584 1564 d3de8fc7e2e1bb766bb064e49681f4ecaac0e8c110111dcd324c16e3d69461a5.exe 30 PID 1564 wrote to memory of 2584 1564 d3de8fc7e2e1bb766bb064e49681f4ecaac0e8c110111dcd324c16e3d69461a5.exe 30 PID 1564 wrote to memory of 2584 1564 d3de8fc7e2e1bb766bb064e49681f4ecaac0e8c110111dcd324c16e3d69461a5.exe 30 PID 1564 wrote to memory of 2584 1564 d3de8fc7e2e1bb766bb064e49681f4ecaac0e8c110111dcd324c16e3d69461a5.exe 30 PID 1564 wrote to memory of 2584 1564 d3de8fc7e2e1bb766bb064e49681f4ecaac0e8c110111dcd324c16e3d69461a5.exe 30 PID 1564 wrote to memory of 2584 1564 d3de8fc7e2e1bb766bb064e49681f4ecaac0e8c110111dcd324c16e3d69461a5.exe 30 PID 1564 wrote to memory of 2584 1564 d3de8fc7e2e1bb766bb064e49681f4ecaac0e8c110111dcd324c16e3d69461a5.exe 30 PID 1564 wrote to memory of 2584 1564 d3de8fc7e2e1bb766bb064e49681f4ecaac0e8c110111dcd324c16e3d69461a5.exe 30 PID 1564 wrote to memory of 2584 1564 d3de8fc7e2e1bb766bb064e49681f4ecaac0e8c110111dcd324c16e3d69461a5.exe 30 PID 2584 wrote to memory of 2592 2584 AppLaunch.exe 31 PID 2584 wrote to memory of 2592 2584 AppLaunch.exe 31 PID 2584 wrote to memory of 2592 2584 AppLaunch.exe 31 PID 2584 wrote to memory of 2592 2584 AppLaunch.exe 31 PID 2584 wrote to memory of 2592 2584 AppLaunch.exe 31 PID 2584 wrote to memory of 2592 2584 AppLaunch.exe 31 PID 2584 wrote to memory of 2592 2584 AppLaunch.exe 31
Processes
-
C:\Users\Admin\AppData\Local\Temp\d3de8fc7e2e1bb766bb064e49681f4ecaac0e8c110111dcd324c16e3d69461a5.exe"C:\Users\Admin\AppData\Local\Temp\d3de8fc7e2e1bb766bb064e49681f4ecaac0e8c110111dcd324c16e3d69461a5.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:1564 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:1728
-
-
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:2584 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2584 -s 1963⤵
- Program crash
PID:2592
-
-