Analysis
-
max time kernel
25s -
max time network
33s -
platform
windows7_x64 -
resource
win7-20221111-en -
resource tags
arch:x64arch:x86image:win7-20221111-enlocale:en-usos:windows7-x64system -
submitted
12/02/2023, 01:19
Behavioral task
behavioral1
Sample
d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe
Resource
win7-20221111-en
Behavioral task
behavioral2
Sample
d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe
Resource
win10v2004-20221111-en
General
-
Target
d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe
-
Size
2.1MB
-
MD5
5ba5f954be0ccebe4b04a2f7d32b5b70
-
SHA1
40c2e36b7e79d0b676fe90dcc43d0595219885f6
-
SHA256
d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e
-
SHA512
ed7daa30bd8fbe5a2b909a8af2c4386bcbd28c84268b18157e6183855d1451a46db1e1f80ab6f2825fa6068dceffc9e98c6cbd13fdff9c21ecfde86bb9637792
-
SSDEEP
49152:O0hpg74r02Gv8rLcmPYg+z9DgkfMtpPI/LASf7pBOo6bU0FxZ:O0j04rBr4mQFgkfMtikWpUo0L
Malware Config
Extracted
redline
mojno v rot
79.137.192.41:40084
-
auth_value
0cd15a7512436db6ce132ddeaf3b5aeb
Signatures
-
RedLine
RedLine Stealer is a malware family written in C#, first appearing in early 2020.
-
Identifies VirtualBox via ACPI registry values (likely anti-VM) 2 TTPs 1 IoCs
description ioc Process Key opened \REGISTRY\MACHINE\HARDWARE\ACPI\DSDT\VBOX__ d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe -
Checks BIOS information in registry 2 TTPs 2 IoCs
BIOS information is often read in order to detect sandboxing environments.
description ioc Process Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\SystemBiosVersion d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\VideoBiosVersion d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe -
resource yara_rule behavioral1/memory/1268-55-0x0000000000C20000-0x00000000012D4000-memory.dmp themida behavioral1/memory/1268-57-0x0000000000C20000-0x00000000012D4000-memory.dmp themida behavioral1/memory/1268-62-0x0000000000C20000-0x00000000012D4000-memory.dmp themida -
description ioc Process Key value queried \REGISTRY\MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\EnableLUA d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe -
Suspicious use of NtSetInformationThreadHideFromDebugger 1 IoCs
pid Process 1268 d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 1268 set thread context of 1112 1268 d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe 34 -
Program crash 1 IoCs
pid pid_target Process procid_target 1696 1112 WerFault.exe 34 -
Suspicious behavior: EnumeratesProcesses 12 IoCs
pid Process 1268 d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe 1268 d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe 1268 d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe 1268 d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe 1268 d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe 1268 d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe 1268 d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe 1268 d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe 1268 d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe 1268 d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe 1268 d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe 1268 d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe -
Suspicious use of AdjustPrivilegeToken 1 IoCs
description pid Process Token: SeDebugPrivilege 1268 d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe -
Suspicious use of WriteProcessMemory 34 IoCs
description pid Process procid_target PID 1268 wrote to memory of 728 1268 d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe 28 PID 1268 wrote to memory of 728 1268 d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe 28 PID 1268 wrote to memory of 728 1268 d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe 28 PID 1268 wrote to memory of 652 1268 d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe 29 PID 1268 wrote to memory of 652 1268 d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe 29 PID 1268 wrote to memory of 652 1268 d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe 29 PID 1268 wrote to memory of 1036 1268 d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe 30 PID 1268 wrote to memory of 1036 1268 d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe 30 PID 1268 wrote to memory of 1036 1268 d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe 30 PID 1268 wrote to memory of 1272 1268 d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe 31 PID 1268 wrote to memory of 1272 1268 d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe 31 PID 1268 wrote to memory of 1272 1268 d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe 31 PID 1268 wrote to memory of 1896 1268 d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe 32 PID 1268 wrote to memory of 1896 1268 d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe 32 PID 1268 wrote to memory of 1896 1268 d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe 32 PID 1268 wrote to memory of 668 1268 d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe 33 PID 1268 wrote to memory of 668 1268 d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe 33 PID 1268 wrote to memory of 668 1268 d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe 33 PID 1268 wrote to memory of 1112 1268 d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe 34 PID 1268 wrote to memory of 1112 1268 d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe 34 PID 1268 wrote to memory of 1112 1268 d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe 34 PID 1268 wrote to memory of 1112 1268 d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe 34 PID 1268 wrote to memory of 1112 1268 d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe 34 PID 1268 wrote to memory of 1112 1268 d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe 34 PID 1268 wrote to memory of 1112 1268 d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe 34 PID 1268 wrote to memory of 1112 1268 d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe 34 PID 1268 wrote to memory of 1112 1268 d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe 34 PID 1268 wrote to memory of 1112 1268 d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe 34 PID 1268 wrote to memory of 1112 1268 d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe 34 PID 1268 wrote to memory of 1112 1268 d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe 34 PID 1112 wrote to memory of 1696 1112 SetupUtility.exe 35 PID 1112 wrote to memory of 1696 1112 SetupUtility.exe 35 PID 1112 wrote to memory of 1696 1112 SetupUtility.exe 35 PID 1112 wrote to memory of 1696 1112 SetupUtility.exe 35
Processes
-
C:\Users\Admin\AppData\Local\Temp\d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe"C:\Users\Admin\AppData\Local\Temp\d40a01137b266d7416d640caab27ba34517e899aa8d7e53229d8b78067b02a6e.exe"1⤵
- Identifies VirtualBox via ACPI registry values (likely anti-VM)
- Checks BIOS information in registry
- Checks whether UAC is enabled
- Suspicious use of NtSetInformationThreadHideFromDebugger
- Suspicious use of SetThreadContext
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:1268 -
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Workflow.Compiler.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Workflow.Compiler.exe"2⤵PID:728
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\MSBuild.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\MSBuild.exe"2⤵PID:652
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\SMSvcHost.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\SMSvcHost.exe"2⤵PID:1036
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_wp.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_wp.exe"2⤵PID:1272
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\InstallUtil.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\InstallUtil.exe"2⤵PID:1896
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regsql.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regsql.exe"2⤵PID:668
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\SetupCache\v4.7.03062\SetupUtility.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\SetupCache\v4.7.03062\SetupUtility.exe"2⤵
- Suspicious use of WriteProcessMemory
PID:1112 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 1112 -s 1683⤵
- Program crash
PID:1696
-
-