Analysis
-
max time kernel
122s -
max time network
126s -
platform
windows7_x64 -
resource
win7-20230831-en -
resource tags
arch:x64arch:x86image:win7-20230831-enlocale:en-usos:windows7-x64system -
submitted
12-10-2023 15:19
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
6b643ca0b34defb2996c36f34af070d4a9424a06640262363fb96c5f1ac82667_JC.exe
Resource
win7-20230831-en
windows7-x64
5 signatures
150 seconds
General
-
Target
6b643ca0b34defb2996c36f34af070d4a9424a06640262363fb96c5f1ac82667_JC.exe
-
Size
359KB
-
MD5
8d7b85f6cdd896857cbf4bdee0eb920a
-
SHA1
b509b497c7391a00956e2c76d7042b649548ae87
-
SHA256
6b643ca0b34defb2996c36f34af070d4a9424a06640262363fb96c5f1ac82667
-
SHA512
4dc16e8265d7ada6904ab30cc3bc1a2d2791fd07760124b426aa6ef4db307807d5781353fc0a40d72f35b5469555727c77e306c944c8e98862954626d14e114e
-
SSDEEP
6144:HncaGEZt20ZSwbz8+Dxe8kVAOUl7jsiV46Tr/WjbmBRQkzLwwLB6oema5vmbh8Ey:HnFzZtT78T+2O4EjWjTOwGXh8Ey
Malware Config
Signatures
-
Detect Mystic stealer payload 6 IoCs
resource yara_rule behavioral1/memory/2428-3-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2428-4-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2428-7-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2428-5-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2428-9-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2428-11-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2444 set thread context of 2428 2444 6b643ca0b34defb2996c36f34af070d4a9424a06640262363fb96c5f1ac82667_JC.exe 30 -
Program crash 1 IoCs
pid pid_target Process procid_target 1152 2428 WerFault.exe 30 -
Suspicious use of WriteProcessMemory 28 IoCs
description pid Process procid_target PID 2444 wrote to memory of 2176 2444 6b643ca0b34defb2996c36f34af070d4a9424a06640262363fb96c5f1ac82667_JC.exe 29 PID 2444 wrote to memory of 2176 2444 6b643ca0b34defb2996c36f34af070d4a9424a06640262363fb96c5f1ac82667_JC.exe 29 PID 2444 wrote to memory of 2176 2444 6b643ca0b34defb2996c36f34af070d4a9424a06640262363fb96c5f1ac82667_JC.exe 29 PID 2444 wrote to memory of 2176 2444 6b643ca0b34defb2996c36f34af070d4a9424a06640262363fb96c5f1ac82667_JC.exe 29 PID 2444 wrote to memory of 2176 2444 6b643ca0b34defb2996c36f34af070d4a9424a06640262363fb96c5f1ac82667_JC.exe 29 PID 2444 wrote to memory of 2176 2444 6b643ca0b34defb2996c36f34af070d4a9424a06640262363fb96c5f1ac82667_JC.exe 29 PID 2444 wrote to memory of 2176 2444 6b643ca0b34defb2996c36f34af070d4a9424a06640262363fb96c5f1ac82667_JC.exe 29 PID 2444 wrote to memory of 2428 2444 6b643ca0b34defb2996c36f34af070d4a9424a06640262363fb96c5f1ac82667_JC.exe 30 PID 2444 wrote to memory of 2428 2444 6b643ca0b34defb2996c36f34af070d4a9424a06640262363fb96c5f1ac82667_JC.exe 30 PID 2444 wrote to memory of 2428 2444 6b643ca0b34defb2996c36f34af070d4a9424a06640262363fb96c5f1ac82667_JC.exe 30 PID 2444 wrote to memory of 2428 2444 6b643ca0b34defb2996c36f34af070d4a9424a06640262363fb96c5f1ac82667_JC.exe 30 PID 2444 wrote to memory of 2428 2444 6b643ca0b34defb2996c36f34af070d4a9424a06640262363fb96c5f1ac82667_JC.exe 30 PID 2444 wrote to memory of 2428 2444 6b643ca0b34defb2996c36f34af070d4a9424a06640262363fb96c5f1ac82667_JC.exe 30 PID 2444 wrote to memory of 2428 2444 6b643ca0b34defb2996c36f34af070d4a9424a06640262363fb96c5f1ac82667_JC.exe 30 PID 2444 wrote to memory of 2428 2444 6b643ca0b34defb2996c36f34af070d4a9424a06640262363fb96c5f1ac82667_JC.exe 30 PID 2444 wrote to memory of 2428 2444 6b643ca0b34defb2996c36f34af070d4a9424a06640262363fb96c5f1ac82667_JC.exe 30 PID 2444 wrote to memory of 2428 2444 6b643ca0b34defb2996c36f34af070d4a9424a06640262363fb96c5f1ac82667_JC.exe 30 PID 2444 wrote to memory of 2428 2444 6b643ca0b34defb2996c36f34af070d4a9424a06640262363fb96c5f1ac82667_JC.exe 30 PID 2444 wrote to memory of 2428 2444 6b643ca0b34defb2996c36f34af070d4a9424a06640262363fb96c5f1ac82667_JC.exe 30 PID 2444 wrote to memory of 2428 2444 6b643ca0b34defb2996c36f34af070d4a9424a06640262363fb96c5f1ac82667_JC.exe 30 PID 2444 wrote to memory of 2428 2444 6b643ca0b34defb2996c36f34af070d4a9424a06640262363fb96c5f1ac82667_JC.exe 30 PID 2428 wrote to memory of 1152 2428 AppLaunch.exe 31 PID 2428 wrote to memory of 1152 2428 AppLaunch.exe 31 PID 2428 wrote to memory of 1152 2428 AppLaunch.exe 31 PID 2428 wrote to memory of 1152 2428 AppLaunch.exe 31 PID 2428 wrote to memory of 1152 2428 AppLaunch.exe 31 PID 2428 wrote to memory of 1152 2428 AppLaunch.exe 31 PID 2428 wrote to memory of 1152 2428 AppLaunch.exe 31
Processes
-
C:\Users\Admin\AppData\Local\Temp\6b643ca0b34defb2996c36f34af070d4a9424a06640262363fb96c5f1ac82667_JC.exe"C:\Users\Admin\AppData\Local\Temp\6b643ca0b34defb2996c36f34af070d4a9424a06640262363fb96c5f1ac82667_JC.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2444 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:2176
-
-
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:2428 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2428 -s 1963⤵
- Program crash
PID:1152
-
-