Analysis
-
max time kernel
150s -
max time network
157s -
platform
windows10-2004_x64 -
resource
win10v2004-20220414-en -
submitted
14-05-2022 13:50
Static task
static1
Behavioral task
behavioral1
Sample
2f81e8b71640e7b5770deccc56c23d75240c34a5914dcb138ec2972e624a0f03.exe
Resource
win7-20220414-en
Behavioral task
behavioral2
Sample
2f81e8b71640e7b5770deccc56c23d75240c34a5914dcb138ec2972e624a0f03.exe
Resource
win10v2004-20220414-en
General
-
Target
2f81e8b71640e7b5770deccc56c23d75240c34a5914dcb138ec2972e624a0f03.exe
-
Size
512KB
-
MD5
4b204c35e5306c88090ca9f2b52ae930
-
SHA1
f290117f9ad0e7f2507d94be22398b1019775a13
-
SHA256
2f81e8b71640e7b5770deccc56c23d75240c34a5914dcb138ec2972e624a0f03
-
SHA512
cd067bf766447a85b09d894f799996cc9541f41dba3ddee0b40b6af2f49f142600d39d25ead33e8370efd917bbe2bf16bc3a0eb1185e0ce27c34572fcd429a48
Malware Config
Extracted
azorult
http://e4v5sa.xyz/PL341/index.php
Signatures
-
Azorult
An information stealer that was first discovered in 2016, targeting browsing history and passwords.
-
Suspicious use of SetThreadContext 1 IoCs
Processes:
2f81e8b71640e7b5770deccc56c23d75240c34a5914dcb138ec2972e624a0f03.exedescription pid process target process PID 4304 set thread context of 3392 4304 2f81e8b71640e7b5770deccc56c23d75240c34a5914dcb138ec2972e624a0f03.exe 2f81e8b71640e7b5770deccc56c23d75240c34a5914dcb138ec2972e624a0f03.exe -
Suspicious use of WriteProcessMemory 9 IoCs
Processes:
2f81e8b71640e7b5770deccc56c23d75240c34a5914dcb138ec2972e624a0f03.exedescription pid process target process PID 4304 wrote to memory of 3392 4304 2f81e8b71640e7b5770deccc56c23d75240c34a5914dcb138ec2972e624a0f03.exe 2f81e8b71640e7b5770deccc56c23d75240c34a5914dcb138ec2972e624a0f03.exe PID 4304 wrote to memory of 3392 4304 2f81e8b71640e7b5770deccc56c23d75240c34a5914dcb138ec2972e624a0f03.exe 2f81e8b71640e7b5770deccc56c23d75240c34a5914dcb138ec2972e624a0f03.exe PID 4304 wrote to memory of 3392 4304 2f81e8b71640e7b5770deccc56c23d75240c34a5914dcb138ec2972e624a0f03.exe 2f81e8b71640e7b5770deccc56c23d75240c34a5914dcb138ec2972e624a0f03.exe PID 4304 wrote to memory of 3392 4304 2f81e8b71640e7b5770deccc56c23d75240c34a5914dcb138ec2972e624a0f03.exe 2f81e8b71640e7b5770deccc56c23d75240c34a5914dcb138ec2972e624a0f03.exe PID 4304 wrote to memory of 3392 4304 2f81e8b71640e7b5770deccc56c23d75240c34a5914dcb138ec2972e624a0f03.exe 2f81e8b71640e7b5770deccc56c23d75240c34a5914dcb138ec2972e624a0f03.exe PID 4304 wrote to memory of 3392 4304 2f81e8b71640e7b5770deccc56c23d75240c34a5914dcb138ec2972e624a0f03.exe 2f81e8b71640e7b5770deccc56c23d75240c34a5914dcb138ec2972e624a0f03.exe PID 4304 wrote to memory of 3392 4304 2f81e8b71640e7b5770deccc56c23d75240c34a5914dcb138ec2972e624a0f03.exe 2f81e8b71640e7b5770deccc56c23d75240c34a5914dcb138ec2972e624a0f03.exe PID 4304 wrote to memory of 3392 4304 2f81e8b71640e7b5770deccc56c23d75240c34a5914dcb138ec2972e624a0f03.exe 2f81e8b71640e7b5770deccc56c23d75240c34a5914dcb138ec2972e624a0f03.exe PID 4304 wrote to memory of 3392 4304 2f81e8b71640e7b5770deccc56c23d75240c34a5914dcb138ec2972e624a0f03.exe 2f81e8b71640e7b5770deccc56c23d75240c34a5914dcb138ec2972e624a0f03.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\2f81e8b71640e7b5770deccc56c23d75240c34a5914dcb138ec2972e624a0f03.exe"C:\Users\Admin\AppData\Local\Temp\2f81e8b71640e7b5770deccc56c23d75240c34a5914dcb138ec2972e624a0f03.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:4304 -
C:\Users\Admin\AppData\Local\Temp\2f81e8b71640e7b5770deccc56c23d75240c34a5914dcb138ec2972e624a0f03.exe"C:\Users\Admin\AppData\Local\Temp\2f81e8b71640e7b5770deccc56c23d75240c34a5914dcb138ec2972e624a0f03.exe"2⤵PID:3392
-
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k appmodel -p -s camsvc1⤵PID:220