Analysis
-
max time kernel
120s -
max time network
125s -
platform
windows7_x64 -
resource
win7-20230831-en -
resource tags
arch:x64arch:x86image:win7-20230831-enlocale:en-usos:windows7-x64system -
submitted
13-10-2023 02:43
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
7a266b1d528127259dc89f9d9410b19c5ab55247034db6e4ec8f37c1b51bee79_JC.exe
Resource
win7-20230831-en
windows7-x64
4 signatures
150 seconds
General
-
Target
7a266b1d528127259dc89f9d9410b19c5ab55247034db6e4ec8f37c1b51bee79_JC.exe
-
Size
1.8MB
-
MD5
f94bf3a0e3733958d4973ef664f78927
-
SHA1
a1e0a0f9d6d92e6047f9dbbbe57cda7925af7e29
-
SHA256
7a266b1d528127259dc89f9d9410b19c5ab55247034db6e4ec8f37c1b51bee79
-
SHA512
947d6efffd28f45692eef1dfc893636679e76c907d45504ee7e6778f0b412ec8ab91771cb821d1ccb2c212077c51d49bdb71b072ad57a07c8c44d8eafb76c2b0
-
SSDEEP
24576:DMdQ1KOpYU/hsYVNQnb3iUBDqd6a9Dhvh9wj78ptl:31F/hsYVNQ+UI6a3vHwj78pv
Malware Config
Signatures
-
Detect Mystic stealer payload 8 IoCs
resource yara_rule behavioral1/memory/2372-15-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2372-13-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2372-10-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2372-8-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2372-17-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2372-19-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2372-18-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2372-6-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 1248 set thread context of 2372 1248 7a266b1d528127259dc89f9d9410b19c5ab55247034db6e4ec8f37c1b51bee79_JC.exe 29 -
Suspicious use of WriteProcessMemory 14 IoCs
description pid Process procid_target PID 1248 wrote to memory of 2372 1248 7a266b1d528127259dc89f9d9410b19c5ab55247034db6e4ec8f37c1b51bee79_JC.exe 29 PID 1248 wrote to memory of 2372 1248 7a266b1d528127259dc89f9d9410b19c5ab55247034db6e4ec8f37c1b51bee79_JC.exe 29 PID 1248 wrote to memory of 2372 1248 7a266b1d528127259dc89f9d9410b19c5ab55247034db6e4ec8f37c1b51bee79_JC.exe 29 PID 1248 wrote to memory of 2372 1248 7a266b1d528127259dc89f9d9410b19c5ab55247034db6e4ec8f37c1b51bee79_JC.exe 29 PID 1248 wrote to memory of 2372 1248 7a266b1d528127259dc89f9d9410b19c5ab55247034db6e4ec8f37c1b51bee79_JC.exe 29 PID 1248 wrote to memory of 2372 1248 7a266b1d528127259dc89f9d9410b19c5ab55247034db6e4ec8f37c1b51bee79_JC.exe 29 PID 1248 wrote to memory of 2372 1248 7a266b1d528127259dc89f9d9410b19c5ab55247034db6e4ec8f37c1b51bee79_JC.exe 29 PID 1248 wrote to memory of 2372 1248 7a266b1d528127259dc89f9d9410b19c5ab55247034db6e4ec8f37c1b51bee79_JC.exe 29 PID 1248 wrote to memory of 2372 1248 7a266b1d528127259dc89f9d9410b19c5ab55247034db6e4ec8f37c1b51bee79_JC.exe 29 PID 1248 wrote to memory of 2372 1248 7a266b1d528127259dc89f9d9410b19c5ab55247034db6e4ec8f37c1b51bee79_JC.exe 29 PID 1248 wrote to memory of 2372 1248 7a266b1d528127259dc89f9d9410b19c5ab55247034db6e4ec8f37c1b51bee79_JC.exe 29 PID 1248 wrote to memory of 2372 1248 7a266b1d528127259dc89f9d9410b19c5ab55247034db6e4ec8f37c1b51bee79_JC.exe 29 PID 1248 wrote to memory of 2372 1248 7a266b1d528127259dc89f9d9410b19c5ab55247034db6e4ec8f37c1b51bee79_JC.exe 29 PID 1248 wrote to memory of 2372 1248 7a266b1d528127259dc89f9d9410b19c5ab55247034db6e4ec8f37c1b51bee79_JC.exe 29
Processes
-
C:\Users\Admin\AppData\Local\Temp\7a266b1d528127259dc89f9d9410b19c5ab55247034db6e4ec8f37c1b51bee79_JC.exe"C:\Users\Admin\AppData\Local\Temp\7a266b1d528127259dc89f9d9410b19c5ab55247034db6e4ec8f37c1b51bee79_JC.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:1248 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:2372
-