Analysis
-
max time kernel
117s -
max time network
124s -
platform
windows7_x64 -
resource
win7-20230831-en -
resource tags
arch:x64arch:x86image:win7-20230831-enlocale:en-usos:windows7-x64system -
submitted
11-10-2023 13:48
Static task
static1
Behavioral task
behavioral1
Sample
ec828ad2b3c4d34d8e1c374dfcfff2b339abd9ea5e99e01478387dd12c4ca501.exe
Resource
win7-20230831-en
windows7-x64
5 signatures
150 seconds
General
-
Target
ec828ad2b3c4d34d8e1c374dfcfff2b339abd9ea5e99e01478387dd12c4ca501.exe
-
Size
379KB
-
MD5
6275adebe99585bb79eb1ba3fc7aa212
-
SHA1
e3360751c689dde6ffb7809bf1a13f8da7d2ea99
-
SHA256
ec828ad2b3c4d34d8e1c374dfcfff2b339abd9ea5e99e01478387dd12c4ca501
-
SHA512
9691c566394941333ca316ba0235e48e3187719e5db6321eb905f32e82eb81bdb525d63015654b5ea4d1a71af9d336b5e842d2e8a7252ec24086223dbea1c5c6
-
SSDEEP
6144:Pk8cRgs3r9vIum2Tg0N63KAO1r/PpVnTw1t1w5om8ced6VviU+Ro9iKIjg3F:PkTRP3r9HmeLrDnU1ty5oged6VviU+RU
Malware Config
Signatures
-
Detect Mystic stealer payload 6 IoCs
resource yara_rule behavioral1/memory/2584-11-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2584-9-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2584-7-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2584-5-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2584-4-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2584-3-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2244 set thread context of 2584 2244 ec828ad2b3c4d34d8e1c374dfcfff2b339abd9ea5e99e01478387dd12c4ca501.exe 28 -
Program crash 2 IoCs
pid pid_target Process procid_target 2400 2244 WerFault.exe 18 2036 2584 WerFault.exe 28 -
Suspicious use of WriteProcessMemory 25 IoCs
description pid Process procid_target PID 2244 wrote to memory of 2584 2244 ec828ad2b3c4d34d8e1c374dfcfff2b339abd9ea5e99e01478387dd12c4ca501.exe 28 PID 2244 wrote to memory of 2584 2244 ec828ad2b3c4d34d8e1c374dfcfff2b339abd9ea5e99e01478387dd12c4ca501.exe 28 PID 2244 wrote to memory of 2584 2244 ec828ad2b3c4d34d8e1c374dfcfff2b339abd9ea5e99e01478387dd12c4ca501.exe 28 PID 2244 wrote to memory of 2584 2244 ec828ad2b3c4d34d8e1c374dfcfff2b339abd9ea5e99e01478387dd12c4ca501.exe 28 PID 2244 wrote to memory of 2584 2244 ec828ad2b3c4d34d8e1c374dfcfff2b339abd9ea5e99e01478387dd12c4ca501.exe 28 PID 2244 wrote to memory of 2584 2244 ec828ad2b3c4d34d8e1c374dfcfff2b339abd9ea5e99e01478387dd12c4ca501.exe 28 PID 2244 wrote to memory of 2584 2244 ec828ad2b3c4d34d8e1c374dfcfff2b339abd9ea5e99e01478387dd12c4ca501.exe 28 PID 2244 wrote to memory of 2584 2244 ec828ad2b3c4d34d8e1c374dfcfff2b339abd9ea5e99e01478387dd12c4ca501.exe 28 PID 2244 wrote to memory of 2584 2244 ec828ad2b3c4d34d8e1c374dfcfff2b339abd9ea5e99e01478387dd12c4ca501.exe 28 PID 2244 wrote to memory of 2584 2244 ec828ad2b3c4d34d8e1c374dfcfff2b339abd9ea5e99e01478387dd12c4ca501.exe 28 PID 2244 wrote to memory of 2584 2244 ec828ad2b3c4d34d8e1c374dfcfff2b339abd9ea5e99e01478387dd12c4ca501.exe 28 PID 2244 wrote to memory of 2584 2244 ec828ad2b3c4d34d8e1c374dfcfff2b339abd9ea5e99e01478387dd12c4ca501.exe 28 PID 2244 wrote to memory of 2584 2244 ec828ad2b3c4d34d8e1c374dfcfff2b339abd9ea5e99e01478387dd12c4ca501.exe 28 PID 2244 wrote to memory of 2584 2244 ec828ad2b3c4d34d8e1c374dfcfff2b339abd9ea5e99e01478387dd12c4ca501.exe 28 PID 2244 wrote to memory of 2400 2244 ec828ad2b3c4d34d8e1c374dfcfff2b339abd9ea5e99e01478387dd12c4ca501.exe 29 PID 2244 wrote to memory of 2400 2244 ec828ad2b3c4d34d8e1c374dfcfff2b339abd9ea5e99e01478387dd12c4ca501.exe 29 PID 2244 wrote to memory of 2400 2244 ec828ad2b3c4d34d8e1c374dfcfff2b339abd9ea5e99e01478387dd12c4ca501.exe 29 PID 2244 wrote to memory of 2400 2244 ec828ad2b3c4d34d8e1c374dfcfff2b339abd9ea5e99e01478387dd12c4ca501.exe 29 PID 2584 wrote to memory of 2036 2584 AppLaunch.exe 30 PID 2584 wrote to memory of 2036 2584 AppLaunch.exe 30 PID 2584 wrote to memory of 2036 2584 AppLaunch.exe 30 PID 2584 wrote to memory of 2036 2584 AppLaunch.exe 30 PID 2584 wrote to memory of 2036 2584 AppLaunch.exe 30 PID 2584 wrote to memory of 2036 2584 AppLaunch.exe 30 PID 2584 wrote to memory of 2036 2584 AppLaunch.exe 30
Processes
-
C:\Users\Admin\AppData\Local\Temp\ec828ad2b3c4d34d8e1c374dfcfff2b339abd9ea5e99e01478387dd12c4ca501.exe"C:\Users\Admin\AppData\Local\Temp\ec828ad2b3c4d34d8e1c374dfcfff2b339abd9ea5e99e01478387dd12c4ca501.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2244 -
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:2584 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2584 -s 1963⤵
- Program crash
PID:2036
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2244 -s 922⤵
- Program crash
PID:2400
-