Analysis
-
max time kernel
122s -
max time network
130s -
platform
windows7_x64 -
resource
win7-20230831-en -
resource tags
arch:x64arch:x86image:win7-20230831-enlocale:en-usos:windows7-x64system -
submitted
13/10/2023, 00:16
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
74a884161c80f24623c59c0272e3548bb6c9ed52a7c4a2beff731f44d7f4fac0.exe
Resource
win7-20230831-en
5 signatures
150 seconds
General
-
Target
74a884161c80f24623c59c0272e3548bb6c9ed52a7c4a2beff731f44d7f4fac0.exe
-
Size
359KB
-
MD5
31e25ad8653615790e9414f89ab5ce8b
-
SHA1
af11d2089daf52977abf56c61305041615532b01
-
SHA256
74a884161c80f24623c59c0272e3548bb6c9ed52a7c4a2beff731f44d7f4fac0
-
SHA512
f13a822519c365fa5f5efcd6ae83303a2ef68d7a4227a08fbbe1ff61904932bb7c3186cb0e71500f4da0f8dfd84f103b85ca820499504f8029feb736f274bf3e
-
SSDEEP
6144:22caGEZt20ZSwbz8+Dxe8kVAO1lAJRgcD5JZbw+wmGfB08I3VUL6YOCTJKCiopTj:22FzZtT78TX+qmYL6YOpCnTUh8Ey
Malware Config
Signatures
-
Detect Mystic stealer payload 6 IoCs
resource yara_rule behavioral1/memory/3000-3-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/3000-4-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/3000-5-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/3000-7-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/3000-9-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/3000-11-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2680 set thread context of 3000 2680 74a884161c80f24623c59c0272e3548bb6c9ed52a7c4a2beff731f44d7f4fac0.exe 29 -
Program crash 1 IoCs
pid pid_target Process procid_target 2600 3000 WerFault.exe 29 -
Suspicious use of WriteProcessMemory 21 IoCs
description pid Process procid_target PID 2680 wrote to memory of 3000 2680 74a884161c80f24623c59c0272e3548bb6c9ed52a7c4a2beff731f44d7f4fac0.exe 29 PID 2680 wrote to memory of 3000 2680 74a884161c80f24623c59c0272e3548bb6c9ed52a7c4a2beff731f44d7f4fac0.exe 29 PID 2680 wrote to memory of 3000 2680 74a884161c80f24623c59c0272e3548bb6c9ed52a7c4a2beff731f44d7f4fac0.exe 29 PID 2680 wrote to memory of 3000 2680 74a884161c80f24623c59c0272e3548bb6c9ed52a7c4a2beff731f44d7f4fac0.exe 29 PID 2680 wrote to memory of 3000 2680 74a884161c80f24623c59c0272e3548bb6c9ed52a7c4a2beff731f44d7f4fac0.exe 29 PID 2680 wrote to memory of 3000 2680 74a884161c80f24623c59c0272e3548bb6c9ed52a7c4a2beff731f44d7f4fac0.exe 29 PID 2680 wrote to memory of 3000 2680 74a884161c80f24623c59c0272e3548bb6c9ed52a7c4a2beff731f44d7f4fac0.exe 29 PID 2680 wrote to memory of 3000 2680 74a884161c80f24623c59c0272e3548bb6c9ed52a7c4a2beff731f44d7f4fac0.exe 29 PID 2680 wrote to memory of 3000 2680 74a884161c80f24623c59c0272e3548bb6c9ed52a7c4a2beff731f44d7f4fac0.exe 29 PID 2680 wrote to memory of 3000 2680 74a884161c80f24623c59c0272e3548bb6c9ed52a7c4a2beff731f44d7f4fac0.exe 29 PID 2680 wrote to memory of 3000 2680 74a884161c80f24623c59c0272e3548bb6c9ed52a7c4a2beff731f44d7f4fac0.exe 29 PID 2680 wrote to memory of 3000 2680 74a884161c80f24623c59c0272e3548bb6c9ed52a7c4a2beff731f44d7f4fac0.exe 29 PID 2680 wrote to memory of 3000 2680 74a884161c80f24623c59c0272e3548bb6c9ed52a7c4a2beff731f44d7f4fac0.exe 29 PID 2680 wrote to memory of 3000 2680 74a884161c80f24623c59c0272e3548bb6c9ed52a7c4a2beff731f44d7f4fac0.exe 29 PID 3000 wrote to memory of 2600 3000 AppLaunch.exe 30 PID 3000 wrote to memory of 2600 3000 AppLaunch.exe 30 PID 3000 wrote to memory of 2600 3000 AppLaunch.exe 30 PID 3000 wrote to memory of 2600 3000 AppLaunch.exe 30 PID 3000 wrote to memory of 2600 3000 AppLaunch.exe 30 PID 3000 wrote to memory of 2600 3000 AppLaunch.exe 30 PID 3000 wrote to memory of 2600 3000 AppLaunch.exe 30
Processes
-
C:\Users\Admin\AppData\Local\Temp\74a884161c80f24623c59c0272e3548bb6c9ed52a7c4a2beff731f44d7f4fac0.exe"C:\Users\Admin\AppData\Local\Temp\74a884161c80f24623c59c0272e3548bb6c9ed52a7c4a2beff731f44d7f4fac0.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2680 -
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:3000 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3000 -s 1963⤵
- Program crash
PID:2600
-
-