Analysis
- max time kernel
112s - max time network
139s - platform
windows10-2004_x64 - resource
win10v2004-20220414-en - submitted
31/05/2022, 04:02
Static task
static1
Behavioral task
behavioral1
Sample
06ed40a4c9da968767115328b83b65ce8d2043338576e1e636f3c48ef754ba53.exe
Resource
win7-20220414-en
0 signatures
0 seconds
Behavioral task
behavioral2
Sample
06ed40a4c9da968767115328b83b65ce8d2043338576e1e636f3c48ef754ba53.exe
Resource
win10v2004-20220414-en
0 signatures
0 seconds
General
- Target 06ed40a4c9da968767115328b83b65ce8d2043338576e1e636f3c48ef754ba53.exe
- Size 237KB
- Sample220531-elyjgahebp
- SHA256 06ed40a4c9da968767115328b83b65ce8d2043338576e1e636f3c48ef754ba53
- MD5 e4f2465953609b0dd9a7353c8562285b
- SHA1 449141f50a72eec34a07de811da8edab335810ef
- SHA512 e9492913a49f4524b643e991275928e89f54ab366aed6df4e2f3044baab2e2ef3dfb06183aefb68584f79d1a1f3a3b41756ffc6e6f9abfeb901ddb65df341c6e
- MD5 SHA1 SHA512
Score
5/10
Malware Config
Signatures
- Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2176 set thread context of 212 2176 06ed40a4c9da968767115328b83b65ce8d2043338576e1e636f3c48ef754ba53.exe 87 - Checks processor information in registry 2 TTPs 3 IoCs
Processor information is often read in order to detect sandboxing environments.
description ioc Process Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0\~MHz dw20.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0\ProcessorNameString dw20.exe Key opened \REGISTRY\MACHINE\Hardware\Description\System\CentralProcessor\0 dw20.exe - Enumerates system info in registry 2 TTPs 2 IoCs
description ioc Process Key opened \REGISTRY\MACHINE\Hardware\Description\System\BIOS dw20.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\BIOS\SystemSKU dw20.exe - Suspicious use of AdjustPrivilegeToken 2 IoCs
description pid Process Token: SeBackupPrivilege 4076 dw20.exe Token: SeBackupPrivilege 4076 dw20.exe - Suspicious use of WriteProcessMemory 11 IoCs
description pid Process procid_target PID 2176 wrote to memory of 212 2176 06ed40a4c9da968767115328b83b65ce8d2043338576e1e636f3c48ef754ba53.exe 87 PID 2176 wrote to memory of 212 2176 06ed40a4c9da968767115328b83b65ce8d2043338576e1e636f3c48ef754ba53.exe 87 PID 2176 wrote to memory of 212 2176 06ed40a4c9da968767115328b83b65ce8d2043338576e1e636f3c48ef754ba53.exe 87 PID 2176 wrote to memory of 212 2176 06ed40a4c9da968767115328b83b65ce8d2043338576e1e636f3c48ef754ba53.exe 87 PID 2176 wrote to memory of 212 2176 06ed40a4c9da968767115328b83b65ce8d2043338576e1e636f3c48ef754ba53.exe 87 PID 2176 wrote to memory of 212 2176 06ed40a4c9da968767115328b83b65ce8d2043338576e1e636f3c48ef754ba53.exe 87 PID 2176 wrote to memory of 212 2176 06ed40a4c9da968767115328b83b65ce8d2043338576e1e636f3c48ef754ba53.exe 87 PID 2176 wrote to memory of 212 2176 06ed40a4c9da968767115328b83b65ce8d2043338576e1e636f3c48ef754ba53.exe 87 PID 212 wrote to memory of 4076 212 06ed40a4c9da968767115328b83b65ce8d2043338576e1e636f3c48ef754ba53.exe 88 PID 212 wrote to memory of 4076 212 06ed40a4c9da968767115328b83b65ce8d2043338576e1e636f3c48ef754ba53.exe 88 PID 212 wrote to memory of 4076 212 06ed40a4c9da968767115328b83b65ce8d2043338576e1e636f3c48ef754ba53.exe 88
Processes
-
C:\Users\Admin\AppData\Local\Temp\06ed40a4c9da968767115328b83b65ce8d2043338576e1e636f3c48ef754ba53.exe"C:\Users\Admin\AppData\Local\Temp\06ed40a4c9da968767115328b83b65ce8d2043338576e1e636f3c48ef754ba53.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2176 -
C:\Users\Admin\AppData\Local\Temp\06ed40a4c9da968767115328b83b65ce8d2043338576e1e636f3c48ef754ba53.exe"C:\Users\Admin\AppData\Local\Temp\06ed40a4c9da968767115328b83b65ce8d2043338576e1e636f3c48ef754ba53.exe"2⤵
- Suspicious use of WriteProcessMemory
PID:212 -
C:\Windows\Microsoft.NET\Framework\v2.0.50727\dw20.exedw20.exe -x -s 7723⤵
- Checks processor information in registry
- Enumerates system info in registry
- Suspicious use of AdjustPrivilegeToken
PID:4076
-
-
Network
MITRE ATT&CK Enterprise v6
Replay Monitor
Loading Replay Monitor...
Downloads
- Path C:\Users\Admin\AppData\Local\Microsoft\CLR_v2.0_32\UsageLogs\06ed40a4c9da968767115328b83b65ce8d2043338576e1e636f3c48ef754ba53.exe.log
- Size 500B
- SHA256 688549abc7e5071c610eaf9aa5b0b308f43116b1e14f118ff3e7fe1c969a9cde
- MD5 85dac674f699b59130cd2f4d7e2e04c5
- SHA1 bc28aa347d27da7e9121ed2d823c63daf4ec5f58
- SHA512 a045d0a3c45aa54ca922056139b13605fbefa48365b9b17ff513d2e8d61a214df6119adb7ba9ad4fe7ffb61c5244c5514704499efbf3aca7c9a954796fea76c3
- MD5 SHA1 SHA512