Analysis
-
max time kernel
119s -
max time network
134s -
platform
windows7_x64 -
resource
win7-20230831-en -
resource tags
arch:x64arch:x86image:win7-20230831-enlocale:en-usos:windows7-x64system -
submitted
11-10-2023 10:36
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
4370af9251062edeaf536fa0770a5779c2ec59ef3f3e61050b64bb58eb4a7f9c.exe
Resource
win7-20230831-en
windows7-x64
5 signatures
150 seconds
General
-
Target
4370af9251062edeaf536fa0770a5779c2ec59ef3f3e61050b64bb58eb4a7f9c.exe
-
Size
350KB
-
MD5
05f4b85c81e7d08832041807cf53662a
-
SHA1
282516da27d4442043ca8d8cd00bb1d3c9f26999
-
SHA256
4370af9251062edeaf536fa0770a5779c2ec59ef3f3e61050b64bb58eb4a7f9c
-
SHA512
dec29a80657315d94bb1e62c76ecb391404d2d733ca97ea5d18d24ff36245eb4eb58b5c19597c58496d2ccc25ed8e5398944e5329e424a0a0e424197c69585bf
-
SSDEEP
6144:bt3LsrNJmc30jXud9b7zAOhp70n6PqU6ag6AbQxsMPGXkfaJF4S:bqxJm+bzLpwn6dM6cKPGU6F4S
Malware Config
Signatures
-
Detect Mystic stealer payload 6 IoCs
resource yara_rule behavioral1/memory/2088-3-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2088-5-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2088-4-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2088-7-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2088-9-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2088-11-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2404 set thread context of 2088 2404 4370af9251062edeaf536fa0770a5779c2ec59ef3f3e61050b64bb58eb4a7f9c.exe 28 -
Program crash 2 IoCs
pid pid_target Process procid_target 2724 2404 WerFault.exe 27 2808 2088 WerFault.exe 28 -
Suspicious use of WriteProcessMemory 25 IoCs
description pid Process procid_target PID 2404 wrote to memory of 2088 2404 4370af9251062edeaf536fa0770a5779c2ec59ef3f3e61050b64bb58eb4a7f9c.exe 28 PID 2404 wrote to memory of 2088 2404 4370af9251062edeaf536fa0770a5779c2ec59ef3f3e61050b64bb58eb4a7f9c.exe 28 PID 2404 wrote to memory of 2088 2404 4370af9251062edeaf536fa0770a5779c2ec59ef3f3e61050b64bb58eb4a7f9c.exe 28 PID 2404 wrote to memory of 2088 2404 4370af9251062edeaf536fa0770a5779c2ec59ef3f3e61050b64bb58eb4a7f9c.exe 28 PID 2404 wrote to memory of 2088 2404 4370af9251062edeaf536fa0770a5779c2ec59ef3f3e61050b64bb58eb4a7f9c.exe 28 PID 2404 wrote to memory of 2088 2404 4370af9251062edeaf536fa0770a5779c2ec59ef3f3e61050b64bb58eb4a7f9c.exe 28 PID 2404 wrote to memory of 2088 2404 4370af9251062edeaf536fa0770a5779c2ec59ef3f3e61050b64bb58eb4a7f9c.exe 28 PID 2404 wrote to memory of 2088 2404 4370af9251062edeaf536fa0770a5779c2ec59ef3f3e61050b64bb58eb4a7f9c.exe 28 PID 2404 wrote to memory of 2088 2404 4370af9251062edeaf536fa0770a5779c2ec59ef3f3e61050b64bb58eb4a7f9c.exe 28 PID 2404 wrote to memory of 2088 2404 4370af9251062edeaf536fa0770a5779c2ec59ef3f3e61050b64bb58eb4a7f9c.exe 28 PID 2404 wrote to memory of 2088 2404 4370af9251062edeaf536fa0770a5779c2ec59ef3f3e61050b64bb58eb4a7f9c.exe 28 PID 2404 wrote to memory of 2088 2404 4370af9251062edeaf536fa0770a5779c2ec59ef3f3e61050b64bb58eb4a7f9c.exe 28 PID 2404 wrote to memory of 2088 2404 4370af9251062edeaf536fa0770a5779c2ec59ef3f3e61050b64bb58eb4a7f9c.exe 28 PID 2404 wrote to memory of 2088 2404 4370af9251062edeaf536fa0770a5779c2ec59ef3f3e61050b64bb58eb4a7f9c.exe 28 PID 2404 wrote to memory of 2724 2404 4370af9251062edeaf536fa0770a5779c2ec59ef3f3e61050b64bb58eb4a7f9c.exe 29 PID 2404 wrote to memory of 2724 2404 4370af9251062edeaf536fa0770a5779c2ec59ef3f3e61050b64bb58eb4a7f9c.exe 29 PID 2404 wrote to memory of 2724 2404 4370af9251062edeaf536fa0770a5779c2ec59ef3f3e61050b64bb58eb4a7f9c.exe 29 PID 2404 wrote to memory of 2724 2404 4370af9251062edeaf536fa0770a5779c2ec59ef3f3e61050b64bb58eb4a7f9c.exe 29 PID 2088 wrote to memory of 2808 2088 AppLaunch.exe 30 PID 2088 wrote to memory of 2808 2088 AppLaunch.exe 30 PID 2088 wrote to memory of 2808 2088 AppLaunch.exe 30 PID 2088 wrote to memory of 2808 2088 AppLaunch.exe 30 PID 2088 wrote to memory of 2808 2088 AppLaunch.exe 30 PID 2088 wrote to memory of 2808 2088 AppLaunch.exe 30 PID 2088 wrote to memory of 2808 2088 AppLaunch.exe 30
Processes
-
C:\Users\Admin\AppData\Local\Temp\4370af9251062edeaf536fa0770a5779c2ec59ef3f3e61050b64bb58eb4a7f9c.exe"C:\Users\Admin\AppData\Local\Temp\4370af9251062edeaf536fa0770a5779c2ec59ef3f3e61050b64bb58eb4a7f9c.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2404 -
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:2088 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2088 -s 1963⤵
- Program crash
PID:2808
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2404 -s 922⤵
- Program crash
PID:2724
-