Analysis
-
max time kernel
31s -
max time network
33s -
platform
windows7_x64 -
resource
win7-20230220-en -
resource tags
arch:x64arch:x86image:win7-20230220-enlocale:en-usos:windows7-x64system -
submitted
10-06-2023 01:35
Static task
static1
Behavioral task
behavioral1
Sample
7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe
Resource
win7-20230220-en
Behavioral task
behavioral2
Sample
7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe
Resource
win10v2004-20230220-en
General
-
Target
7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe
-
Size
45KB
-
MD5
788f396393dcab0c3dee93fbd2ae8371
-
SHA1
3ba5c566299ba91072f41cffa8894a237bcff71d
-
SHA256
7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24
-
SHA512
a11266ac7f051fc8ef89ae8a003dd7d27456891e835754d40b706d08c0446d1a176eb2ff3673dfb3a351b8e59856db4902b90d44195c9c3d88a99d3fdaeb35d4
-
SSDEEP
768:RjFq7GFIOtbLrPg2Eln1eL2HLMGTay0CE5qb4rafyFZ:xF3b/PZEV1eL2rhTarefyFZ
Malware Config
Signatures
-
Detects LgoogLoader payload 1 IoCs
resource yara_rule behavioral1/memory/1900-62-0x0000000000140000-0x000000000014D000-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" 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2008 set thread context of 1900 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 40 -
Suspicious behavior: EnumeratesProcesses 13 IoCs
pid Process 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe -
Suspicious behavior: LoadsDriver 1 IoCs
pid Process 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe -
Suspicious use of AdjustPrivilegeToken 3 IoCs
description pid Process Token: SeDebugPrivilege 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe Token: SeDebugPrivilege 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe Token: SeLoadDriverPrivilege 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe -
Suspicious use of WriteProcessMemory 51 IoCs
description pid Process procid_target PID 2008 wrote to memory of 1412 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 27 PID 2008 wrote to memory of 1412 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 27 PID 2008 wrote to memory of 1412 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 27 PID 2008 wrote to memory of 340 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 28 PID 2008 wrote to memory of 340 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 28 PID 2008 wrote to memory of 340 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 28 PID 2008 wrote to memory of 1416 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 29 PID 2008 wrote to memory of 1416 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 29 PID 2008 wrote to memory of 1416 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 29 PID 2008 wrote to memory of 1852 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 30 PID 2008 wrote to memory of 1852 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 30 PID 2008 wrote to memory of 1852 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 30 PID 2008 wrote to memory of 524 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 31 PID 2008 wrote to memory of 524 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 31 PID 2008 wrote to memory of 524 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 31 PID 2008 wrote to memory of 1444 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 32 PID 2008 wrote to memory of 1444 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 32 PID 2008 wrote to memory of 1444 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 32 PID 2008 wrote to memory of 1148 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 33 PID 2008 wrote to memory of 1148 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 33 PID 2008 wrote to memory of 1148 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 33 PID 2008 wrote to memory of 1696 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 34 PID 2008 wrote to memory of 1696 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 34 PID 2008 wrote to memory of 1696 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 34 PID 2008 wrote to memory of 1716 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 35 PID 2008 wrote to memory of 1716 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 35 PID 2008 wrote to memory of 1716 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 35 PID 2008 wrote to memory of 1536 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 36 PID 2008 wrote to memory of 1536 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 36 PID 2008 wrote to memory of 1536 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 36 PID 2008 wrote to memory of 1864 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 37 PID 2008 wrote to memory of 1864 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 37 PID 2008 wrote to memory of 1864 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 37 PID 2008 wrote to memory of 1952 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 38 PID 2008 wrote to memory of 1952 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 38 PID 2008 wrote to memory of 1952 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 38 PID 2008 wrote to memory of 1748 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 39 PID 2008 wrote to memory of 1748 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 39 PID 2008 wrote to memory of 1748 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 39 PID 2008 wrote to memory of 1748 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 39 PID 2008 wrote to memory of 1900 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 40 PID 2008 wrote to memory of 1900 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 40 PID 2008 wrote to memory of 1900 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 40 PID 2008 wrote to memory of 1900 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 40 PID 2008 wrote to memory of 1900 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 40 PID 2008 wrote to memory of 1900 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 40 PID 2008 wrote to memory of 1900 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 40 PID 2008 wrote to memory of 1900 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 40 PID 2008 wrote to memory of 1900 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 40 PID 2008 wrote to memory of 1900 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 40 PID 2008 wrote to memory of 1900 2008 7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe 40
Processes
-
C:\Users\Admin\AppData\Local\Temp\7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.exe"C:\Users\Admin\AppData\Local\Temp\7ba6ab30eb71e8ab3ccdc734633391c092b25160f62173d4b6237da6c55b5a24.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:2008 -
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regsql.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regsql.exe"2⤵PID:1412
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regbrowsers.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regbrowsers.exe"2⤵PID:340
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe"2⤵PID:1416
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_state.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_state.exe"2⤵PID:1852
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\EdmGen.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\EdmGen.exe"2⤵PID:524
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\dfsvc.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\dfsvc.exe"2⤵PID:1444
-
-
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:1148
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\DataSvcUtil.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\DataSvcUtil.exe"2⤵PID:1696
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\CasPol.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\CasPol.exe"2⤵PID:1716
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\InstallUtil.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\InstallUtil.exe"2⤵PID:1536
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\AddInProcess.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\AddInProcess.exe"2⤵PID:1864
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\SMSvcHost.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\SMSvcHost.exe"2⤵PID:1952
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\AddInProcess32.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\AddInProcess32.exe"2⤵PID:1748
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\jsc.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\jsc.exe"2⤵PID:1900
-