Analysis
-
max time kernel
91s -
max time network
151s -
platform
windows10-2004_x64 -
resource
win10v2004-20220901-en -
resource tags
arch:x64arch:x86image:win10v2004-20220901-enlocale:en-usos:windows10-2004-x64system -
submitted
15-01-2023 08:19
Static task
static1
Behavioral task
behavioral1
Sample
file.exe
Resource
win7-20220901-en
8 signatures
150 seconds
Behavioral task
behavioral2
Sample
file.exe
Resource
win10v2004-20220901-en
8 signatures
150 seconds
General
-
Target
file.exe
-
Size
695KB
-
MD5
928fa3e8a43ce4f32e5cb5f469a4981f
-
SHA1
742c4185e8ef6a8a70b320927d0dbc13a33a7c6f
-
SHA256
c6135818ddc5d31afa68f42f21e1da3e19f879096298ccb84f68803847235004
-
SHA512
c625374d344ef3c607659e5a4eb0d2978e6d030d25310cc9c9ed4aa249ef9adcf50a2053035c94daa750c8ddef044208c2425e01fe759662c32eff9140e9513c
-
SSDEEP
12288:8HbpxW0j2LnZvxo1IB5DiQqyGF3S064Fd+smJjMHGT/Ksq/KsK/Ksu:8HbpxW0j2LnboqiV3p/FEZjX7iC+
Score
10/10
Malware Config
Signatures
-
Detects LgoogLoader payload 1 IoCs
resource yara_rule behavioral2/memory/4540-142-0x0000000001370000-0x000000000137D000-memory.dmp family_lgoogloader -
LgoogLoader
A downloader capable of dropping and executing other malware families.
-
Sets service image path in registry 2 TTPs 1 IoCs
description ioc Process Set value (str) \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\TaskKill\ImagePath = "\\??\\C:\\Users\\Admin\\AppData\\Local\\Temp\\Иисус.sys" file.exe -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 5060 set thread context of 4540 5060 file.exe 89 -
Suspicious behavior: EnumeratesProcesses 16 IoCs
pid Process 5060 file.exe 5060 file.exe 5060 file.exe 5060 file.exe 5060 file.exe 5060 file.exe 5060 file.exe 5060 file.exe 5060 file.exe 5060 file.exe 5060 file.exe 5060 file.exe 5060 file.exe 5060 file.exe 5060 file.exe 5060 file.exe -
Suspicious behavior: LoadsDriver 1 IoCs
pid Process 5060 file.exe -
Suspicious use of AdjustPrivilegeToken 3 IoCs
description pid Process Token: SeDebugPrivilege 5060 file.exe Token: SeLoadDriverPrivilege 5060 file.exe Token: SeDebugPrivilege 5060 file.exe -
Suspicious use of WriteProcessMemory 27 IoCs
description pid Process procid_target PID 5060 wrote to memory of 2160 5060 file.exe 81 PID 5060 wrote to memory of 2160 5060 file.exe 81 PID 5060 wrote to memory of 2820 5060 file.exe 82 PID 5060 wrote to memory of 2820 5060 file.exe 82 PID 5060 wrote to memory of 4744 5060 file.exe 83 PID 5060 wrote to memory of 4744 5060 file.exe 83 PID 5060 wrote to memory of 3944 5060 file.exe 84 PID 5060 wrote to memory of 3944 5060 file.exe 84 PID 5060 wrote to memory of 4904 5060 file.exe 85 PID 5060 wrote to memory of 4904 5060 file.exe 85 PID 5060 wrote to memory of 3672 5060 file.exe 86 PID 5060 wrote to memory of 3672 5060 file.exe 86 PID 5060 wrote to memory of 4716 5060 file.exe 87 PID 5060 wrote to memory of 4716 5060 file.exe 87 PID 5060 wrote to memory of 2784 5060 file.exe 88 PID 5060 wrote to memory of 2784 5060 file.exe 88 PID 5060 wrote to memory of 4540 5060 file.exe 89 PID 5060 wrote to memory of 4540 5060 file.exe 89 PID 5060 wrote to memory of 4540 5060 file.exe 89 PID 5060 wrote to memory of 4540 5060 file.exe 89 PID 5060 wrote to memory of 4540 5060 file.exe 89 PID 5060 wrote to memory of 4540 5060 file.exe 89 PID 5060 wrote to memory of 4540 5060 file.exe 89 PID 5060 wrote to memory of 4540 5060 file.exe 89 PID 5060 wrote to memory of 4540 5060 file.exe 89 PID 5060 wrote to memory of 4540 5060 file.exe 89 PID 5060 wrote to memory of 4540 5060 file.exe 89
Processes
-
C:\Users\Admin\AppData\Local\Temp\file.exe"C:\Users\Admin\AppData\Local\Temp\file.exe"1⤵
- Sets service image path in registry
- Suspicious use of SetThreadContext
- Suspicious behavior: EnumeratesProcesses
- Suspicious behavior: LoadsDriver
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:5060 -
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegSvcs.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegSvcs.exe"2⤵PID:2160
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\AddInProcess.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\AddInProcess.exe"2⤵PID:2820
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe"2⤵PID:4744
-
-
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:3944
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ilasm.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ilasm.exe"2⤵PID:4904
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegAsm.exe"2⤵PID:3672
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe"2⤵PID:4716
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ComSvcConfig.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ComSvcConfig.exe"2⤵PID:2784
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\jsc.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\jsc.exe"2⤵PID:4540
-