Analysis
-
max time kernel
118s -
max time network
138s -
platform
windows7_x64 -
resource
win7-20230831-en -
resource tags
arch:x64arch:x86image:win7-20230831-enlocale:en-usos:windows7-x64system -
submitted
13-10-2023 04:25
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
b1fb533ebaf2186ec97735f6ab6c54b5449b035a2746796cf726f014a73a86a5.exe
Resource
win7-20230831-en
windows7-x64
5 signatures
150 seconds
General
-
Target
b1fb533ebaf2186ec97735f6ab6c54b5449b035a2746796cf726f014a73a86a5.exe
-
Size
358KB
-
MD5
6b806a33b04641253dfe8f1b77234755
-
SHA1
1285197612530f96b32f8207b45ec12262064c67
-
SHA256
b1fb533ebaf2186ec97735f6ab6c54b5449b035a2746796cf726f014a73a86a5
-
SHA512
4862501ab0ce37d1fe4bca60f9bd40933d7fe5df8874f985f2cb18b292ec2acde1c23612c44e8198bcc9ca3fd2caa8bc7d03b460e05e3bb1d35b553605abbd05
-
SSDEEP
6144:T/DXR/bOEHHkwxOSeyCKrJz4AOIpJZ8+RHYP0K/28fi:jDX1aEHEw94CpJZ8+f8fi
Malware Config
Signatures
-
Detect Mystic stealer payload 6 IoCs
resource yara_rule behavioral1/memory/2796-3-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2796-4-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2796-5-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2796-7-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2796-9-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2796-11-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2764 set thread context of 2796 2764 b1fb533ebaf2186ec97735f6ab6c54b5449b035a2746796cf726f014a73a86a5.exe 30 -
Program crash 1 IoCs
pid pid_target Process procid_target 2752 2796 WerFault.exe 30 -
Suspicious use of WriteProcessMemory 21 IoCs
description pid Process procid_target PID 2764 wrote to memory of 2796 2764 b1fb533ebaf2186ec97735f6ab6c54b5449b035a2746796cf726f014a73a86a5.exe 30 PID 2764 wrote to memory of 2796 2764 b1fb533ebaf2186ec97735f6ab6c54b5449b035a2746796cf726f014a73a86a5.exe 30 PID 2764 wrote to memory of 2796 2764 b1fb533ebaf2186ec97735f6ab6c54b5449b035a2746796cf726f014a73a86a5.exe 30 PID 2764 wrote to memory of 2796 2764 b1fb533ebaf2186ec97735f6ab6c54b5449b035a2746796cf726f014a73a86a5.exe 30 PID 2764 wrote to memory of 2796 2764 b1fb533ebaf2186ec97735f6ab6c54b5449b035a2746796cf726f014a73a86a5.exe 30 PID 2764 wrote to memory of 2796 2764 b1fb533ebaf2186ec97735f6ab6c54b5449b035a2746796cf726f014a73a86a5.exe 30 PID 2764 wrote to memory of 2796 2764 b1fb533ebaf2186ec97735f6ab6c54b5449b035a2746796cf726f014a73a86a5.exe 30 PID 2764 wrote to memory of 2796 2764 b1fb533ebaf2186ec97735f6ab6c54b5449b035a2746796cf726f014a73a86a5.exe 30 PID 2764 wrote to memory of 2796 2764 b1fb533ebaf2186ec97735f6ab6c54b5449b035a2746796cf726f014a73a86a5.exe 30 PID 2764 wrote to memory of 2796 2764 b1fb533ebaf2186ec97735f6ab6c54b5449b035a2746796cf726f014a73a86a5.exe 30 PID 2764 wrote to memory of 2796 2764 b1fb533ebaf2186ec97735f6ab6c54b5449b035a2746796cf726f014a73a86a5.exe 30 PID 2764 wrote to memory of 2796 2764 b1fb533ebaf2186ec97735f6ab6c54b5449b035a2746796cf726f014a73a86a5.exe 30 PID 2764 wrote to memory of 2796 2764 b1fb533ebaf2186ec97735f6ab6c54b5449b035a2746796cf726f014a73a86a5.exe 30 PID 2764 wrote to memory of 2796 2764 b1fb533ebaf2186ec97735f6ab6c54b5449b035a2746796cf726f014a73a86a5.exe 30 PID 2796 wrote to memory of 2752 2796 AppLaunch.exe 31 PID 2796 wrote to memory of 2752 2796 AppLaunch.exe 31 PID 2796 wrote to memory of 2752 2796 AppLaunch.exe 31 PID 2796 wrote to memory of 2752 2796 AppLaunch.exe 31 PID 2796 wrote to memory of 2752 2796 AppLaunch.exe 31 PID 2796 wrote to memory of 2752 2796 AppLaunch.exe 31 PID 2796 wrote to memory of 2752 2796 AppLaunch.exe 31
Processes
-
C:\Users\Admin\AppData\Local\Temp\b1fb533ebaf2186ec97735f6ab6c54b5449b035a2746796cf726f014a73a86a5.exe"C:\Users\Admin\AppData\Local\Temp\b1fb533ebaf2186ec97735f6ab6c54b5449b035a2746796cf726f014a73a86a5.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2764 -
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:2796 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2796 -s 1963⤵
- Program crash
PID:2752
-
-