Analysis
-
max time kernel
119s -
max time network
132s -
platform
windows10_x64 -
resource
win10-en-20211208 -
submitted
27-01-2022 21:32
Static task
static1
Behavioral task
behavioral1
Sample
1fd74e431f84ab00ad62620141b53491c450b3d6c71dc0fe8ff0dbc47ea304a3.exe
Resource
win7-en-20211208
Behavioral task
behavioral2
Sample
1fd74e431f84ab00ad62620141b53491c450b3d6c71dc0fe8ff0dbc47ea304a3.exe
Resource
win10-en-20211208
General
-
Target
1fd74e431f84ab00ad62620141b53491c450b3d6c71dc0fe8ff0dbc47ea304a3.exe
-
Size
857KB
-
MD5
10e2d3cb3e7b746b352f280e0ac1d2d4
-
SHA1
855c4ba7467dfc75a38013fb7fed7da287fe5170
-
SHA256
1fd74e431f84ab00ad62620141b53491c450b3d6c71dc0fe8ff0dbc47ea304a3
-
SHA512
e65f82790a51e009d5dc809d5e2e4d112eb257aa2de2dea5e073f38fb9113adbec48f716618fe01f676295a4cdcea1d8fe0bd17f3a9339e6c2039fe953f891d1
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:
1fd74e431f84ab00ad62620141b53491c450b3d6c71dc0fe8ff0dbc47ea304a3.exedescription pid process target process PID 732 set thread context of 2392 732 1fd74e431f84ab00ad62620141b53491c450b3d6c71dc0fe8ff0dbc47ea304a3.exe 1fd74e431f84ab00ad62620141b53491c450b3d6c71dc0fe8ff0dbc47ea304a3.exe -
Program crash 1 IoCs
Processes:
WerFault.exepid pid_target process target process 3968 2392 WerFault.exe 1fd74e431f84ab00ad62620141b53491c450b3d6c71dc0fe8ff0dbc47ea304a3.exe -
Suspicious use of WriteProcessMemory 9 IoCs
Processes:
1fd74e431f84ab00ad62620141b53491c450b3d6c71dc0fe8ff0dbc47ea304a3.exedescription pid process target process PID 732 wrote to memory of 2392 732 1fd74e431f84ab00ad62620141b53491c450b3d6c71dc0fe8ff0dbc47ea304a3.exe 1fd74e431f84ab00ad62620141b53491c450b3d6c71dc0fe8ff0dbc47ea304a3.exe PID 732 wrote to memory of 2392 732 1fd74e431f84ab00ad62620141b53491c450b3d6c71dc0fe8ff0dbc47ea304a3.exe 1fd74e431f84ab00ad62620141b53491c450b3d6c71dc0fe8ff0dbc47ea304a3.exe PID 732 wrote to memory of 2392 732 1fd74e431f84ab00ad62620141b53491c450b3d6c71dc0fe8ff0dbc47ea304a3.exe 1fd74e431f84ab00ad62620141b53491c450b3d6c71dc0fe8ff0dbc47ea304a3.exe PID 732 wrote to memory of 2392 732 1fd74e431f84ab00ad62620141b53491c450b3d6c71dc0fe8ff0dbc47ea304a3.exe 1fd74e431f84ab00ad62620141b53491c450b3d6c71dc0fe8ff0dbc47ea304a3.exe PID 732 wrote to memory of 2392 732 1fd74e431f84ab00ad62620141b53491c450b3d6c71dc0fe8ff0dbc47ea304a3.exe 1fd74e431f84ab00ad62620141b53491c450b3d6c71dc0fe8ff0dbc47ea304a3.exe PID 732 wrote to memory of 2392 732 1fd74e431f84ab00ad62620141b53491c450b3d6c71dc0fe8ff0dbc47ea304a3.exe 1fd74e431f84ab00ad62620141b53491c450b3d6c71dc0fe8ff0dbc47ea304a3.exe PID 732 wrote to memory of 2392 732 1fd74e431f84ab00ad62620141b53491c450b3d6c71dc0fe8ff0dbc47ea304a3.exe 1fd74e431f84ab00ad62620141b53491c450b3d6c71dc0fe8ff0dbc47ea304a3.exe PID 732 wrote to memory of 2392 732 1fd74e431f84ab00ad62620141b53491c450b3d6c71dc0fe8ff0dbc47ea304a3.exe 1fd74e431f84ab00ad62620141b53491c450b3d6c71dc0fe8ff0dbc47ea304a3.exe PID 732 wrote to memory of 2392 732 1fd74e431f84ab00ad62620141b53491c450b3d6c71dc0fe8ff0dbc47ea304a3.exe 1fd74e431f84ab00ad62620141b53491c450b3d6c71dc0fe8ff0dbc47ea304a3.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\1fd74e431f84ab00ad62620141b53491c450b3d6c71dc0fe8ff0dbc47ea304a3.exe"C:\Users\Admin\AppData\Local\Temp\1fd74e431f84ab00ad62620141b53491c450b3d6c71dc0fe8ff0dbc47ea304a3.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
-
C:\Users\Admin\AppData\Local\Temp\1fd74e431f84ab00ad62620141b53491c450b3d6c71dc0fe8ff0dbc47ea304a3.exe"C:\Users\Admin\AppData\Local\Temp\1fd74e431f84ab00ad62620141b53491c450b3d6c71dc0fe8ff0dbc47ea304a3.exe"2⤵
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2392 -s 243⤵
- Program crash