mystic | d3bf8e89033d6d5c4e910b1e8edd75f9252b4915ca79819250835aeb5f100729

Analysis

max time kernel
156s
max time network
176s
platform
windows10-2004_x64
resource
win10v2004-20230915-en
resource tags

arch:x64arch:x86image:win10v2004-20230915-enlocale:en-usos:windows10-2004-x64system
submitted
12-10-2023 01:11

Target

d3bf8e89033d6d5c4e910b1e8edd75f9252b4915ca79819250835aeb5f100729.exe
Size

364KB
MD5

80852e1ef80a7c4eb56a78554be11a37
SHA1

ae5f358ddb1c01668d02ade390a805f0c1ed209d
SHA256

d3bf8e89033d6d5c4e910b1e8edd75f9252b4915ca79819250835aeb5f100729
SHA512

5d52831352b9b0026b3fb68a497ae919cd49ece58bc46908bd3095e9fd5ca268940004d76bba4fe988543b7618900e1174f468501d7472ac65cc873391aaa1ba
SSDEEP

6144:qzc46fuYXChoQTjlFgLuCY1dRuAO6T4ozYIUv2wg9ct1U5B5gjhAsw8y0:qZYzXChdTbv1buE4uzFwg9ctiBq1w8y

Score

10^/10

mystic stealer

Family

mystic

http://5.42.92.211/loghub/master

Suspicious use of SetThreadContext 1 IoCs

description	pid	Process	procid_target
PID 3600 set thread context of 3892	3600	d3bf8e89033d6d5c4e910b1e8edd75f9252b4915ca79819250835aeb5f100729.exe	87

Program crash 1 IoCs

pid	pid_target	Process	procid_target
4940	3600	WerFault.exe	84

Suspicious use of WriteProcessMemory 13 IoCs

description	pid	Process	procid_target
PID 3600 wrote to memory of 908	3600	d3bf8e89033d6d5c4e910b1e8edd75f9252b4915ca79819250835aeb5f100729.exe	86
PID 3600 wrote to memory of 908	3600	d3bf8e89033d6d5c4e910b1e8edd75f9252b4915ca79819250835aeb5f100729.exe	86
PID 3600 wrote to memory of 908	3600	d3bf8e89033d6d5c4e910b1e8edd75f9252b4915ca79819250835aeb5f100729.exe	86
PID 3600 wrote to memory of 3892	3600	d3bf8e89033d6d5c4e910b1e8edd75f9252b4915ca79819250835aeb5f100729.exe	87
PID 3600 wrote to memory of 3892	3600	d3bf8e89033d6d5c4e910b1e8edd75f9252b4915ca79819250835aeb5f100729.exe	87
PID 3600 wrote to memory of 3892	3600	d3bf8e89033d6d5c4e910b1e8edd75f9252b4915ca79819250835aeb5f100729.exe	87
PID 3600 wrote to memory of 3892	3600	d3bf8e89033d6d5c4e910b1e8edd75f9252b4915ca79819250835aeb5f100729.exe	87
PID 3600 wrote to memory of 3892	3600	d3bf8e89033d6d5c4e910b1e8edd75f9252b4915ca79819250835aeb5f100729.exe	87
PID 3600 wrote to memory of 3892	3600	d3bf8e89033d6d5c4e910b1e8edd75f9252b4915ca79819250835aeb5f100729.exe	87
PID 3600 wrote to memory of 3892	3600	d3bf8e89033d6d5c4e910b1e8edd75f9252b4915ca79819250835aeb5f100729.exe	87
PID 3600 wrote to memory of 3892	3600	d3bf8e89033d6d5c4e910b1e8edd75f9252b4915ca79819250835aeb5f100729.exe	87
PID 3600 wrote to memory of 3892	3600	d3bf8e89033d6d5c4e910b1e8edd75f9252b4915ca79819250835aeb5f100729.exe	87
PID 3600 wrote to memory of 3892	3600	d3bf8e89033d6d5c4e910b1e8edd75f9252b4915ca79819250835aeb5f100729.exe	87

C:\Users\Admin\AppData\Local\Temp\d3bf8e89033d6d5c4e910b1e8edd75f9252b4915ca79819250835aeb5f100729.exe
"C:\Users\Admin\AppData\Local\Temp\d3bf8e89033d6d5c4e910b1e8edd75f9252b4915ca79819250835aeb5f100729.exe"
1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:3600
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:908
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:3892
- C:\Windows\SysWOW64\WerFault.exe
  C:\Windows\SysWOW64\WerFault.exe -u -p 3600 -s 236
  2⤵
  - Program crash
  PID:4940

C:\Windows\SysWOW64\WerFault.exe
C:\Windows\SysWOW64\WerFault.exe -pss -s 444 -p 3600 -ip 3600
1⤵
PID:1976

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

Filesize
176KB

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

Filesize
176KB

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

Filesize
176KB

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

Filesize
176KB

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

Filesize
176KB

Download