Analysis
-
max time kernel
45s -
max time network
39s -
platform
windows7_x64 -
resource
win7-20230831-en -
resource tags
arch:x64arch:x86image:win7-20230831-enlocale:en-usos:windows7-x64system -
submitted
11/10/2023, 14:24
Static task
static1
Behavioral task
behavioral1
Sample
92924ae90c6f1718abd931401df47b2e548b7784ea6ba577ff1d3c1db94db866.exe
Resource
win7-20230831-en
5 signatures
150 seconds
General
-
Target
92924ae90c6f1718abd931401df47b2e548b7784ea6ba577ff1d3c1db94db866.exe
-
Size
379KB
-
MD5
a18065f2f9f8809e079821ddd8a8fab4
-
SHA1
af832c18bb00d816be8a5885e05c60ab687025da
-
SHA256
92924ae90c6f1718abd931401df47b2e548b7784ea6ba577ff1d3c1db94db866
-
SHA512
2c9b67a43aba22e8ae3e6e47aa0e7bc11562f940a6430a8202f3f7c1664185d5450c7213af716040fca166e3a4a3e336b26f9c431d35afaa98ae813e12e5e37f
-
SSDEEP
6144:CLfcRgs3r9vIum2Tg0N63KAOA/bhC/k5KjiLvLYxwl4+z4g3F:CL0RP3r9Hme+ThC/sKjuLYxl+zD3F
Malware Config
Signatures
-
Detect Mystic stealer payload 6 IoCs
resource yara_rule behavioral1/memory/2700-3-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2700-4-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2700-7-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2700-5-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2700-9-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2700-11-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2648 set thread context of 2700 2648 92924ae90c6f1718abd931401df47b2e548b7784ea6ba577ff1d3c1db94db866.exe 29 -
Program crash 2 IoCs
pid pid_target Process procid_target 2612 2648 WerFault.exe 6 2632 2700 WerFault.exe 29 -
Suspicious use of WriteProcessMemory 25 IoCs
description pid Process procid_target PID 2648 wrote to memory of 2700 2648 92924ae90c6f1718abd931401df47b2e548b7784ea6ba577ff1d3c1db94db866.exe 29 PID 2648 wrote to memory of 2700 2648 92924ae90c6f1718abd931401df47b2e548b7784ea6ba577ff1d3c1db94db866.exe 29 PID 2648 wrote to memory of 2700 2648 92924ae90c6f1718abd931401df47b2e548b7784ea6ba577ff1d3c1db94db866.exe 29 PID 2648 wrote to memory of 2700 2648 92924ae90c6f1718abd931401df47b2e548b7784ea6ba577ff1d3c1db94db866.exe 29 PID 2648 wrote to memory of 2700 2648 92924ae90c6f1718abd931401df47b2e548b7784ea6ba577ff1d3c1db94db866.exe 29 PID 2648 wrote to memory of 2700 2648 92924ae90c6f1718abd931401df47b2e548b7784ea6ba577ff1d3c1db94db866.exe 29 PID 2648 wrote to memory of 2700 2648 92924ae90c6f1718abd931401df47b2e548b7784ea6ba577ff1d3c1db94db866.exe 29 PID 2648 wrote to memory of 2700 2648 92924ae90c6f1718abd931401df47b2e548b7784ea6ba577ff1d3c1db94db866.exe 29 PID 2648 wrote to memory of 2700 2648 92924ae90c6f1718abd931401df47b2e548b7784ea6ba577ff1d3c1db94db866.exe 29 PID 2648 wrote to memory of 2700 2648 92924ae90c6f1718abd931401df47b2e548b7784ea6ba577ff1d3c1db94db866.exe 29 PID 2648 wrote to memory of 2700 2648 92924ae90c6f1718abd931401df47b2e548b7784ea6ba577ff1d3c1db94db866.exe 29 PID 2648 wrote to memory of 2700 2648 92924ae90c6f1718abd931401df47b2e548b7784ea6ba577ff1d3c1db94db866.exe 29 PID 2648 wrote to memory of 2700 2648 92924ae90c6f1718abd931401df47b2e548b7784ea6ba577ff1d3c1db94db866.exe 29 PID 2648 wrote to memory of 2700 2648 92924ae90c6f1718abd931401df47b2e548b7784ea6ba577ff1d3c1db94db866.exe 29 PID 2648 wrote to memory of 2612 2648 92924ae90c6f1718abd931401df47b2e548b7784ea6ba577ff1d3c1db94db866.exe 30 PID 2648 wrote to memory of 2612 2648 92924ae90c6f1718abd931401df47b2e548b7784ea6ba577ff1d3c1db94db866.exe 30 PID 2648 wrote to memory of 2612 2648 92924ae90c6f1718abd931401df47b2e548b7784ea6ba577ff1d3c1db94db866.exe 30 PID 2648 wrote to memory of 2612 2648 92924ae90c6f1718abd931401df47b2e548b7784ea6ba577ff1d3c1db94db866.exe 30 PID 2700 wrote to memory of 2632 2700 AppLaunch.exe 31 PID 2700 wrote to memory of 2632 2700 AppLaunch.exe 31 PID 2700 wrote to memory of 2632 2700 AppLaunch.exe 31 PID 2700 wrote to memory of 2632 2700 AppLaunch.exe 31 PID 2700 wrote to memory of 2632 2700 AppLaunch.exe 31 PID 2700 wrote to memory of 2632 2700 AppLaunch.exe 31 PID 2700 wrote to memory of 2632 2700 AppLaunch.exe 31
Processes
-
C:\Users\Admin\AppData\Local\Temp\92924ae90c6f1718abd931401df47b2e548b7784ea6ba577ff1d3c1db94db866.exe"C:\Users\Admin\AppData\Local\Temp\92924ae90c6f1718abd931401df47b2e548b7784ea6ba577ff1d3c1db94db866.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2648 -
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:2700 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2700 -s 1963⤵
- Program crash
PID:2632
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2648 -s 922⤵
- Program crash
PID:2612
-