Analysis
-
max time kernel
115s -
max time network
120s -
platform
windows10-2004_x64 -
resource
win10v2004-20220812-en -
resource tags
arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system -
submitted
02/01/2023, 04:02
Static task
static1
Behavioral task
behavioral1
Sample
87e2a2bde61f533bf3616de31a2996e8750a5c37d677036b6a3a8de1dd24bbf8.exe
Resource
win10v2004-20220812-en
General
-
Target
87e2a2bde61f533bf3616de31a2996e8750a5c37d677036b6a3a8de1dd24bbf8.exe
-
Size
277KB
-
MD5
cba8587e6152a7facf4adda766f1f0cc
-
SHA1
dc38b43ec07f1f7727e9a663914b07ad590b0580
-
SHA256
87e2a2bde61f533bf3616de31a2996e8750a5c37d677036b6a3a8de1dd24bbf8
-
SHA512
fc319ac044997ac8cc1ed67f5d53a956800d2a5c3d415026b208e9b9e4d21965a636da878e640514d7f1895ab1f0f1032c3d817aef122178df335b4644c42a81
-
SSDEEP
3072:K3DJ0ADKLyLGAZzIXBVWIMekVAngc13iaeVQjE2ELs07SfRO7hOD0IB4lX:2d30yLGaaBVSeku/eVQQY07Zy0fX
Malware Config
Extracted
redline
pub2
89.22.231.25:45245
-
auth_value
ea9464d486a641bb513057e5f63399e1
Signatures
-
RedLine
RedLine Stealer is a malware family written in C#, first appearing in early 2020.
-
Uses the VBS compiler for execution 1 TTPs
-
Accesses cryptocurrency files/wallets, possible credential harvesting 2 TTPs
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 3648 set thread context of 4392 3648 87e2a2bde61f533bf3616de31a2996e8750a5c37d677036b6a3a8de1dd24bbf8.exe 80 -
Program crash 3 IoCs
pid pid_target Process procid_target 3620 3648 WerFault.exe 78 3312 3648 WerFault.exe 78 4804 3648 WerFault.exe 78 -
Suspicious behavior: EnumeratesProcesses 2 IoCs
pid Process 4392 vbc.exe 4392 vbc.exe -
Suspicious use of AdjustPrivilegeToken 1 IoCs
description pid Process Token: SeDebugPrivilege 4392 vbc.exe -
Suspicious use of WriteProcessMemory 5 IoCs
description pid Process procid_target PID 3648 wrote to memory of 4392 3648 87e2a2bde61f533bf3616de31a2996e8750a5c37d677036b6a3a8de1dd24bbf8.exe 80 PID 3648 wrote to memory of 4392 3648 87e2a2bde61f533bf3616de31a2996e8750a5c37d677036b6a3a8de1dd24bbf8.exe 80 PID 3648 wrote to memory of 4392 3648 87e2a2bde61f533bf3616de31a2996e8750a5c37d677036b6a3a8de1dd24bbf8.exe 80 PID 3648 wrote to memory of 4392 3648 87e2a2bde61f533bf3616de31a2996e8750a5c37d677036b6a3a8de1dd24bbf8.exe 80 PID 3648 wrote to memory of 4392 3648 87e2a2bde61f533bf3616de31a2996e8750a5c37d677036b6a3a8de1dd24bbf8.exe 80
Processes
-
C:\Users\Admin\AppData\Local\Temp\87e2a2bde61f533bf3616de31a2996e8750a5c37d677036b6a3a8de1dd24bbf8.exe"C:\Users\Admin\AppData\Local\Temp\87e2a2bde61f533bf3616de31a2996e8750a5c37d677036b6a3a8de1dd24bbf8.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:3648 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\vbc.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\vbc.exe"2⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of AdjustPrivilegeToken
PID:4392
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3648 -s 2482⤵
- Program crash
PID:3620
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3648 -s 2522⤵
- Program crash
PID:3312
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3648 -s 1522⤵
- Program crash
PID:4804
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 184 -p 3648 -ip 36481⤵PID:4980
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 420 -p 3648 -ip 36481⤵PID:4936
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 516 -p 3648 -ip 36481⤵PID:4900