Analysis
-
max time kernel
46s -
max time network
51s -
platform
windows7_x64 -
resource
win7-20230831-en -
resource tags
arch:x64arch:x86image:win7-20230831-enlocale:en-usos:windows7-x64system -
submitted
11/10/2023, 06:01
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
85cea14c62d038eab11954c093b9a7ef52c99084fa3a822b50b1d86d406fbfef.exe
Resource
win7-20230831-en
5 signatures
150 seconds
General
-
Target
85cea14c62d038eab11954c093b9a7ef52c99084fa3a822b50b1d86d406fbfef.exe
-
Size
356KB
-
MD5
53ebf495e825c5ae181438c5a7dc7343
-
SHA1
ea99b79d5896b5d797b18afbf3a3fbb26bc41859
-
SHA256
85cea14c62d038eab11954c093b9a7ef52c99084fa3a822b50b1d86d406fbfef
-
SHA512
11b5c8186930e0a9dd98a08f61c1430e2236cd823337e64dd00bf17e19cdd66e66ef6b826c7a14cb18c651c8f7a9dd50a274809515a606345384fdf5bc93fcd9
-
SSDEEP
6144:w2TeW/s5GqrO5aXnfEGIXWPvZAOWyzCZUixJxn4CL2zjvoELP4Vs0BC+:CmcGqrOk86xNCZUixJxn92HTL8s0BC+
Malware Config
Signatures
-
Detect Mystic stealer payload 6 IoCs
resource yara_rule behavioral1/memory/2628-9-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2628-7-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2628-5-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2628-3-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2628-11-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2628-13-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2952 set thread context of 2628 2952 85cea14c62d038eab11954c093b9a7ef52c99084fa3a822b50b1d86d406fbfef.exe 29 -
Program crash 2 IoCs
pid pid_target Process procid_target 2452 2952 WerFault.exe 20 1632 2628 WerFault.exe 29 -
Suspicious use of WriteProcessMemory 25 IoCs
description pid Process procid_target PID 2952 wrote to memory of 2628 2952 85cea14c62d038eab11954c093b9a7ef52c99084fa3a822b50b1d86d406fbfef.exe 29 PID 2952 wrote to memory of 2628 2952 85cea14c62d038eab11954c093b9a7ef52c99084fa3a822b50b1d86d406fbfef.exe 29 PID 2952 wrote to memory of 2628 2952 85cea14c62d038eab11954c093b9a7ef52c99084fa3a822b50b1d86d406fbfef.exe 29 PID 2952 wrote to memory of 2628 2952 85cea14c62d038eab11954c093b9a7ef52c99084fa3a822b50b1d86d406fbfef.exe 29 PID 2952 wrote to memory of 2628 2952 85cea14c62d038eab11954c093b9a7ef52c99084fa3a822b50b1d86d406fbfef.exe 29 PID 2952 wrote to memory of 2628 2952 85cea14c62d038eab11954c093b9a7ef52c99084fa3a822b50b1d86d406fbfef.exe 29 PID 2952 wrote to memory of 2628 2952 85cea14c62d038eab11954c093b9a7ef52c99084fa3a822b50b1d86d406fbfef.exe 29 PID 2952 wrote to memory of 2628 2952 85cea14c62d038eab11954c093b9a7ef52c99084fa3a822b50b1d86d406fbfef.exe 29 PID 2952 wrote to memory of 2628 2952 85cea14c62d038eab11954c093b9a7ef52c99084fa3a822b50b1d86d406fbfef.exe 29 PID 2952 wrote to memory of 2628 2952 85cea14c62d038eab11954c093b9a7ef52c99084fa3a822b50b1d86d406fbfef.exe 29 PID 2952 wrote to memory of 2628 2952 85cea14c62d038eab11954c093b9a7ef52c99084fa3a822b50b1d86d406fbfef.exe 29 PID 2952 wrote to memory of 2628 2952 85cea14c62d038eab11954c093b9a7ef52c99084fa3a822b50b1d86d406fbfef.exe 29 PID 2952 wrote to memory of 2628 2952 85cea14c62d038eab11954c093b9a7ef52c99084fa3a822b50b1d86d406fbfef.exe 29 PID 2952 wrote to memory of 2628 2952 85cea14c62d038eab11954c093b9a7ef52c99084fa3a822b50b1d86d406fbfef.exe 29 PID 2952 wrote to memory of 2452 2952 85cea14c62d038eab11954c093b9a7ef52c99084fa3a822b50b1d86d406fbfef.exe 30 PID 2952 wrote to memory of 2452 2952 85cea14c62d038eab11954c093b9a7ef52c99084fa3a822b50b1d86d406fbfef.exe 30 PID 2952 wrote to memory of 2452 2952 85cea14c62d038eab11954c093b9a7ef52c99084fa3a822b50b1d86d406fbfef.exe 30 PID 2952 wrote to memory of 2452 2952 85cea14c62d038eab11954c093b9a7ef52c99084fa3a822b50b1d86d406fbfef.exe 30 PID 2628 wrote to memory of 1632 2628 AppLaunch.exe 31 PID 2628 wrote to memory of 1632 2628 AppLaunch.exe 31 PID 2628 wrote to memory of 1632 2628 AppLaunch.exe 31 PID 2628 wrote to memory of 1632 2628 AppLaunch.exe 31 PID 2628 wrote to memory of 1632 2628 AppLaunch.exe 31 PID 2628 wrote to memory of 1632 2628 AppLaunch.exe 31 PID 2628 wrote to memory of 1632 2628 AppLaunch.exe 31
Processes
-
C:\Users\Admin\AppData\Local\Temp\85cea14c62d038eab11954c093b9a7ef52c99084fa3a822b50b1d86d406fbfef.exe"C:\Users\Admin\AppData\Local\Temp\85cea14c62d038eab11954c093b9a7ef52c99084fa3a822b50b1d86d406fbfef.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2952 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵
- Suspicious use of WriteProcessMemory
PID:2628 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2628 -s 1963⤵
- Program crash
PID:1632
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2952 -s 762⤵
- Program crash
PID:2452
-