Analysis
-
max time kernel
119s -
max time network
124s -
platform
windows10_x64 -
resource
win10-en-20211208 -
submitted
27-01-2022 20:39
Static task
static1
Behavioral task
behavioral1
Sample
2fd38911f08f6ebd447c6f7466ea6cbf9dfd472a3fd20b7ac9cdf1d3cbed0e35.exe
Resource
win7-en-20211208
Behavioral task
behavioral2
Sample
2fd38911f08f6ebd447c6f7466ea6cbf9dfd472a3fd20b7ac9cdf1d3cbed0e35.exe
Resource
win10-en-20211208
General
-
Target
2fd38911f08f6ebd447c6f7466ea6cbf9dfd472a3fd20b7ac9cdf1d3cbed0e35.exe
-
Size
1.2MB
-
MD5
3c28605ba9465db98e45a4dc89909304
-
SHA1
0884f9c59ffa2039f3b9ef663cfadf080d00c150
-
SHA256
2fd38911f08f6ebd447c6f7466ea6cbf9dfd472a3fd20b7ac9cdf1d3cbed0e35
-
SHA512
87c03f7fbb010804d4d6c9b69ca6b8b9b8d924cadcf7b4f09125efb8119c2264c8fef8f5a8b9a73c2f232d4c480f7dcdddb7ed1e475b5c17a6ebb35594cca80d
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:
2fd38911f08f6ebd447c6f7466ea6cbf9dfd472a3fd20b7ac9cdf1d3cbed0e35.exedescription pid process target process PID 3280 set thread context of 660 3280 2fd38911f08f6ebd447c6f7466ea6cbf9dfd472a3fd20b7ac9cdf1d3cbed0e35.exe 2fd38911f08f6ebd447c6f7466ea6cbf9dfd472a3fd20b7ac9cdf1d3cbed0e35.exe -
Program crash 1 IoCs
Processes:
WerFault.exepid pid_target process target process 912 660 WerFault.exe 2fd38911f08f6ebd447c6f7466ea6cbf9dfd472a3fd20b7ac9cdf1d3cbed0e35.exe -
Suspicious use of WriteProcessMemory 9 IoCs
Processes:
2fd38911f08f6ebd447c6f7466ea6cbf9dfd472a3fd20b7ac9cdf1d3cbed0e35.exedescription pid process target process PID 3280 wrote to memory of 660 3280 2fd38911f08f6ebd447c6f7466ea6cbf9dfd472a3fd20b7ac9cdf1d3cbed0e35.exe 2fd38911f08f6ebd447c6f7466ea6cbf9dfd472a3fd20b7ac9cdf1d3cbed0e35.exe PID 3280 wrote to memory of 660 3280 2fd38911f08f6ebd447c6f7466ea6cbf9dfd472a3fd20b7ac9cdf1d3cbed0e35.exe 2fd38911f08f6ebd447c6f7466ea6cbf9dfd472a3fd20b7ac9cdf1d3cbed0e35.exe PID 3280 wrote to memory of 660 3280 2fd38911f08f6ebd447c6f7466ea6cbf9dfd472a3fd20b7ac9cdf1d3cbed0e35.exe 2fd38911f08f6ebd447c6f7466ea6cbf9dfd472a3fd20b7ac9cdf1d3cbed0e35.exe PID 3280 wrote to memory of 660 3280 2fd38911f08f6ebd447c6f7466ea6cbf9dfd472a3fd20b7ac9cdf1d3cbed0e35.exe 2fd38911f08f6ebd447c6f7466ea6cbf9dfd472a3fd20b7ac9cdf1d3cbed0e35.exe PID 3280 wrote to memory of 660 3280 2fd38911f08f6ebd447c6f7466ea6cbf9dfd472a3fd20b7ac9cdf1d3cbed0e35.exe 2fd38911f08f6ebd447c6f7466ea6cbf9dfd472a3fd20b7ac9cdf1d3cbed0e35.exe PID 3280 wrote to memory of 660 3280 2fd38911f08f6ebd447c6f7466ea6cbf9dfd472a3fd20b7ac9cdf1d3cbed0e35.exe 2fd38911f08f6ebd447c6f7466ea6cbf9dfd472a3fd20b7ac9cdf1d3cbed0e35.exe PID 3280 wrote to memory of 660 3280 2fd38911f08f6ebd447c6f7466ea6cbf9dfd472a3fd20b7ac9cdf1d3cbed0e35.exe 2fd38911f08f6ebd447c6f7466ea6cbf9dfd472a3fd20b7ac9cdf1d3cbed0e35.exe PID 3280 wrote to memory of 660 3280 2fd38911f08f6ebd447c6f7466ea6cbf9dfd472a3fd20b7ac9cdf1d3cbed0e35.exe 2fd38911f08f6ebd447c6f7466ea6cbf9dfd472a3fd20b7ac9cdf1d3cbed0e35.exe PID 3280 wrote to memory of 660 3280 2fd38911f08f6ebd447c6f7466ea6cbf9dfd472a3fd20b7ac9cdf1d3cbed0e35.exe 2fd38911f08f6ebd447c6f7466ea6cbf9dfd472a3fd20b7ac9cdf1d3cbed0e35.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\2fd38911f08f6ebd447c6f7466ea6cbf9dfd472a3fd20b7ac9cdf1d3cbed0e35.exe"C:\Users\Admin\AppData\Local\Temp\2fd38911f08f6ebd447c6f7466ea6cbf9dfd472a3fd20b7ac9cdf1d3cbed0e35.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
-
C:\Users\Admin\AppData\Local\Temp\2fd38911f08f6ebd447c6f7466ea6cbf9dfd472a3fd20b7ac9cdf1d3cbed0e35.exe"C:\Users\Admin\AppData\Local\Temp\2fd38911f08f6ebd447c6f7466ea6cbf9dfd472a3fd20b7ac9cdf1d3cbed0e35.exe"2⤵
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 660 -s 243⤵
- Program crash