Analysis
-
max time kernel
117s -
max time network
122s -
platform
windows7_x64 -
resource
win7-20230831-en -
resource tags
arch:x64arch:x86image:win7-20230831-enlocale:en-usos:windows7-x64system -
submitted
11-10-2023 11:36
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
ecf879394639be2b544d62d7b904223c106cb07bf0c5dc87429282b52a0ba86d.exe
Resource
win7-20230831-en
windows7-x64
5 signatures
150 seconds
General
-
Target
ecf879394639be2b544d62d7b904223c106cb07bf0c5dc87429282b52a0ba86d.exe
-
Size
346KB
-
MD5
0d4507df6c4f697f5c2e61dd574a55d3
-
SHA1
2644c9b8da6a26510d8d38c586834f223c374e15
-
SHA256
ecf879394639be2b544d62d7b904223c106cb07bf0c5dc87429282b52a0ba86d
-
SHA512
f6e17885e5bd1b4fbca1827a0b189d0124c773d6443d2ce4a05601e0e6898b8822b22fef98bad85e34e45b75ddd798a80a3c20811867b5b7055f417776b0af9c
-
SSDEEP
6144:7NCTljS9PgGzqLHvw1t6mAOfd5pBgepdWq+R0z4viKC:7NgS9PgGimf5pBgIWH5iKC
Malware Config
Signatures
-
Detect Mystic stealer payload 6 IoCs
resource yara_rule behavioral1/memory/3052-3-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/3052-7-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/3052-5-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/3052-4-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/3052-9-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/3052-11-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2760 set thread context of 3052 2760 ecf879394639be2b544d62d7b904223c106cb07bf0c5dc87429282b52a0ba86d.exe 31 -
Program crash 2 IoCs
pid pid_target Process procid_target 2692 2760 WerFault.exe 27 2184 3052 WerFault.exe 31 -
Suspicious use of WriteProcessMemory 39 IoCs
description pid Process procid_target PID 2760 wrote to memory of 2988 2760 ecf879394639be2b544d62d7b904223c106cb07bf0c5dc87429282b52a0ba86d.exe 29 PID 2760 wrote to memory of 2988 2760 ecf879394639be2b544d62d7b904223c106cb07bf0c5dc87429282b52a0ba86d.exe 29 PID 2760 wrote to memory of 2988 2760 ecf879394639be2b544d62d7b904223c106cb07bf0c5dc87429282b52a0ba86d.exe 29 PID 2760 wrote to memory of 2988 2760 ecf879394639be2b544d62d7b904223c106cb07bf0c5dc87429282b52a0ba86d.exe 29 PID 2760 wrote to memory of 2988 2760 ecf879394639be2b544d62d7b904223c106cb07bf0c5dc87429282b52a0ba86d.exe 29 PID 2760 wrote to memory of 2988 2760 ecf879394639be2b544d62d7b904223c106cb07bf0c5dc87429282b52a0ba86d.exe 29 PID 2760 wrote to memory of 2988 2760 ecf879394639be2b544d62d7b904223c106cb07bf0c5dc87429282b52a0ba86d.exe 29 PID 2760 wrote to memory of 2244 2760 ecf879394639be2b544d62d7b904223c106cb07bf0c5dc87429282b52a0ba86d.exe 30 PID 2760 wrote to memory of 2244 2760 ecf879394639be2b544d62d7b904223c106cb07bf0c5dc87429282b52a0ba86d.exe 30 PID 2760 wrote to memory of 2244 2760 ecf879394639be2b544d62d7b904223c106cb07bf0c5dc87429282b52a0ba86d.exe 30 PID 2760 wrote to memory of 2244 2760 ecf879394639be2b544d62d7b904223c106cb07bf0c5dc87429282b52a0ba86d.exe 30 PID 2760 wrote to memory of 2244 2760 ecf879394639be2b544d62d7b904223c106cb07bf0c5dc87429282b52a0ba86d.exe 30 PID 2760 wrote to memory of 2244 2760 ecf879394639be2b544d62d7b904223c106cb07bf0c5dc87429282b52a0ba86d.exe 30 PID 2760 wrote to memory of 2244 2760 ecf879394639be2b544d62d7b904223c106cb07bf0c5dc87429282b52a0ba86d.exe 30 PID 2760 wrote to memory of 3052 2760 ecf879394639be2b544d62d7b904223c106cb07bf0c5dc87429282b52a0ba86d.exe 31 PID 2760 wrote to memory of 3052 2760 ecf879394639be2b544d62d7b904223c106cb07bf0c5dc87429282b52a0ba86d.exe 31 PID 2760 wrote to memory of 3052 2760 ecf879394639be2b544d62d7b904223c106cb07bf0c5dc87429282b52a0ba86d.exe 31 PID 2760 wrote to memory of 3052 2760 ecf879394639be2b544d62d7b904223c106cb07bf0c5dc87429282b52a0ba86d.exe 31 PID 2760 wrote to memory of 3052 2760 ecf879394639be2b544d62d7b904223c106cb07bf0c5dc87429282b52a0ba86d.exe 31 PID 2760 wrote to memory of 3052 2760 ecf879394639be2b544d62d7b904223c106cb07bf0c5dc87429282b52a0ba86d.exe 31 PID 2760 wrote to memory of 3052 2760 ecf879394639be2b544d62d7b904223c106cb07bf0c5dc87429282b52a0ba86d.exe 31 PID 2760 wrote to memory of 3052 2760 ecf879394639be2b544d62d7b904223c106cb07bf0c5dc87429282b52a0ba86d.exe 31 PID 2760 wrote to memory of 3052 2760 ecf879394639be2b544d62d7b904223c106cb07bf0c5dc87429282b52a0ba86d.exe 31 PID 2760 wrote to memory of 3052 2760 ecf879394639be2b544d62d7b904223c106cb07bf0c5dc87429282b52a0ba86d.exe 31 PID 2760 wrote to memory of 3052 2760 ecf879394639be2b544d62d7b904223c106cb07bf0c5dc87429282b52a0ba86d.exe 31 PID 2760 wrote to memory of 3052 2760 ecf879394639be2b544d62d7b904223c106cb07bf0c5dc87429282b52a0ba86d.exe 31 PID 2760 wrote to memory of 3052 2760 ecf879394639be2b544d62d7b904223c106cb07bf0c5dc87429282b52a0ba86d.exe 31 PID 2760 wrote to memory of 3052 2760 ecf879394639be2b544d62d7b904223c106cb07bf0c5dc87429282b52a0ba86d.exe 31 PID 2760 wrote to memory of 2692 2760 ecf879394639be2b544d62d7b904223c106cb07bf0c5dc87429282b52a0ba86d.exe 32 PID 2760 wrote to memory of 2692 2760 ecf879394639be2b544d62d7b904223c106cb07bf0c5dc87429282b52a0ba86d.exe 32 PID 2760 wrote to memory of 2692 2760 ecf879394639be2b544d62d7b904223c106cb07bf0c5dc87429282b52a0ba86d.exe 32 PID 2760 wrote to memory of 2692 2760 ecf879394639be2b544d62d7b904223c106cb07bf0c5dc87429282b52a0ba86d.exe 32 PID 3052 wrote to memory of 2184 3052 AppLaunch.exe 33 PID 3052 wrote to memory of 2184 3052 AppLaunch.exe 33 PID 3052 wrote to memory of 2184 3052 AppLaunch.exe 33 PID 3052 wrote to memory of 2184 3052 AppLaunch.exe 33 PID 3052 wrote to memory of 2184 3052 AppLaunch.exe 33 PID 3052 wrote to memory of 2184 3052 AppLaunch.exe 33 PID 3052 wrote to memory of 2184 3052 AppLaunch.exe 33
Processes
-
C:\Users\Admin\AppData\Local\Temp\ecf879394639be2b544d62d7b904223c106cb07bf0c5dc87429282b52a0ba86d.exe"C:\Users\Admin\AppData\Local\Temp\ecf879394639be2b544d62d7b904223c106cb07bf0c5dc87429282b52a0ba86d.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2760 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:2988
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:2244
-
-
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:3052 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3052 -s 1963⤵
- Program crash
PID:2184
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2760 -s 1402⤵
- Program crash
PID:2692
-