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
11-06-2023 13:04
Static task
static1
Behavioral task
behavioral1
Sample
8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe
Resource
win7-20230220-en
Behavioral task
behavioral2
Sample
8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe
Resource
win10v2004-20230220-en
General
-
Target
8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe
-
Size
402KB
-
MD5
64611ca692664bc54b040e4b01c38ff4
-
SHA1
83c4893ea4e7bbe82cd5b9ad197e37462e9c43c6
-
SHA256
8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e
-
SHA512
d98649ab0b002a4bfadb31ae0105b61153cf17ba39e1f81a6c6d697e39958d62b7384e15332e5eb9ca97910e15dfb3774666740c851ecde8aac65eba803e6c6b
-
SSDEEP
3072:8mXHmM0YFSJrXx0ooARRMkAHFIxobrvZkJv6SjaFvVmuLyRpPS68urGh3Lzs/vqH:Z10YMmooARiXCFT2Fp6SQaofZAf
Malware Config
Signatures
-
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" 8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 308 set thread context of 1804 308 8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe 34 -
Program crash 1 IoCs
pid pid_target Process procid_target 1904 1804 WerFault.exe 34 -
Suspicious behavior: EnumeratesProcesses 7 IoCs
pid Process 308 8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe 308 8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe 308 8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe 308 8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe 308 8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe 308 8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe 308 8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe -
Suspicious behavior: LoadsDriver 1 IoCs
pid Process 308 8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe -
Suspicious use of AdjustPrivilegeToken 3 IoCs
description pid Process Token: SeDebugPrivilege 308 8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe Token: SeDebugPrivilege 308 8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe Token: SeLoadDriverPrivilege 308 8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe -
Suspicious use of WriteProcessMemory 39 IoCs
description pid Process procid_target PID 308 wrote to memory of 1772 308 8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe 27 PID 308 wrote to memory of 1772 308 8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe 27 PID 308 wrote to memory of 1772 308 8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe 27 PID 308 wrote to memory of 1760 308 8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe 28 PID 308 wrote to memory of 1760 308 8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe 28 PID 308 wrote to memory of 1760 308 8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe 28 PID 308 wrote to memory of 632 308 8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe 29 PID 308 wrote to memory of 632 308 8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe 29 PID 308 wrote to memory of 632 308 8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe 29 PID 308 wrote to memory of 1320 308 8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe 30 PID 308 wrote to memory of 1320 308 8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe 30 PID 308 wrote to memory of 1320 308 8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe 30 PID 308 wrote to memory of 592 308 8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe 31 PID 308 wrote to memory of 592 308 8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe 31 PID 308 wrote to memory of 592 308 8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe 31 PID 308 wrote to memory of 664 308 8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe 32 PID 308 wrote to memory of 664 308 8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe 32 PID 308 wrote to memory of 664 308 8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe 32 PID 308 wrote to memory of 1832 308 8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe 33 PID 308 wrote to memory of 1832 308 8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe 33 PID 308 wrote to memory of 1832 308 8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe 33 PID 308 wrote to memory of 1804 308 8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe 34 PID 308 wrote to memory of 1804 308 8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe 34 PID 308 wrote to memory of 1804 308 8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe 34 PID 308 wrote to memory of 1804 308 8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe 34 PID 308 wrote to memory of 1804 308 8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe 34 PID 308 wrote to memory of 1804 308 8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe 34 PID 308 wrote to memory of 1804 308 8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe 34 PID 308 wrote to memory of 1804 308 8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe 34 PID 308 wrote to memory of 1804 308 8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe 34 PID 308 wrote to memory of 1804 308 8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe 34 PID 308 wrote to memory of 1804 308 8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe 34 PID 308 wrote to memory of 1804 308 8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe 34 PID 308 wrote to memory of 1804 308 8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe 34 PID 308 wrote to memory of 1804 308 8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe 34 PID 1804 wrote to memory of 1904 1804 Setup.exe 35 PID 1804 wrote to memory of 1904 1804 Setup.exe 35 PID 1804 wrote to memory of 1904 1804 Setup.exe 35 PID 1804 wrote to memory of 1904 1804 Setup.exe 35
Processes
-
C:\Users\Admin\AppData\Local\Temp\8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.exe"C:\Users\Admin\AppData\Local\Temp\8080f28eb2c4e6406a8df0f3ed8c1f42f8bb038a35398e13d29c618ade13d06e.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:308 -
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regbrowsers.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regbrowsers.exe"2⤵PID:1772
-
-
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:1760
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\AddInProcess.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\AddInProcess.exe"2⤵PID:632
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\cvtres.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\cvtres.exe"2⤵PID:1320
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ServiceModelReg.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ServiceModelReg.exe"2⤵PID:592
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ilasm.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ilasm.exe"2⤵PID:664
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\csc.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\csc.exe"2⤵PID:1832
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\SetupCache\v4.7.03062\Setup.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\SetupCache\v4.7.03062\Setup.exe"2⤵
- Suspicious use of WriteProcessMemory
PID:1804 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 1804 -s 3043⤵
- Program crash
PID:1904
-
-