Analysis
- max time kernel
91s - max time network
132s - platform
windows10-2004_x64 - resource
win10v2004-20220414-en - submitted
20/05/2022, 07:47
Static task
static1
Behavioral task
behavioral1
Sample
6fd11b4a09db2c2713edbe0bb7536402e7e7bf0255ed7b80c6dc4d934938e327.exe
Resource
win7-20220414-en
0 signatures
0 seconds
Behavioral task
behavioral2
Sample
6fd11b4a09db2c2713edbe0bb7536402e7e7bf0255ed7b80c6dc4d934938e327.exe
Resource
win10v2004-20220414-en
0 signatures
0 seconds
General
- Target 6fd11b4a09db2c2713edbe0bb7536402e7e7bf0255ed7b80c6dc4d934938e327.exe
- Size 706KB
- Sample220520-jmn4msghc7
- SHA256 6fd11b4a09db2c2713edbe0bb7536402e7e7bf0255ed7b80c6dc4d934938e327
- MD5 3b753f760f97b526392a2d7cd2f034b8
- SHA1 c746419307c55d44f9b7341efcaaa4ac1ee6e7dc
- SHA512 224bc9ad9eaed6a3a0b0e1586575b3cbc5719a63d4f05509b9c0364d27b9ccc2e040f537019fdb34483ea0b3369cc46cee633385b0e0d9ca6f0b0537682e73a5
- MD5 SHA1 SHA512
Score
10/10
Malware Config
Extracted
Family
-
azorult
C2
-
http://85.202.169.121/mann/index.php
Signatures
- Azorult
An information stealer that was first discovered in 2016, targeting browsing history and passwords.
- suricata: ET MALWARE Win32/AZORult V3.3 Client Checkin M13
suricata: ET MALWARE Win32/AZORult V3.3 Client Checkin M13
- Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 4764 set thread context of 1068 4764 6fd11b4a09db2c2713edbe0bb7536402e7e7bf0255ed7b80c6dc4d934938e327.exe 88 - Suspicious use of WriteProcessMemory 9 IoCs
description pid Process procid_target PID 4764 wrote to memory of 1068 4764 6fd11b4a09db2c2713edbe0bb7536402e7e7bf0255ed7b80c6dc4d934938e327.exe 88 PID 4764 wrote to memory of 1068 4764 6fd11b4a09db2c2713edbe0bb7536402e7e7bf0255ed7b80c6dc4d934938e327.exe 88 PID 4764 wrote to memory of 1068 4764 6fd11b4a09db2c2713edbe0bb7536402e7e7bf0255ed7b80c6dc4d934938e327.exe 88 PID 4764 wrote to memory of 1068 4764 6fd11b4a09db2c2713edbe0bb7536402e7e7bf0255ed7b80c6dc4d934938e327.exe 88 PID 4764 wrote to memory of 1068 4764 6fd11b4a09db2c2713edbe0bb7536402e7e7bf0255ed7b80c6dc4d934938e327.exe 88 PID 4764 wrote to memory of 1068 4764 6fd11b4a09db2c2713edbe0bb7536402e7e7bf0255ed7b80c6dc4d934938e327.exe 88 PID 4764 wrote to memory of 1068 4764 6fd11b4a09db2c2713edbe0bb7536402e7e7bf0255ed7b80c6dc4d934938e327.exe 88 PID 4764 wrote to memory of 1068 4764 6fd11b4a09db2c2713edbe0bb7536402e7e7bf0255ed7b80c6dc4d934938e327.exe 88 PID 4764 wrote to memory of 1068 4764 6fd11b4a09db2c2713edbe0bb7536402e7e7bf0255ed7b80c6dc4d934938e327.exe 88
Processes
-
C:\Users\Admin\AppData\Local\Temp\6fd11b4a09db2c2713edbe0bb7536402e7e7bf0255ed7b80c6dc4d934938e327.exe"C:\Users\Admin\AppData\Local\Temp\6fd11b4a09db2c2713edbe0bb7536402e7e7bf0255ed7b80c6dc4d934938e327.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:4764 -
C:\Users\Admin\AppData\Local\Temp\6fd11b4a09db2c2713edbe0bb7536402e7e7bf0255ed7b80c6dc4d934938e327.exe"C:\Users\Admin\AppData\Local\Temp\6fd11b4a09db2c2713edbe0bb7536402e7e7bf0255ed7b80c6dc4d934938e327.exe"2⤵PID:1068
-