mystic | 625f46bebd89bacf69362cc16169ae401cc0cbf58766afea1588d9f690feb897

Analysis

max time kernel
127s
max time network
131s
platform
windows10-1703_x64
resource
win10-20230915-en
resource tags

arch:x64arch:x86image:win10-20230915-enlocale:en-usos:windows10-1703-x64system
submitted
01/10/2023, 08:55

Target

625f46bebd89bacf69362cc16169ae401cc0cbf58766afea1588d9f690feb897.exe
Size

276KB
MD5

798c12022e50420bdd65803d916d9349
SHA1

517f82f131a687ac6c22dfe38bb6e4db0885d2e1
SHA256

625f46bebd89bacf69362cc16169ae401cc0cbf58766afea1588d9f690feb897
SHA512

f5d7acd694f5c7d3f0d198d0baac08507cd939d7be577c5eee406b9d8d80da300d9bf9cf540af76749f3ad3d6c2456558d0673de4ec59b2a887a8670677ec8f5
SSDEEP

6144:WhmdKajWpVP06+ZHnmWhC4WknnxrwYqrj:WMKajW2HmMntdcj

Score

10^/10

mystic stealer

Suspicious use of SetThreadContext 1 IoCs

description	pid	Process	procid_target
PID 4972 set thread context of 4756	4972	625f46bebd89bacf69362cc16169ae401cc0cbf58766afea1588d9f690feb897.exe	72

Program crash 1 IoCs

pid	pid_target	Process	procid_target
3980	4972	WerFault.exe	69

Suspicious use of WriteProcessMemory 13 IoCs

description	pid	Process	procid_target
PID 4972 wrote to memory of 5076	4972	625f46bebd89bacf69362cc16169ae401cc0cbf58766afea1588d9f690feb897.exe	71
PID 4972 wrote to memory of 5076	4972	625f46bebd89bacf69362cc16169ae401cc0cbf58766afea1588d9f690feb897.exe	71
PID 4972 wrote to memory of 5076	4972	625f46bebd89bacf69362cc16169ae401cc0cbf58766afea1588d9f690feb897.exe	71
PID 4972 wrote to memory of 4756	4972	625f46bebd89bacf69362cc16169ae401cc0cbf58766afea1588d9f690feb897.exe	72
PID 4972 wrote to memory of 4756	4972	625f46bebd89bacf69362cc16169ae401cc0cbf58766afea1588d9f690feb897.exe	72
PID 4972 wrote to memory of 4756	4972	625f46bebd89bacf69362cc16169ae401cc0cbf58766afea1588d9f690feb897.exe	72
PID 4972 wrote to memory of 4756	4972	625f46bebd89bacf69362cc16169ae401cc0cbf58766afea1588d9f690feb897.exe	72
PID 4972 wrote to memory of 4756	4972	625f46bebd89bacf69362cc16169ae401cc0cbf58766afea1588d9f690feb897.exe	72
PID 4972 wrote to memory of 4756	4972	625f46bebd89bacf69362cc16169ae401cc0cbf58766afea1588d9f690feb897.exe	72
PID 4972 wrote to memory of 4756	4972	625f46bebd89bacf69362cc16169ae401cc0cbf58766afea1588d9f690feb897.exe	72
PID 4972 wrote to memory of 4756	4972	625f46bebd89bacf69362cc16169ae401cc0cbf58766afea1588d9f690feb897.exe	72
PID 4972 wrote to memory of 4756	4972	625f46bebd89bacf69362cc16169ae401cc0cbf58766afea1588d9f690feb897.exe	72
PID 4972 wrote to memory of 4756	4972	625f46bebd89bacf69362cc16169ae401cc0cbf58766afea1588d9f690feb897.exe	72

C:\Users\Admin\AppData\Local\Temp\625f46bebd89bacf69362cc16169ae401cc0cbf58766afea1588d9f690feb897.exe
"C:\Users\Admin\AppData\Local\Temp\625f46bebd89bacf69362cc16169ae401cc0cbf58766afea1588d9f690feb897.exe"
1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:4972
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:5076
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:4756
- C:\Windows\SysWOW64\WerFault.exe
  C:\Windows\SysWOW64\WerFault.exe -u -p 4972 -s 144
  2⤵
  - Program crash
  PID:3980

memory/4756-0-0x0000000000400000-0x0000000000428000-memory.dmp

Filesize
160KB

Download
memory/4756-4-0x0000000000400000-0x0000000000428000-memory.dmp

Filesize
160KB

Download
memory/4756-3-0x0000000000400000-0x0000000000428000-memory.dmp

Filesize
160KB

Download
memory/4756-5-0x0000000000400000-0x0000000000428000-memory.dmp

Filesize
160KB

Download
memory/4756-6-0x0000000000400000-0x0000000000428000-memory.dmp

Filesize
160KB

Download