mystic | abe102abdc93352259218ae051e905469a5e9f2fc8e3b6e3a34ab1c21ab8a8f3

Analysis

max time kernel
128s
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
22/09/2023, 01:06

Target

abe102abdc93352259218ae051e905469a5e9f2fc8e3b6e3a34ab1c21ab8a8f3.exe
Size

700KB
MD5

588f408e6782f4d1a018a2aa0457b0e2
SHA1

ff7fa8913bd38fb537888010cb6dd7b4f898b851
SHA256

abe102abdc93352259218ae051e905469a5e9f2fc8e3b6e3a34ab1c21ab8a8f3
SHA512

872184e34536c2a89fba968baff2260c94ca46ccc9c1269f0d85e6ae4f6ca423b2f9ce22431fc77599a21f73cbdca93577f760f9ebf8cfa59118790a6c0de4e5
SSDEEP

6144:V6vGALXgBEIy8wluzNcq/PVucQpHeGLB5B0D6kIq+vELg1bAKIABF2h6Vvfr:IHXgFysVucQpHeorOxFeELIAKIABD1r

Score

10^/10

mystic stealer

Suspicious use of SetThreadContext 1 IoCs

description	pid	Process	procid_target
PID 1676 set thread context of 5100	1676	abe102abdc93352259218ae051e905469a5e9f2fc8e3b6e3a34ab1c21ab8a8f3.exe	71

Program crash 1 IoCs

pid	pid_target	Process	procid_target
4688	1676	WerFault.exe	68

Suspicious use of WriteProcessMemory 13 IoCs

description	pid	Process	procid_target
PID 1676 wrote to memory of 2064	1676	abe102abdc93352259218ae051e905469a5e9f2fc8e3b6e3a34ab1c21ab8a8f3.exe	70
PID 1676 wrote to memory of 2064	1676	abe102abdc93352259218ae051e905469a5e9f2fc8e3b6e3a34ab1c21ab8a8f3.exe	70
PID 1676 wrote to memory of 2064	1676	abe102abdc93352259218ae051e905469a5e9f2fc8e3b6e3a34ab1c21ab8a8f3.exe	70
PID 1676 wrote to memory of 5100	1676	abe102abdc93352259218ae051e905469a5e9f2fc8e3b6e3a34ab1c21ab8a8f3.exe	71
PID 1676 wrote to memory of 5100	1676	abe102abdc93352259218ae051e905469a5e9f2fc8e3b6e3a34ab1c21ab8a8f3.exe	71
PID 1676 wrote to memory of 5100	1676	abe102abdc93352259218ae051e905469a5e9f2fc8e3b6e3a34ab1c21ab8a8f3.exe	71
PID 1676 wrote to memory of 5100	1676	abe102abdc93352259218ae051e905469a5e9f2fc8e3b6e3a34ab1c21ab8a8f3.exe	71
PID 1676 wrote to memory of 5100	1676	abe102abdc93352259218ae051e905469a5e9f2fc8e3b6e3a34ab1c21ab8a8f3.exe	71
PID 1676 wrote to memory of 5100	1676	abe102abdc93352259218ae051e905469a5e9f2fc8e3b6e3a34ab1c21ab8a8f3.exe	71
PID 1676 wrote to memory of 5100	1676	abe102abdc93352259218ae051e905469a5e9f2fc8e3b6e3a34ab1c21ab8a8f3.exe	71
PID 1676 wrote to memory of 5100	1676	abe102abdc93352259218ae051e905469a5e9f2fc8e3b6e3a34ab1c21ab8a8f3.exe	71
PID 1676 wrote to memory of 5100	1676	abe102abdc93352259218ae051e905469a5e9f2fc8e3b6e3a34ab1c21ab8a8f3.exe	71
PID 1676 wrote to memory of 5100	1676	abe102abdc93352259218ae051e905469a5e9f2fc8e3b6e3a34ab1c21ab8a8f3.exe	71

C:\Users\Admin\AppData\Local\Temp\abe102abdc93352259218ae051e905469a5e9f2fc8e3b6e3a34ab1c21ab8a8f3.exe
"C:\Users\Admin\AppData\Local\Temp\abe102abdc93352259218ae051e905469a5e9f2fc8e3b6e3a34ab1c21ab8a8f3.exe"
1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:1676
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:2064
- 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\SysWOW64\WerFault.exe
  C:\Windows\SysWOW64\WerFault.exe -u -p 1676 -s 144
  2⤵
  - Program crash
  PID:4688

memory/5100-0-0x0000000000400000-0x000000000042F000-memory.dmp

Filesize
188KB

Download
memory/5100-3-0x0000000000400000-0x000000000042F000-memory.dmp

Filesize
188KB

Download
memory/5100-4-0x0000000000400000-0x000000000042F000-memory.dmp

Filesize
188KB

Download
memory/5100-5-0x0000000000400000-0x000000000042F000-memory.dmp

Filesize
188KB

Download
memory/5100-6-0x0000000000400000-0x000000000042F000-memory.dmp

Filesize
188KB

Download