mystic | f6116442a2973862c838effc2b1296f0435e1233caf64c32c0d3ae9feb9d2834

Analysis

max time kernel
161s
max time network
171s
platform
windows10-2004_x64
resource
win10v2004-20230915-en
resource tags

arch:x64arch:x86image:win10v2004-20230915-enlocale:en-usos:windows10-2004-x64system
submitted
11/10/2023, 22:19

Target

f6116442a2973862c838effc2b1296f0435e1233caf64c32c0d3ae9feb9d2834_JC.exe
Size

695KB
MD5

ce0aa245546b4388c31e265389630022
SHA1

45a16a59a2047b88942afe8656e439bd18242c37
SHA256

f6116442a2973862c838effc2b1296f0435e1233caf64c32c0d3ae9feb9d2834
SHA512

c9d1f4170c06cf59a2c20f310efbb7c21c052d1f5d494a06e5d4ad92e2c519d16e9641c36f0c0a4193daf1f0fec1ce535930f0b1986b2b22a3d2f8fc8de734c2
SSDEEP

12288:9P/gohZVucQ5qfICJSHSsPe5A96RPYw9l:dgQ7pJCSsPEW4

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 4480 set thread context of 1756	4480	f6116442a2973862c838effc2b1296f0435e1233caf64c32c0d3ae9feb9d2834_JC.exe	94

Program crash 1 IoCs

pid	pid_target	Process	procid_target
4372	4480	WerFault.exe	25

Suspicious use of WriteProcessMemory 13 IoCs

description	pid	Process	procid_target
PID 4480 wrote to memory of 2360	4480	f6116442a2973862c838effc2b1296f0435e1233caf64c32c0d3ae9feb9d2834_JC.exe	93
PID 4480 wrote to memory of 2360	4480	f6116442a2973862c838effc2b1296f0435e1233caf64c32c0d3ae9feb9d2834_JC.exe	93
PID 4480 wrote to memory of 2360	4480	f6116442a2973862c838effc2b1296f0435e1233caf64c32c0d3ae9feb9d2834_JC.exe	93
PID 4480 wrote to memory of 1756	4480	f6116442a2973862c838effc2b1296f0435e1233caf64c32c0d3ae9feb9d2834_JC.exe	94
PID 4480 wrote to memory of 1756	4480	f6116442a2973862c838effc2b1296f0435e1233caf64c32c0d3ae9feb9d2834_JC.exe	94
PID 4480 wrote to memory of 1756	4480	f6116442a2973862c838effc2b1296f0435e1233caf64c32c0d3ae9feb9d2834_JC.exe	94
PID 4480 wrote to memory of 1756	4480	f6116442a2973862c838effc2b1296f0435e1233caf64c32c0d3ae9feb9d2834_JC.exe	94
PID 4480 wrote to memory of 1756	4480	f6116442a2973862c838effc2b1296f0435e1233caf64c32c0d3ae9feb9d2834_JC.exe	94
PID 4480 wrote to memory of 1756	4480	f6116442a2973862c838effc2b1296f0435e1233caf64c32c0d3ae9feb9d2834_JC.exe	94
PID 4480 wrote to memory of 1756	4480	f6116442a2973862c838effc2b1296f0435e1233caf64c32c0d3ae9feb9d2834_JC.exe	94
PID 4480 wrote to memory of 1756	4480	f6116442a2973862c838effc2b1296f0435e1233caf64c32c0d3ae9feb9d2834_JC.exe	94
PID 4480 wrote to memory of 1756	4480	f6116442a2973862c838effc2b1296f0435e1233caf64c32c0d3ae9feb9d2834_JC.exe	94
PID 4480 wrote to memory of 1756	4480	f6116442a2973862c838effc2b1296f0435e1233caf64c32c0d3ae9feb9d2834_JC.exe	94

C:\Users\Admin\AppData\Local\Temp\f6116442a2973862c838effc2b1296f0435e1233caf64c32c0d3ae9feb9d2834_JC.exe
"C:\Users\Admin\AppData\Local\Temp\f6116442a2973862c838effc2b1296f0435e1233caf64c32c0d3ae9feb9d2834_JC.exe"
1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:4480
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:2360
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:1756
- C:\Windows\SysWOW64\WerFault.exe
  C:\Windows\SysWOW64\WerFault.exe -u -p 4480 -s 280
  2⤵
  - Program crash
  PID:4372

C:\Windows\SysWOW64\WerFault.exe
C:\Windows\SysWOW64\WerFault.exe -pss -s 456 -p 4480 -ip 4480
1⤵
PID:1668

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

Filesize
188KB

Download
memory/1756-1-0x0000000000400000-0x000000000042F000-memory.dmp

Filesize
188KB

Download
memory/1756-2-0x0000000000400000-0x000000000042F000-memory.dmp

Filesize
188KB

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

Filesize
188KB

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

Filesize
188KB

Download