Analysis
-
max time kernel
82s -
max time network
140s -
platform
windows10_x64 -
resource
win10-en-20211208 -
submitted
27-01-2022 21:46
Static task
static1
Behavioral task
behavioral1
Sample
1b2b8cb04b6aca7d35061c7b6337a05b6d74fff7604a5afcd9161650ff55238b.exe
Resource
win7-en-20211208
Behavioral task
behavioral2
Sample
1b2b8cb04b6aca7d35061c7b6337a05b6d74fff7604a5afcd9161650ff55238b.exe
Resource
win10-en-20211208
General
-
Target
1b2b8cb04b6aca7d35061c7b6337a05b6d74fff7604a5afcd9161650ff55238b.exe
-
Size
864KB
-
MD5
17be9811767ee50b75ef86a57b4c901b
-
SHA1
de7a063e554aeaf247654e8ba004df14a7f26edb
-
SHA256
1b2b8cb04b6aca7d35061c7b6337a05b6d74fff7604a5afcd9161650ff55238b
-
SHA512
59212cb1c718df94f8938bad7ae717e3283a14dc8c5cc22b4f4717357337f785559eab6ceefeda2de62f858e0d71e8914a194604015982a5a1ca027bb3210abf
Malware Config
Extracted
metasploit
encoder/call4_dword_xor
Signatures
-
MetaSploit
Detected malicious payload which is part of the Metasploit Framework, likely generated with msfvenom or similar.
-
Suspicious use of SetThreadContext 1 IoCs
Processes:
1b2b8cb04b6aca7d35061c7b6337a05b6d74fff7604a5afcd9161650ff55238b.exedescription pid process target process PID 2536 set thread context of 3576 2536 1b2b8cb04b6aca7d35061c7b6337a05b6d74fff7604a5afcd9161650ff55238b.exe 1b2b8cb04b6aca7d35061c7b6337a05b6d74fff7604a5afcd9161650ff55238b.exe -
Program crash 1 IoCs
Processes:
WerFault.exepid pid_target process target process 1740 3576 WerFault.exe 1b2b8cb04b6aca7d35061c7b6337a05b6d74fff7604a5afcd9161650ff55238b.exe -
Suspicious use of WriteProcessMemory 9 IoCs
Processes:
1b2b8cb04b6aca7d35061c7b6337a05b6d74fff7604a5afcd9161650ff55238b.exedescription pid process target process PID 2536 wrote to memory of 3576 2536 1b2b8cb04b6aca7d35061c7b6337a05b6d74fff7604a5afcd9161650ff55238b.exe 1b2b8cb04b6aca7d35061c7b6337a05b6d74fff7604a5afcd9161650ff55238b.exe PID 2536 wrote to memory of 3576 2536 1b2b8cb04b6aca7d35061c7b6337a05b6d74fff7604a5afcd9161650ff55238b.exe 1b2b8cb04b6aca7d35061c7b6337a05b6d74fff7604a5afcd9161650ff55238b.exe PID 2536 wrote to memory of 3576 2536 1b2b8cb04b6aca7d35061c7b6337a05b6d74fff7604a5afcd9161650ff55238b.exe 1b2b8cb04b6aca7d35061c7b6337a05b6d74fff7604a5afcd9161650ff55238b.exe PID 2536 wrote to memory of 3576 2536 1b2b8cb04b6aca7d35061c7b6337a05b6d74fff7604a5afcd9161650ff55238b.exe 1b2b8cb04b6aca7d35061c7b6337a05b6d74fff7604a5afcd9161650ff55238b.exe PID 2536 wrote to memory of 3576 2536 1b2b8cb04b6aca7d35061c7b6337a05b6d74fff7604a5afcd9161650ff55238b.exe 1b2b8cb04b6aca7d35061c7b6337a05b6d74fff7604a5afcd9161650ff55238b.exe PID 2536 wrote to memory of 3576 2536 1b2b8cb04b6aca7d35061c7b6337a05b6d74fff7604a5afcd9161650ff55238b.exe 1b2b8cb04b6aca7d35061c7b6337a05b6d74fff7604a5afcd9161650ff55238b.exe PID 2536 wrote to memory of 3576 2536 1b2b8cb04b6aca7d35061c7b6337a05b6d74fff7604a5afcd9161650ff55238b.exe 1b2b8cb04b6aca7d35061c7b6337a05b6d74fff7604a5afcd9161650ff55238b.exe PID 2536 wrote to memory of 3576 2536 1b2b8cb04b6aca7d35061c7b6337a05b6d74fff7604a5afcd9161650ff55238b.exe 1b2b8cb04b6aca7d35061c7b6337a05b6d74fff7604a5afcd9161650ff55238b.exe PID 2536 wrote to memory of 3576 2536 1b2b8cb04b6aca7d35061c7b6337a05b6d74fff7604a5afcd9161650ff55238b.exe 1b2b8cb04b6aca7d35061c7b6337a05b6d74fff7604a5afcd9161650ff55238b.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\1b2b8cb04b6aca7d35061c7b6337a05b6d74fff7604a5afcd9161650ff55238b.exe"C:\Users\Admin\AppData\Local\Temp\1b2b8cb04b6aca7d35061c7b6337a05b6d74fff7604a5afcd9161650ff55238b.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
-
C:\Users\Admin\AppData\Local\Temp\1b2b8cb04b6aca7d35061c7b6337a05b6d74fff7604a5afcd9161650ff55238b.exe"C:\Users\Admin\AppData\Local\Temp\1b2b8cb04b6aca7d35061c7b6337a05b6d74fff7604a5afcd9161650ff55238b.exe"2⤵
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3576 -s 243⤵
- Program crash