Analysis
-
max time kernel
135s -
max time network
153s -
platform
windows10-2004_x64 -
resource
win10v2004-20230221-en -
resource tags
arch:x64arch:x86image:win10v2004-20230221-enlocale:en-usos:windows10-2004-x64system -
submitted
15-05-2023 17:49
Static task
static1
Behavioral task
behavioral1
Sample
7470f8e74c2124a59f01f74ad91af303fb994218657c0c9dd21be5b5b9c2a74a.exe
Resource
win10v2004-20230221-en
windows10-2004-x64
9 signatures
150 seconds
General
-
Target
7470f8e74c2124a59f01f74ad91af303fb994218657c0c9dd21be5b5b9c2a74a.exe
-
Size
1.4MB
-
MD5
2fae82eebe27dd5e33fdc10ee8e90d24
-
SHA1
65729d70f2b1842b43e5e1499462251493e5dd1a
-
SHA256
7470f8e74c2124a59f01f74ad91af303fb994218657c0c9dd21be5b5b9c2a74a
-
SHA512
85201127ed02103d0e6577b5a880573ccfeeeeb045ea9ed91205dee0b61edbaf79199adb592dccd96eeacc78088f78693ca23ac7bc948d8ac91f2f6b318cfbb1
-
SSDEEP
12288:NhW88Erwb4r/GWOkMBOngocM3PhRXNmh9SHi8yzW0JGU3gOWyLsFLKRIImRKMqtW:DuG7IzxdtgOW+MfG67yWqfi5I7dK
Score
10/10
Malware Config
Signatures
-
Detects LgoogLoader payload 1 IoCs
resource yara_rule behavioral1/memory/4284-142-0x0000000001460000-0x000000000146D000-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" 7470f8e74c2124a59f01f74ad91af303fb994218657c0c9dd21be5b5b9c2a74a.exe -
Uses the VBS compiler for execution 1 TTPs
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 1188 set thread context of 4284 1188 7470f8e74c2124a59f01f74ad91af303fb994218657c0c9dd21be5b5b9c2a74a.exe 86 -
Suspicious behavior: EnumeratesProcesses 8 IoCs
pid Process 1188 7470f8e74c2124a59f01f74ad91af303fb994218657c0c9dd21be5b5b9c2a74a.exe 1188 7470f8e74c2124a59f01f74ad91af303fb994218657c0c9dd21be5b5b9c2a74a.exe 1188 7470f8e74c2124a59f01f74ad91af303fb994218657c0c9dd21be5b5b9c2a74a.exe 1188 7470f8e74c2124a59f01f74ad91af303fb994218657c0c9dd21be5b5b9c2a74a.exe 1188 7470f8e74c2124a59f01f74ad91af303fb994218657c0c9dd21be5b5b9c2a74a.exe 1188 7470f8e74c2124a59f01f74ad91af303fb994218657c0c9dd21be5b5b9c2a74a.exe 1188 7470f8e74c2124a59f01f74ad91af303fb994218657c0c9dd21be5b5b9c2a74a.exe 1188 7470f8e74c2124a59f01f74ad91af303fb994218657c0c9dd21be5b5b9c2a74a.exe -
Suspicious behavior: LoadsDriver 1 IoCs
pid Process 1188 7470f8e74c2124a59f01f74ad91af303fb994218657c0c9dd21be5b5b9c2a74a.exe -
Suspicious use of AdjustPrivilegeToken 3 IoCs
description pid Process Token: SeDebugPrivilege 1188 7470f8e74c2124a59f01f74ad91af303fb994218657c0c9dd21be5b5b9c2a74a.exe Token: SeLoadDriverPrivilege 1188 7470f8e74c2124a59f01f74ad91af303fb994218657c0c9dd21be5b5b9c2a74a.exe Token: SeDebugPrivilege 1188 7470f8e74c2124a59f01f74ad91af303fb994218657c0c9dd21be5b5b9c2a74a.exe -
Suspicious use of WriteProcessMemory 18 IoCs
description pid Process procid_target PID 1188 wrote to memory of 3044 1188 7470f8e74c2124a59f01f74ad91af303fb994218657c0c9dd21be5b5b9c2a74a.exe 82 PID 1188 wrote to memory of 3044 1188 7470f8e74c2124a59f01f74ad91af303fb994218657c0c9dd21be5b5b9c2a74a.exe 82 PID 1188 wrote to memory of 740 1188 7470f8e74c2124a59f01f74ad91af303fb994218657c0c9dd21be5b5b9c2a74a.exe 83 PID 1188 wrote to memory of 740 1188 7470f8e74c2124a59f01f74ad91af303fb994218657c0c9dd21be5b5b9c2a74a.exe 83 PID 1188 wrote to memory of 4388 1188 7470f8e74c2124a59f01f74ad91af303fb994218657c0c9dd21be5b5b9c2a74a.exe 84 PID 1188 wrote to memory of 4388 1188 7470f8e74c2124a59f01f74ad91af303fb994218657c0c9dd21be5b5b9c2a74a.exe 84 PID 1188 wrote to memory of 4376 1188 7470f8e74c2124a59f01f74ad91af303fb994218657c0c9dd21be5b5b9c2a74a.exe 85 PID 1188 wrote to memory of 4376 1188 7470f8e74c2124a59f01f74ad91af303fb994218657c0c9dd21be5b5b9c2a74a.exe 85 PID 1188 wrote to memory of 4284 1188 7470f8e74c2124a59f01f74ad91af303fb994218657c0c9dd21be5b5b9c2a74a.exe 86 PID 1188 wrote to memory of 4284 1188 7470f8e74c2124a59f01f74ad91af303fb994218657c0c9dd21be5b5b9c2a74a.exe 86 PID 1188 wrote to memory of 4284 1188 7470f8e74c2124a59f01f74ad91af303fb994218657c0c9dd21be5b5b9c2a74a.exe 86 PID 1188 wrote to memory of 4284 1188 7470f8e74c2124a59f01f74ad91af303fb994218657c0c9dd21be5b5b9c2a74a.exe 86 PID 1188 wrote to memory of 4284 1188 7470f8e74c2124a59f01f74ad91af303fb994218657c0c9dd21be5b5b9c2a74a.exe 86 PID 1188 wrote to memory of 4284 1188 7470f8e74c2124a59f01f74ad91af303fb994218657c0c9dd21be5b5b9c2a74a.exe 86 PID 1188 wrote to memory of 4284 1188 7470f8e74c2124a59f01f74ad91af303fb994218657c0c9dd21be5b5b9c2a74a.exe 86 PID 1188 wrote to memory of 4284 1188 7470f8e74c2124a59f01f74ad91af303fb994218657c0c9dd21be5b5b9c2a74a.exe 86 PID 1188 wrote to memory of 4284 1188 7470f8e74c2124a59f01f74ad91af303fb994218657c0c9dd21be5b5b9c2a74a.exe 86 PID 1188 wrote to memory of 4284 1188 7470f8e74c2124a59f01f74ad91af303fb994218657c0c9dd21be5b5b9c2a74a.exe 86
Processes
-
C:\Users\Admin\AppData\Local\Temp\7470f8e74c2124a59f01f74ad91af303fb994218657c0c9dd21be5b5b9c2a74a.exe"C:\Users\Admin\AppData\Local\Temp\7470f8e74c2124a59f01f74ad91af303fb994218657c0c9dd21be5b5b9c2a74a.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:1188 -
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\dfsvc.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\dfsvc.exe"2⤵PID:3044
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngentask.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngentask.exe"2⤵PID:740
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\vbc.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\vbc.exe"2⤵PID:4388
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\DataSvcUtil.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\DataSvcUtil.exe"2⤵PID:4376
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\AddInProcess32.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\AddInProcess32.exe"2⤵PID:4284
-