Analysis
-
max time kernel
9s -
max time network
105s -
platform
windows10-2004_x64 -
resource
win10v2004-20231215-en -
resource tags
arch:x64arch:x86image:win10v2004-20231215-enlocale:en-usos:windows10-2004-x64system -
submitted
25/12/2023, 07:06
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
0d9cb0a03d97a42dbdd5f1228f5f8339.exe
Resource
win7-20231215-en
2 signatures
150 seconds
Behavioral task
behavioral2
Sample
0d9cb0a03d97a42dbdd5f1228f5f8339.exe
Resource
win10v2004-20231215-en
5 signatures
150 seconds
General
-
Target
0d9cb0a03d97a42dbdd5f1228f5f8339.exe
-
Size
221KB
-
MD5
0d9cb0a03d97a42dbdd5f1228f5f8339
-
SHA1
30904e517db3a13c86cba615521e0afaae3f9235
-
SHA256
bddb300d01df8c12d8661edeae0552c422538b0f4bd86440948ae1445f15feed
-
SHA512
29abdf91f3a0d3845514fff1e8fb504492c22032218d036de0ca575326ca8dcee0767503c8ee77191b2d00f95722c5ce87ac4a597ea2c48cb4f3811113be383f
-
SSDEEP
6144:+KpiGC0eL5HTxXgcpPTTOc9X3Hz8hG1OSv3Z:+rLL5HTlrPTUA1OSvJ
Score
10/10
Malware Config
Signatures
-
Modifies WinLogon for persistence 2 TTPs 1 IoCs
description ioc Process Set value (str) \REGISTRY\MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows NT\CurrentVersion\Winlogon\userinit = "C:\\Windows\\system32\\sdra64.exe," 0d9cb0a03d97a42dbdd5f1228f5f8339.exe -
Drops file in System32 directory 2 IoCs
description ioc Process File opened for modification C:\Windows\SysWOW64\sdra64.exe 0d9cb0a03d97a42dbdd5f1228f5f8339.exe File created C:\Windows\SysWOW64\sdra64.exe 0d9cb0a03d97a42dbdd5f1228f5f8339.exe -
Suspicious behavior: EnumeratesProcesses 4 IoCs
pid Process 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe -
Suspicious use of AdjustPrivilegeToken 1 IoCs
description pid Process Token: SeDebugPrivilege 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe -
Suspicious use of WriteProcessMemory 64 IoCs
description pid Process procid_target PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4 PID 1676 wrote to memory of 616 1676 0d9cb0a03d97a42dbdd5f1228f5f8339.exe 4
Processes
-
C:\Windows\system32\winlogon.exewinlogon.exe1⤵PID:616
-
C:\Users\Admin\AppData\Local\Temp\0d9cb0a03d97a42dbdd5f1228f5f8339.exe"C:\Users\Admin\AppData\Local\Temp\0d9cb0a03d97a42dbdd5f1228f5f8339.exe"1⤵
- Modifies WinLogon for persistence
- Drops file in System32 directory
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:1676