Analysis
-
max time kernel
122s -
max time network
136s -
platform
windows7_x64 -
resource
win7-20230831-en -
resource tags
arch:x64arch:x86image:win7-20230831-enlocale:en-usos:windows7-x64system -
submitted
11-10-2023 11:28
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
c39c0e650c53272ccb5deb07ac22416ac8b366d795cd33e9ec1f7ca8765cd8b1.exe
Resource
win7-20230831-en
windows7-x64
5 signatures
150 seconds
General
-
Target
c39c0e650c53272ccb5deb07ac22416ac8b366d795cd33e9ec1f7ca8765cd8b1.exe
-
Size
346KB
-
MD5
d0db1d7ea0a6cd39a1c236f02ce76cf6
-
SHA1
a9993a0948ef1252d333ce4682cf3c637b44e407
-
SHA256
c39c0e650c53272ccb5deb07ac22416ac8b366d795cd33e9ec1f7ca8765cd8b1
-
SHA512
9541db09eab8d1880f69aaccf43042f8d290104b314e34cc43a34e25f33d5e0540040949f1ff9eb4f13754616073a8bbf5b23ba5fe43c827875c48c1967fa4ef
-
SSDEEP
6144:K/CFljS9PgGzqLHvw1t6mAOGm3S212JoBfByhUBeyer3viKC:K/mS9PgGimY+J1269BxwiKC
Malware Config
Extracted
Family
mystic
C2
http://5.42.92.211/loghub/master
Signatures
-
Detect Mystic stealer payload 9 IoCs
resource yara_rule behavioral1/memory/2744-6-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2744-8-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2744-10-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2744-13-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2744-15-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2744-17-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2744-18-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2744-19-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2744-20-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2080 set thread context of 2744 2080 c39c0e650c53272ccb5deb07ac22416ac8b366d795cd33e9ec1f7ca8765cd8b1.exe 31 -
Program crash 1 IoCs
pid pid_target Process procid_target 3068 2080 WerFault.exe 17 -
Suspicious use of WriteProcessMemory 18 IoCs
description pid Process procid_target PID 2080 wrote to memory of 2744 2080 c39c0e650c53272ccb5deb07ac22416ac8b366d795cd33e9ec1f7ca8765cd8b1.exe 31 PID 2080 wrote to memory of 2744 2080 c39c0e650c53272ccb5deb07ac22416ac8b366d795cd33e9ec1f7ca8765cd8b1.exe 31 PID 2080 wrote to memory of 2744 2080 c39c0e650c53272ccb5deb07ac22416ac8b366d795cd33e9ec1f7ca8765cd8b1.exe 31 PID 2080 wrote to memory of 2744 2080 c39c0e650c53272ccb5deb07ac22416ac8b366d795cd33e9ec1f7ca8765cd8b1.exe 31 PID 2080 wrote to memory of 2744 2080 c39c0e650c53272ccb5deb07ac22416ac8b366d795cd33e9ec1f7ca8765cd8b1.exe 31 PID 2080 wrote to memory of 2744 2080 c39c0e650c53272ccb5deb07ac22416ac8b366d795cd33e9ec1f7ca8765cd8b1.exe 31 PID 2080 wrote to memory of 2744 2080 c39c0e650c53272ccb5deb07ac22416ac8b366d795cd33e9ec1f7ca8765cd8b1.exe 31 PID 2080 wrote to memory of 2744 2080 c39c0e650c53272ccb5deb07ac22416ac8b366d795cd33e9ec1f7ca8765cd8b1.exe 31 PID 2080 wrote to memory of 2744 2080 c39c0e650c53272ccb5deb07ac22416ac8b366d795cd33e9ec1f7ca8765cd8b1.exe 31 PID 2080 wrote to memory of 2744 2080 c39c0e650c53272ccb5deb07ac22416ac8b366d795cd33e9ec1f7ca8765cd8b1.exe 31 PID 2080 wrote to memory of 2744 2080 c39c0e650c53272ccb5deb07ac22416ac8b366d795cd33e9ec1f7ca8765cd8b1.exe 31 PID 2080 wrote to memory of 2744 2080 c39c0e650c53272ccb5deb07ac22416ac8b366d795cd33e9ec1f7ca8765cd8b1.exe 31 PID 2080 wrote to memory of 2744 2080 c39c0e650c53272ccb5deb07ac22416ac8b366d795cd33e9ec1f7ca8765cd8b1.exe 31 PID 2080 wrote to memory of 2744 2080 c39c0e650c53272ccb5deb07ac22416ac8b366d795cd33e9ec1f7ca8765cd8b1.exe 31 PID 2080 wrote to memory of 3068 2080 c39c0e650c53272ccb5deb07ac22416ac8b366d795cd33e9ec1f7ca8765cd8b1.exe 32 PID 2080 wrote to memory of 3068 2080 c39c0e650c53272ccb5deb07ac22416ac8b366d795cd33e9ec1f7ca8765cd8b1.exe 32 PID 2080 wrote to memory of 3068 2080 c39c0e650c53272ccb5deb07ac22416ac8b366d795cd33e9ec1f7ca8765cd8b1.exe 32 PID 2080 wrote to memory of 3068 2080 c39c0e650c53272ccb5deb07ac22416ac8b366d795cd33e9ec1f7ca8765cd8b1.exe 32
Processes
-
C:\Users\Admin\AppData\Local\Temp\c39c0e650c53272ccb5deb07ac22416ac8b366d795cd33e9ec1f7ca8765cd8b1.exe"C:\Users\Admin\AppData\Local\Temp\c39c0e650c53272ccb5deb07ac22416ac8b366d795cd33e9ec1f7ca8765cd8b1.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2080 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:2744
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2080 -s 1202⤵
- Program crash
PID:3068
-