Windows 7 deprecation
Windows 7 will be removed from tria.ge on 2025-03-31
Analysis
-
max time kernel
56s -
max time network
65s -
platform
windows10-1703_x64 -
resource
win10-20230220-en -
resource tags
arch:x64arch:x86image:win10-20230220-enlocale:en-usos:windows10-1703-x64system -
submitted
03/05/2023, 13:05
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe
Resource
win10-20230220-en
8 signatures
150 seconds
General
-
Target
d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe
-
Size
640KB
-
MD5
f32e6f696a6c68a1f86f1ec6a42ae6de
-
SHA1
a50aff89fd87afe4269c77997d8beb7478d37035
-
SHA256
d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de
-
SHA512
87fab9cd754586b2f31958c6c5b3581ae94fbe95a4fdde3bedc2ded57f150146b75487226c8729f326f2ab6f934fefcffc94067830554c3c3c968356092e6565
-
SSDEEP
12288:0iODgTlUNTxvBCwI/zO+nKomSgBQbAD1NpWaRvZU0LXZ6jEC:pxTsv0XKomSgSbABNpWavzLJUE
Score
10/10
Malware Config
Signatures
-
Detects LgoogLoader payload 1 IoCs
resource yara_rule behavioral1/memory/3940-132-0x00000000018D0000-0x00000000018DD000-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" d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2320 set thread context of 3940 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe 76 -
Suspicious behavior: EnumeratesProcesses 20 IoCs
pid Process 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe -
Suspicious behavior: LoadsDriver 1 IoCs
pid Process 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe -
Suspicious use of AdjustPrivilegeToken 3 IoCs
description pid Process Token: SeDebugPrivilege 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe Token: SeLoadDriverPrivilege 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe Token: SeDebugPrivilege 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe -
Suspicious use of WriteProcessMemory 30 IoCs
description pid Process procid_target PID 2320 wrote to memory of 2496 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe 66 PID 2320 wrote to memory of 2496 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe 66 PID 2320 wrote to memory of 2552 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe 67 PID 2320 wrote to memory of 2552 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe 67 PID 2320 wrote to memory of 2512 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe 68 PID 2320 wrote to memory of 2512 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe 68 PID 2320 wrote to memory of 2672 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe 69 PID 2320 wrote to memory of 2672 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe 69 PID 2320 wrote to memory of 2120 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe 70 PID 2320 wrote to memory of 2120 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe 70 PID 2320 wrote to memory of 3016 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe 71 PID 2320 wrote to memory of 3016 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe 71 PID 2320 wrote to memory of 3052 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe 72 PID 2320 wrote to memory of 3052 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe 72 PID 2320 wrote to memory of 3060 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe 73 PID 2320 wrote to memory of 3060 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe 73 PID 2320 wrote to memory of 3108 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe 74 PID 2320 wrote to memory of 3108 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe 74 PID 2320 wrote to memory of 3240 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe 75 PID 2320 wrote to memory of 3240 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe 75 PID 2320 wrote to memory of 3940 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe 76 PID 2320 wrote to memory of 3940 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe 76 PID 2320 wrote to memory of 3940 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe 76 PID 2320 wrote to memory of 3940 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe 76 PID 2320 wrote to memory of 3940 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe 76 PID 2320 wrote to memory of 3940 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe 76 PID 2320 wrote to memory of 3940 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe 76 PID 2320 wrote to memory of 3940 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe 76 PID 2320 wrote to memory of 3940 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe 76 PID 2320 wrote to memory of 3940 2320 d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe 76
Processes
-
C:\Users\Admin\AppData\Local\Temp\d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.exe"C:\Users\Admin\AppData\Local\Temp\d314e4f2c5e7f5eb404d1ba5e72e44c55641f3a930304088183e27e14c2918de.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:2320 -
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegSvcs.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegSvcs.exe"2⤵PID:2496
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_compiler.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_compiler.exe"2⤵PID:2552
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscorsvw.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscorsvw.exe"2⤵PID:2512
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regsql.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regsql.exe"2⤵PID:2672
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\dfsvc.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\dfsvc.exe"2⤵PID:2120
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\SMSvcHost.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\SMSvcHost.exe"2⤵PID:3016
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\AppLaunch.exe"2⤵PID:3052
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ilasm.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ilasm.exe"2⤵PID:3060
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\AddInProcess.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\AddInProcess.exe"2⤵PID:3108
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe"2⤵PID:3240
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\AddInProcess32.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\AddInProcess32.exe"2⤵PID:3940
-