Analysis
-
max time kernel
299s -
max time network
298s -
platform
windows10-1703_x64 -
resource
win10-20240404-en -
resource tags
arch:x64arch:x86image:win10-20240404-enlocale:en-usos:windows10-1703-x64system -
submitted
08/07/2024, 05:03
Static task
static1
Behavioral task
behavioral1
Sample
6ccec07e798b1400fdb5c6d059b4a7421333c12ec60c566d599e556cd74e53b2.exe
Resource
win7-20240220-en
Behavioral task
behavioral2
Sample
6ccec07e798b1400fdb5c6d059b4a7421333c12ec60c566d599e556cd74e53b2.exe
Resource
win10-20240404-en
General
-
Target
6ccec07e798b1400fdb5c6d059b4a7421333c12ec60c566d599e556cd74e53b2.exe
-
Size
537KB
-
MD5
e72e3e0f37eddc11e9003053604c7ab6
-
SHA1
2c8fe866e63d022f0da0f67132d14260fc220e24
-
SHA256
6ccec07e798b1400fdb5c6d059b4a7421333c12ec60c566d599e556cd74e53b2
-
SHA512
10ff29c4310676f4f198baf12d087b4283bcafa846f626493e9716611b4e815df58073f37018a337654de1d382b31bc7e8ae948dbe1c77e156b89f2c5d8479ac
-
SSDEEP
12288:GlPvulyUTwW9U9ybMSDttya3WfwsUXo0gIteVvfL/T+jtx:GlPmlyU82Df3NsUTgsCvfL6
Malware Config
Extracted
redline
LiveTraffic
20.52.165.210:39030
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/2700-1-0x0000000000400000-0x0000000000450000-memory.dmp family_redline -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 3444 set thread context of 2700 3444 6ccec07e798b1400fdb5c6d059b4a7421333c12ec60c566d599e556cd74e53b2.exe 76 -
Suspicious use of WriteProcessMemory 8 IoCs
description pid Process procid_target PID 3444 wrote to memory of 2700 3444 6ccec07e798b1400fdb5c6d059b4a7421333c12ec60c566d599e556cd74e53b2.exe 76 PID 3444 wrote to memory of 2700 3444 6ccec07e798b1400fdb5c6d059b4a7421333c12ec60c566d599e556cd74e53b2.exe 76 PID 3444 wrote to memory of 2700 3444 6ccec07e798b1400fdb5c6d059b4a7421333c12ec60c566d599e556cd74e53b2.exe 76 PID 3444 wrote to memory of 2700 3444 6ccec07e798b1400fdb5c6d059b4a7421333c12ec60c566d599e556cd74e53b2.exe 76 PID 3444 wrote to memory of 2700 3444 6ccec07e798b1400fdb5c6d059b4a7421333c12ec60c566d599e556cd74e53b2.exe 76 PID 3444 wrote to memory of 2700 3444 6ccec07e798b1400fdb5c6d059b4a7421333c12ec60c566d599e556cd74e53b2.exe 76 PID 3444 wrote to memory of 2700 3444 6ccec07e798b1400fdb5c6d059b4a7421333c12ec60c566d599e556cd74e53b2.exe 76 PID 3444 wrote to memory of 2700 3444 6ccec07e798b1400fdb5c6d059b4a7421333c12ec60c566d599e556cd74e53b2.exe 76
Processes
-
C:\Users\Admin\AppData\Local\Temp\6ccec07e798b1400fdb5c6d059b4a7421333c12ec60c566d599e556cd74e53b2.exe"C:\Users\Admin\AppData\Local\Temp\6ccec07e798b1400fdb5c6d059b4a7421333c12ec60c566d599e556cd74e53b2.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:3444 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:2700
-