mystic | 27d9ec4c9e284218eff7b29d75a8c63d928e538fe851a89ab388da30d06d4e21

Analysis

max time kernel
142s
max time network
155s
platform
windows10-2004_x64
resource
win10v2004-20230915-en
resource tags

arch:x64arch:x86image:win10v2004-20230915-enlocale:en-usos:windows10-2004-x64system
submitted
23/09/2023, 01:14

Target

27d9ec4c9e284218eff7b29d75a8c63d928e538fe851a89ab388da30d06d4e21.exe
Size

365KB
MD5

767bf65b38ce2604f2f377dbb83f8560
SHA1

1419ad17e8586556c4e4be7de6c58e33f29d76d3
SHA256

27d9ec4c9e284218eff7b29d75a8c63d928e538fe851a89ab388da30d06d4e21
SHA512

8431a944da1b097ffcdbac783dafdd8b95e30b57cfde6f1a415e543b793489bf1cc74e647924fd0705015375da2d1082437daf794ceb98241c72754eb36c07bb
SSDEEP

6144:CD5frpxdonyq4zaG2u5AOjeK99qECnw9aoyy2U+xquqp:Cdrp0/9u5ZeQQEixquqp

Score

10^/10

mystic stealer

Suspicious use of SetThreadContext 1 IoCs

description	pid	Process	procid_target
PID 2180 set thread context of 408	2180	27d9ec4c9e284218eff7b29d75a8c63d928e538fe851a89ab388da30d06d4e21.exe	93

Program crash 1 IoCs

pid	pid_target	Process	procid_target
2856	2180	WerFault.exe	85

Suspicious use of WriteProcessMemory 13 IoCs

description	pid	Process	procid_target
PID 2180 wrote to memory of 5100	2180	27d9ec4c9e284218eff7b29d75a8c63d928e538fe851a89ab388da30d06d4e21.exe	91
PID 2180 wrote to memory of 5100	2180	27d9ec4c9e284218eff7b29d75a8c63d928e538fe851a89ab388da30d06d4e21.exe	91
PID 2180 wrote to memory of 5100	2180	27d9ec4c9e284218eff7b29d75a8c63d928e538fe851a89ab388da30d06d4e21.exe	91
PID 2180 wrote to memory of 408	2180	27d9ec4c9e284218eff7b29d75a8c63d928e538fe851a89ab388da30d06d4e21.exe	93
PID 2180 wrote to memory of 408	2180	27d9ec4c9e284218eff7b29d75a8c63d928e538fe851a89ab388da30d06d4e21.exe	93
PID 2180 wrote to memory of 408	2180	27d9ec4c9e284218eff7b29d75a8c63d928e538fe851a89ab388da30d06d4e21.exe	93
PID 2180 wrote to memory of 408	2180	27d9ec4c9e284218eff7b29d75a8c63d928e538fe851a89ab388da30d06d4e21.exe	93
PID 2180 wrote to memory of 408	2180	27d9ec4c9e284218eff7b29d75a8c63d928e538fe851a89ab388da30d06d4e21.exe	93
PID 2180 wrote to memory of 408	2180	27d9ec4c9e284218eff7b29d75a8c63d928e538fe851a89ab388da30d06d4e21.exe	93
PID 2180 wrote to memory of 408	2180	27d9ec4c9e284218eff7b29d75a8c63d928e538fe851a89ab388da30d06d4e21.exe	93
PID 2180 wrote to memory of 408	2180	27d9ec4c9e284218eff7b29d75a8c63d928e538fe851a89ab388da30d06d4e21.exe	93
PID 2180 wrote to memory of 408	2180	27d9ec4c9e284218eff7b29d75a8c63d928e538fe851a89ab388da30d06d4e21.exe	93
PID 2180 wrote to memory of 408	2180	27d9ec4c9e284218eff7b29d75a8c63d928e538fe851a89ab388da30d06d4e21.exe	93

C:\Users\Admin\AppData\Local\Temp\27d9ec4c9e284218eff7b29d75a8c63d928e538fe851a89ab388da30d06d4e21.exe
"C:\Users\Admin\AppData\Local\Temp\27d9ec4c9e284218eff7b29d75a8c63d928e538fe851a89ab388da30d06d4e21.exe"
1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2180
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:5100
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:408
- C:\Windows\SysWOW64\WerFault.exe
  C:\Windows\SysWOW64\WerFault.exe -u -p 2180 -s 288
  2⤵
  - Program crash
  PID:2856

C:\Windows\SysWOW64\WerFault.exe
C:\Windows\SysWOW64\WerFault.exe -pss -s 460 -p 2180 -ip 2180
1⤵
PID:944

memory/408-0-0x0000000000400000-0x000000000042C000-memory.dmp

Filesize
176KB

Download
memory/408-1-0x0000000000400000-0x000000000042C000-memory.dmp

Filesize
176KB

Download
memory/408-2-0x0000000000400000-0x000000000042C000-memory.dmp

Filesize
176KB

Download
memory/408-3-0x0000000000400000-0x000000000042C000-memory.dmp

Filesize
176KB

Download
memory/408-4-0x0000000000400000-0x000000000042C000-memory.dmp

Filesize
176KB

Download