mystic | 5570d8ea68fe9044b2329528c87832c684b019545ba904c1666f5a6014b4ed90

Analysis

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

arch:x64arch:x86image:win10-20230915-enlocale:en-usos:windows10-1703-x64system
submitted
30-09-2023 07:46

Target

5570d8ea68fe9044b2329528c87832c684b019545ba904c1666f5a6014b4ed90.exe
Size

356KB
MD5

aea8431cb8462e4ad32de6c2e0643cd3
SHA1

a5e9749521120a5692989873c8ba1102930e1ed4
SHA256

5570d8ea68fe9044b2329528c87832c684b019545ba904c1666f5a6014b4ed90
SHA512

c2847b08c0a278259ad0a026a8c6a4a8a8771e719f79a254c417de9afef7b5eb39e57fc796116f18ea2e695f06adaf2bdc573af45d6d93f4d7d6a487214e2644
SSDEEP

6144:siTeW/s5GqrO5aXnfEGIXWPvZAOzyIkM+s2TWEltyDgVs0BC+:ymcGqrOk86xz2rTs0BC+

Score

10^/10

mystic stealer

Suspicious use of SetThreadContext 1 IoCs

description	pid	Process	procid_target
PID 4408 set thread context of 884	4408	5570d8ea68fe9044b2329528c87832c684b019545ba904c1666f5a6014b4ed90.exe	72

Program crash 1 IoCs

pid	pid_target	Process	procid_target
4552	4408	WerFault.exe	69

Suspicious use of WriteProcessMemory 13 IoCs

description	pid	Process	procid_target
PID 4408 wrote to memory of 2016	4408	5570d8ea68fe9044b2329528c87832c684b019545ba904c1666f5a6014b4ed90.exe	71
PID 4408 wrote to memory of 2016	4408	5570d8ea68fe9044b2329528c87832c684b019545ba904c1666f5a6014b4ed90.exe	71
PID 4408 wrote to memory of 2016	4408	5570d8ea68fe9044b2329528c87832c684b019545ba904c1666f5a6014b4ed90.exe	71
PID 4408 wrote to memory of 884	4408	5570d8ea68fe9044b2329528c87832c684b019545ba904c1666f5a6014b4ed90.exe	72
PID 4408 wrote to memory of 884	4408	5570d8ea68fe9044b2329528c87832c684b019545ba904c1666f5a6014b4ed90.exe	72
PID 4408 wrote to memory of 884	4408	5570d8ea68fe9044b2329528c87832c684b019545ba904c1666f5a6014b4ed90.exe	72
PID 4408 wrote to memory of 884	4408	5570d8ea68fe9044b2329528c87832c684b019545ba904c1666f5a6014b4ed90.exe	72
PID 4408 wrote to memory of 884	4408	5570d8ea68fe9044b2329528c87832c684b019545ba904c1666f5a6014b4ed90.exe	72
PID 4408 wrote to memory of 884	4408	5570d8ea68fe9044b2329528c87832c684b019545ba904c1666f5a6014b4ed90.exe	72
PID 4408 wrote to memory of 884	4408	5570d8ea68fe9044b2329528c87832c684b019545ba904c1666f5a6014b4ed90.exe	72
PID 4408 wrote to memory of 884	4408	5570d8ea68fe9044b2329528c87832c684b019545ba904c1666f5a6014b4ed90.exe	72
PID 4408 wrote to memory of 884	4408	5570d8ea68fe9044b2329528c87832c684b019545ba904c1666f5a6014b4ed90.exe	72
PID 4408 wrote to memory of 884	4408	5570d8ea68fe9044b2329528c87832c684b019545ba904c1666f5a6014b4ed90.exe	72

C:\Users\Admin\AppData\Local\Temp\5570d8ea68fe9044b2329528c87832c684b019545ba904c1666f5a6014b4ed90.exe
"C:\Users\Admin\AppData\Local\Temp\5570d8ea68fe9044b2329528c87832c684b019545ba904c1666f5a6014b4ed90.exe"
1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:4408
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:2016
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:884
- C:\Windows\SysWOW64\WerFault.exe
  C:\Windows\SysWOW64\WerFault.exe -u -p 4408 -s 268
  2⤵
  - Program crash
  PID:4552

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

Filesize
160KB

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

Filesize
160KB

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

Filesize
160KB

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

Filesize
160KB

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

Filesize
160KB

Download