Analysis
-
max time kernel
163s -
max time network
178s -
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:10
Static task
static1
Behavioral task
behavioral1
Sample
b22be0c777ed1cf28efb837a32be0f6e1d7871ff3e02e7c6e96a3605321feaa8.exe
Resource
win7-20230831-en
windows7-x64
3 signatures
150 seconds
General
-
Target
b22be0c777ed1cf28efb837a32be0f6e1d7871ff3e02e7c6e96a3605321feaa8.exe
-
Size
396KB
-
MD5
355e77edf624035bf7543af28b08e80b
-
SHA1
7389af1e18653dca964bed93a1422f80be5033ec
-
SHA256
b22be0c777ed1cf28efb837a32be0f6e1d7871ff3e02e7c6e96a3605321feaa8
-
SHA512
455f29dc8739484dff8a53e5c59da3f7bd7af5b21979f16d330b057be9a58730a78d46b3ec0fe91bd35ab9dcdf347c96e9d4199ff8cdf312d6b44aad2565a950
-
SSDEEP
6144:pN/hUOqW5XJ6EDOpvOCm5MNuAO41hH+XXKuJa/Jiyzdv1Sszxqwh:pN5dqW5sEe2uuO1hcQwypvss0wh
Malware Config
Extracted
Family
mystic
C2
http://5.42.92.211/loghub/master
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2380 set thread context of 1924 2380 b22be0c777ed1cf28efb837a32be0f6e1d7871ff3e02e7c6e96a3605321feaa8.exe 86 -
Program crash 1 IoCs
pid pid_target Process procid_target 256 2380 WerFault.exe 83 -
Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 2380 wrote to memory of 1924 2380 b22be0c777ed1cf28efb837a32be0f6e1d7871ff3e02e7c6e96a3605321feaa8.exe 86 PID 2380 wrote to memory of 1924 2380 b22be0c777ed1cf28efb837a32be0f6e1d7871ff3e02e7c6e96a3605321feaa8.exe 86 PID 2380 wrote to memory of 1924 2380 b22be0c777ed1cf28efb837a32be0f6e1d7871ff3e02e7c6e96a3605321feaa8.exe 86 PID 2380 wrote to memory of 1924 2380 b22be0c777ed1cf28efb837a32be0f6e1d7871ff3e02e7c6e96a3605321feaa8.exe 86 PID 2380 wrote to memory of 1924 2380 b22be0c777ed1cf28efb837a32be0f6e1d7871ff3e02e7c6e96a3605321feaa8.exe 86 PID 2380 wrote to memory of 1924 2380 b22be0c777ed1cf28efb837a32be0f6e1d7871ff3e02e7c6e96a3605321feaa8.exe 86 PID 2380 wrote to memory of 1924 2380 b22be0c777ed1cf28efb837a32be0f6e1d7871ff3e02e7c6e96a3605321feaa8.exe 86 PID 2380 wrote to memory of 1924 2380 b22be0c777ed1cf28efb837a32be0f6e1d7871ff3e02e7c6e96a3605321feaa8.exe 86 PID 2380 wrote to memory of 1924 2380 b22be0c777ed1cf28efb837a32be0f6e1d7871ff3e02e7c6e96a3605321feaa8.exe 86 PID 2380 wrote to memory of 1924 2380 b22be0c777ed1cf28efb837a32be0f6e1d7871ff3e02e7c6e96a3605321feaa8.exe 86
Processes
-
C:\Users\Admin\AppData\Local\Temp\b22be0c777ed1cf28efb837a32be0f6e1d7871ff3e02e7c6e96a3605321feaa8.exe"C:\Users\Admin\AppData\Local\Temp\b22be0c777ed1cf28efb837a32be0f6e1d7871ff3e02e7c6e96a3605321feaa8.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2380 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:1924
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2380 -s 2442⤵
- Program crash
PID:256
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 444 -p 2380 -ip 23801⤵PID:100