Analysis
-
max time kernel
150s -
max time network
151s -
platform
windows10-2004_x64 -
resource
win10v2004-20240412-en -
resource tags
arch:x64arch:x86image:win10v2004-20240412-enlocale:en-usos:windows10-2004-x64system -
submitted
20-04-2024 19:20
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
1a58f07bcdc72061d1761d5b3a41ec5811006b2634d80240504ffafa01496e16.exe
Resource
win7-20240221-en
windows7-x64
5 signatures
150 seconds
General
-
Target
1a58f07bcdc72061d1761d5b3a41ec5811006b2634d80240504ffafa01496e16.exe
-
Size
1.1MB
-
MD5
2ec6e05eb510e491a168f8377725b43c
-
SHA1
180bf9be7944e5aa8190161ec34c00fa85000c7f
-
SHA256
1a58f07bcdc72061d1761d5b3a41ec5811006b2634d80240504ffafa01496e16
-
SHA512
b957c1d3d6fb1618b8a408a4b9dd528f81970fcf63c435fadf02435a8c3837ff8cf9b5880d7d5a29028cafc4039eac03f18ff24109ff6adc8333c77ef02e2158
-
SSDEEP
12288:3JL65OW9gH1dNmfJ7VqgLEZqg4wcvg8S8rAtufCeRBmRAnU1aWFrWO6HA:ZLZW9gH1dNmfzqfZqgeIWAwWb6H
Malware Config
Signatures
-
Detect Mystic stealer payload 4 IoCs
resource yara_rule behavioral2/memory/4888-0-0x0000000000400000-0x0000000000434000-memory.dmp mystic_family behavioral2/memory/4888-1-0x0000000000400000-0x0000000000434000-memory.dmp mystic_family behavioral2/memory/4888-2-0x0000000000400000-0x0000000000434000-memory.dmp mystic_family behavioral2/memory/4888-3-0x0000000000400000-0x0000000000434000-memory.dmp mystic_family -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 5060 set thread context of 4888 5060 1a58f07bcdc72061d1761d5b3a41ec5811006b2634d80240504ffafa01496e16.exe 88 -
Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 5060 wrote to memory of 4888 5060 1a58f07bcdc72061d1761d5b3a41ec5811006b2634d80240504ffafa01496e16.exe 88 PID 5060 wrote to memory of 4888 5060 1a58f07bcdc72061d1761d5b3a41ec5811006b2634d80240504ffafa01496e16.exe 88 PID 5060 wrote to memory of 4888 5060 1a58f07bcdc72061d1761d5b3a41ec5811006b2634d80240504ffafa01496e16.exe 88 PID 5060 wrote to memory of 4888 5060 1a58f07bcdc72061d1761d5b3a41ec5811006b2634d80240504ffafa01496e16.exe 88 PID 5060 wrote to memory of 4888 5060 1a58f07bcdc72061d1761d5b3a41ec5811006b2634d80240504ffafa01496e16.exe 88 PID 5060 wrote to memory of 4888 5060 1a58f07bcdc72061d1761d5b3a41ec5811006b2634d80240504ffafa01496e16.exe 88 PID 5060 wrote to memory of 4888 5060 1a58f07bcdc72061d1761d5b3a41ec5811006b2634d80240504ffafa01496e16.exe 88 PID 5060 wrote to memory of 4888 5060 1a58f07bcdc72061d1761d5b3a41ec5811006b2634d80240504ffafa01496e16.exe 88 PID 5060 wrote to memory of 4888 5060 1a58f07bcdc72061d1761d5b3a41ec5811006b2634d80240504ffafa01496e16.exe 88 PID 5060 wrote to memory of 4888 5060 1a58f07bcdc72061d1761d5b3a41ec5811006b2634d80240504ffafa01496e16.exe 88
Processes
-
C:\Users\Admin\AppData\Local\Temp\1a58f07bcdc72061d1761d5b3a41ec5811006b2634d80240504ffafa01496e16.exe"C:\Users\Admin\AppData\Local\Temp\1a58f07bcdc72061d1761d5b3a41ec5811006b2634d80240504ffafa01496e16.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:5060 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:4888
-