Analysis
- max time kernel
188s - max time network
300s - platform
windows10-1703_x64 - resource
win10-20230915-en - resource tags
arch:x64arch:x86image:win10-20230915-enlocale:en-usos:windows10-1703-x64system - submitted
04/10/2023, 04:49
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
940fcb61134684d28efa774fecdd1c6ccd179e38c1e060ea04c8270ee18a16a0.exe
Resource
win7-20230831-en
8 signatures
300 seconds
Behavioral task
behavioral2
Sample
940fcb61134684d28efa774fecdd1c6ccd179e38c1e060ea04c8270ee18a16a0.exe
Resource
win10-20230915-en
8 signatures
300 seconds
General
- Target 940fcb61134684d28efa774fecdd1c6ccd179e38c1e060ea04c8270ee18a16a0.exe
- Size 1.5MB
- Sample231004-ffsxgaba76
- SHA256 940fcb61134684d28efa774fecdd1c6ccd179e38c1e060ea04c8270ee18a16a0
- MD5 7aa2d4005c0688fbb8c3ff8f1ad2f898
- SHA1 789b429372d9eec386382a1893efb56a52890d5d
- SHA512 4dd6ce4903a33ab1a8fc4a2a8e3467833b1ad60573e0ce0da250526c96f06180b52b4147e1f155c8833c082f49af04e25fff7e1f6bdea73f24ea6a118ae6e18f
- SSDEEP 12288:4ruH7lpvsJws5ZcmuLVc9X6a9Dhvh/nIUvmlG9bj:4rGldsJwh46a9DhvhAUvU4
- MD5 SHA1 SHA512 SSDEEP
Malware Config
Extracted
Family
-
redline
Botnet
-
LogsDiller Cloud (TG: @logsdillabot)
C2
-
51.255.152.132:36011
Signatures
- RedLine
RedLine Stealer is a malware family written in C#, first appearing in early 2020.
- RedLine payload 1 IoCs
resource yara_rule behavioral2/memory/2136-0-0x0000000000400000-0x000000000043E000-memory.dmp family_redline - Accesses cryptocurrency files/wallets, possible credential harvesting 2 TTPs
- Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 596 set thread context of 2136 596 940fcb61134684d28efa774fecdd1c6ccd179e38c1e060ea04c8270ee18a16a0.exe 74 - Program crash 1 IoCs
pid pid_target Process procid_target 2292 596 WerFault.exe 68 - Suspicious behavior: EnumeratesProcesses 3 IoCs
pid Process 2136 AppLaunch.exe 2136 AppLaunch.exe 2136 AppLaunch.exe - Suspicious use of AdjustPrivilegeToken 1 IoCs
description pid Process Token: SeDebugPrivilege 2136 AppLaunch.exe - Suspicious use of WriteProcessMemory 20 IoCs
description pid Process procid_target PID 596 wrote to memory of 2216 596 940fcb61134684d28efa774fecdd1c6ccd179e38c1e060ea04c8270ee18a16a0.exe 70 PID 596 wrote to memory of 2216 596 940fcb61134684d28efa774fecdd1c6ccd179e38c1e060ea04c8270ee18a16a0.exe 70 PID 596 wrote to memory of 2216 596 940fcb61134684d28efa774fecdd1c6ccd179e38c1e060ea04c8270ee18a16a0.exe 70 PID 596 wrote to memory of 592 596 940fcb61134684d28efa774fecdd1c6ccd179e38c1e060ea04c8270ee18a16a0.exe 71 PID 596 wrote to memory of 592 596 940fcb61134684d28efa774fecdd1c6ccd179e38c1e060ea04c8270ee18a16a0.exe 71 PID 596 wrote to memory of 592 596 940fcb61134684d28efa774fecdd1c6ccd179e38c1e060ea04c8270ee18a16a0.exe 71 PID 596 wrote to memory of 4820 596 940fcb61134684d28efa774fecdd1c6ccd179e38c1e060ea04c8270ee18a16a0.exe 72 PID 596 wrote to memory of 4820 596 940fcb61134684d28efa774fecdd1c6ccd179e38c1e060ea04c8270ee18a16a0.exe 72 PID 596 wrote to memory of 4820 596 940fcb61134684d28efa774fecdd1c6ccd179e38c1e060ea04c8270ee18a16a0.exe 72 PID 596 wrote to memory of 3024 596 940fcb61134684d28efa774fecdd1c6ccd179e38c1e060ea04c8270ee18a16a0.exe 73 PID 596 wrote to memory of 3024 596 940fcb61134684d28efa774fecdd1c6ccd179e38c1e060ea04c8270ee18a16a0.exe 73 PID 596 wrote to memory of 3024 596 940fcb61134684d28efa774fecdd1c6ccd179e38c1e060ea04c8270ee18a16a0.exe 73 PID 596 wrote to memory of 2136 596 940fcb61134684d28efa774fecdd1c6ccd179e38c1e060ea04c8270ee18a16a0.exe 74 PID 596 wrote to memory of 2136 596 940fcb61134684d28efa774fecdd1c6ccd179e38c1e060ea04c8270ee18a16a0.exe 74 PID 596 wrote to memory of 2136 596 940fcb61134684d28efa774fecdd1c6ccd179e38c1e060ea04c8270ee18a16a0.exe 74 PID 596 wrote to memory of 2136 596 940fcb61134684d28efa774fecdd1c6ccd179e38c1e060ea04c8270ee18a16a0.exe 74 PID 596 wrote to memory of 2136 596 940fcb61134684d28efa774fecdd1c6ccd179e38c1e060ea04c8270ee18a16a0.exe 74 PID 596 wrote to memory of 2136 596 940fcb61134684d28efa774fecdd1c6ccd179e38c1e060ea04c8270ee18a16a0.exe 74 PID 596 wrote to memory of 2136 596 940fcb61134684d28efa774fecdd1c6ccd179e38c1e060ea04c8270ee18a16a0.exe 74 PID 596 wrote to memory of 2136 596 940fcb61134684d28efa774fecdd1c6ccd179e38c1e060ea04c8270ee18a16a0.exe 74
Processes
-
C:\Users\Admin\AppData\Local\Temp\940fcb61134684d28efa774fecdd1c6ccd179e38c1e060ea04c8270ee18a16a0.exe"C:\Users\Admin\AppData\Local\Temp\940fcb61134684d28efa774fecdd1c6ccd179e38c1e060ea04c8270ee18a16a0.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:596 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:2216
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:592
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:4820
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:3024
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of AdjustPrivilegeToken
PID:2136
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 596 -s 3402⤵
- Program crash
PID:2292
-