Analysis
-
max time kernel
120s -
max time network
164s -
platform
windows7_x64 -
resource
win7-20230831-en -
resource tags
arch:x64arch:x86image:win7-20230831-enlocale:en-usos:windows7-x64system -
submitted
13/10/2023, 02:01
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
faf4d4a6c1e99183c10d2f3e5116d3213da393c687743e0a16a9af3677777a99_JC.exe
Resource
win7-20230831-en
5 signatures
150 seconds
General
-
Target
faf4d4a6c1e99183c10d2f3e5116d3213da393c687743e0a16a9af3677777a99_JC.exe
-
Size
372KB
-
MD5
414b8a2493d13e0e1f88188525d0f1e0
-
SHA1
7bdf6250911b91b52ac8c65f15cdfb88b310546e
-
SHA256
faf4d4a6c1e99183c10d2f3e5116d3213da393c687743e0a16a9af3677777a99
-
SHA512
d76b3f764813ba5fa25f0383d27d5515756710bef07390691405f53503f9004ce89595bf14b51db814fce56428f17c59d3bf2c55b9956531236d6411acc7bfb2
-
SSDEEP
6144:FfP/FCF1NaNyNgAl8gfC93K4BAOad2+pjsvvjCXBPlZIFfLc8PnfcFrdRTOBT:F/FCF1NnMK4B4d2Y8vmKfo8PfETOBT
Malware Config
Signatures
-
Detect Mystic stealer payload 6 IoCs
resource yara_rule behavioral1/memory/2896-3-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2896-4-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2896-5-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2896-7-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2896-9-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2896-11-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2720 set thread context of 2896 2720 faf4d4a6c1e99183c10d2f3e5116d3213da393c687743e0a16a9af3677777a99_JC.exe 28 -
Program crash 1 IoCs
pid pid_target Process procid_target 2468 2896 WerFault.exe 28 -
Suspicious use of WriteProcessMemory 21 IoCs
description pid Process procid_target PID 2720 wrote to memory of 2896 2720 faf4d4a6c1e99183c10d2f3e5116d3213da393c687743e0a16a9af3677777a99_JC.exe 28 PID 2720 wrote to memory of 2896 2720 faf4d4a6c1e99183c10d2f3e5116d3213da393c687743e0a16a9af3677777a99_JC.exe 28 PID 2720 wrote to memory of 2896 2720 faf4d4a6c1e99183c10d2f3e5116d3213da393c687743e0a16a9af3677777a99_JC.exe 28 PID 2720 wrote to memory of 2896 2720 faf4d4a6c1e99183c10d2f3e5116d3213da393c687743e0a16a9af3677777a99_JC.exe 28 PID 2720 wrote to memory of 2896 2720 faf4d4a6c1e99183c10d2f3e5116d3213da393c687743e0a16a9af3677777a99_JC.exe 28 PID 2720 wrote to memory of 2896 2720 faf4d4a6c1e99183c10d2f3e5116d3213da393c687743e0a16a9af3677777a99_JC.exe 28 PID 2720 wrote to memory of 2896 2720 faf4d4a6c1e99183c10d2f3e5116d3213da393c687743e0a16a9af3677777a99_JC.exe 28 PID 2720 wrote to memory of 2896 2720 faf4d4a6c1e99183c10d2f3e5116d3213da393c687743e0a16a9af3677777a99_JC.exe 28 PID 2720 wrote to memory of 2896 2720 faf4d4a6c1e99183c10d2f3e5116d3213da393c687743e0a16a9af3677777a99_JC.exe 28 PID 2720 wrote to memory of 2896 2720 faf4d4a6c1e99183c10d2f3e5116d3213da393c687743e0a16a9af3677777a99_JC.exe 28 PID 2720 wrote to memory of 2896 2720 faf4d4a6c1e99183c10d2f3e5116d3213da393c687743e0a16a9af3677777a99_JC.exe 28 PID 2720 wrote to memory of 2896 2720 faf4d4a6c1e99183c10d2f3e5116d3213da393c687743e0a16a9af3677777a99_JC.exe 28 PID 2720 wrote to memory of 2896 2720 faf4d4a6c1e99183c10d2f3e5116d3213da393c687743e0a16a9af3677777a99_JC.exe 28 PID 2720 wrote to memory of 2896 2720 faf4d4a6c1e99183c10d2f3e5116d3213da393c687743e0a16a9af3677777a99_JC.exe 28 PID 2896 wrote to memory of 2468 2896 AppLaunch.exe 29 PID 2896 wrote to memory of 2468 2896 AppLaunch.exe 29 PID 2896 wrote to memory of 2468 2896 AppLaunch.exe 29 PID 2896 wrote to memory of 2468 2896 AppLaunch.exe 29 PID 2896 wrote to memory of 2468 2896 AppLaunch.exe 29 PID 2896 wrote to memory of 2468 2896 AppLaunch.exe 29 PID 2896 wrote to memory of 2468 2896 AppLaunch.exe 29
Processes
-
C:\Users\Admin\AppData\Local\Temp\faf4d4a6c1e99183c10d2f3e5116d3213da393c687743e0a16a9af3677777a99_JC.exe"C:\Users\Admin\AppData\Local\Temp\faf4d4a6c1e99183c10d2f3e5116d3213da393c687743e0a16a9af3677777a99_JC.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2720 -
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:2896 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2896 -s 1963⤵
- Program crash
PID:2468
-
-