Analysis
-
max time kernel
118s -
max time network
151s -
platform
windows7_x64 -
resource
win7-20230831-en -
resource tags
arch:x64arch:x86image:win7-20230831-enlocale:en-usos:windows7-x64system -
submitted
10-10-2023 21:01
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
8085430f270fd6ebcec4d167ee88472e314ef6f7125706f0d8c8a1c3f9796b90.exe
Resource
win7-20230831-en
windows7-x64
5 signatures
150 seconds
General
-
Target
8085430f270fd6ebcec4d167ee88472e314ef6f7125706f0d8c8a1c3f9796b90.exe
-
Size
276KB
-
MD5
daeda710935ca645576818e0b0a6b84b
-
SHA1
4a4b01ce3e39d5598d0031cda8b1af9d3d329e67
-
SHA256
8085430f270fd6ebcec4d167ee88472e314ef6f7125706f0d8c8a1c3f9796b90
-
SHA512
28f62ec366052f41651234e24225485bd91e5d0328b87ee67156c98071e429af1cbf132f387f8f5f23d7a18e894a8ca716e8f3aa84f502116d1ba46f4b76a83d
-
SSDEEP
6144:WhCcKajWpVP06ik3mU29FeiZ7j0VfWpgrj:W1KajWYUM7j0Ipej
Malware Config
Signatures
-
Detect Mystic stealer payload 6 IoCs
resource yara_rule behavioral1/memory/2028-3-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2028-7-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2028-5-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2028-4-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2028-9-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2028-11-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 1572 set thread context of 2028 1572 8085430f270fd6ebcec4d167ee88472e314ef6f7125706f0d8c8a1c3f9796b90.exe 29 -
Program crash 2 IoCs
pid pid_target Process procid_target 2772 1572 WerFault.exe 27 2708 2028 WerFault.exe 29 -
Suspicious use of WriteProcessMemory 25 IoCs
description pid Process procid_target PID 1572 wrote to memory of 2028 1572 8085430f270fd6ebcec4d167ee88472e314ef6f7125706f0d8c8a1c3f9796b90.exe 29 PID 1572 wrote to memory of 2028 1572 8085430f270fd6ebcec4d167ee88472e314ef6f7125706f0d8c8a1c3f9796b90.exe 29 PID 1572 wrote to memory of 2028 1572 8085430f270fd6ebcec4d167ee88472e314ef6f7125706f0d8c8a1c3f9796b90.exe 29 PID 1572 wrote to memory of 2028 1572 8085430f270fd6ebcec4d167ee88472e314ef6f7125706f0d8c8a1c3f9796b90.exe 29 PID 1572 wrote to memory of 2028 1572 8085430f270fd6ebcec4d167ee88472e314ef6f7125706f0d8c8a1c3f9796b90.exe 29 PID 1572 wrote to memory of 2028 1572 8085430f270fd6ebcec4d167ee88472e314ef6f7125706f0d8c8a1c3f9796b90.exe 29 PID 1572 wrote to memory of 2028 1572 8085430f270fd6ebcec4d167ee88472e314ef6f7125706f0d8c8a1c3f9796b90.exe 29 PID 1572 wrote to memory of 2028 1572 8085430f270fd6ebcec4d167ee88472e314ef6f7125706f0d8c8a1c3f9796b90.exe 29 PID 1572 wrote to memory of 2028 1572 8085430f270fd6ebcec4d167ee88472e314ef6f7125706f0d8c8a1c3f9796b90.exe 29 PID 1572 wrote to memory of 2028 1572 8085430f270fd6ebcec4d167ee88472e314ef6f7125706f0d8c8a1c3f9796b90.exe 29 PID 1572 wrote to memory of 2028 1572 8085430f270fd6ebcec4d167ee88472e314ef6f7125706f0d8c8a1c3f9796b90.exe 29 PID 1572 wrote to memory of 2028 1572 8085430f270fd6ebcec4d167ee88472e314ef6f7125706f0d8c8a1c3f9796b90.exe 29 PID 1572 wrote to memory of 2028 1572 8085430f270fd6ebcec4d167ee88472e314ef6f7125706f0d8c8a1c3f9796b90.exe 29 PID 1572 wrote to memory of 2028 1572 8085430f270fd6ebcec4d167ee88472e314ef6f7125706f0d8c8a1c3f9796b90.exe 29 PID 1572 wrote to memory of 2772 1572 8085430f270fd6ebcec4d167ee88472e314ef6f7125706f0d8c8a1c3f9796b90.exe 30 PID 1572 wrote to memory of 2772 1572 8085430f270fd6ebcec4d167ee88472e314ef6f7125706f0d8c8a1c3f9796b90.exe 30 PID 1572 wrote to memory of 2772 1572 8085430f270fd6ebcec4d167ee88472e314ef6f7125706f0d8c8a1c3f9796b90.exe 30 PID 1572 wrote to memory of 2772 1572 8085430f270fd6ebcec4d167ee88472e314ef6f7125706f0d8c8a1c3f9796b90.exe 30 PID 2028 wrote to memory of 2708 2028 AppLaunch.exe 31 PID 2028 wrote to memory of 2708 2028 AppLaunch.exe 31 PID 2028 wrote to memory of 2708 2028 AppLaunch.exe 31 PID 2028 wrote to memory of 2708 2028 AppLaunch.exe 31 PID 2028 wrote to memory of 2708 2028 AppLaunch.exe 31 PID 2028 wrote to memory of 2708 2028 AppLaunch.exe 31 PID 2028 wrote to memory of 2708 2028 AppLaunch.exe 31
Processes
-
C:\Users\Admin\AppData\Local\Temp\8085430f270fd6ebcec4d167ee88472e314ef6f7125706f0d8c8a1c3f9796b90.exe"C:\Users\Admin\AppData\Local\Temp\8085430f270fd6ebcec4d167ee88472e314ef6f7125706f0d8c8a1c3f9796b90.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:1572 -
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:2028 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2028 -s 1963⤵
- Program crash
PID:2708
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 1572 -s 682⤵
- Program crash
PID:2772
-