Analysis
-
max time kernel
259s -
max time network
313s -
platform
windows10-2004_x64 -
resource
win10v2004-20221111-en -
resource tags
arch:x64arch:x86image:win10v2004-20221111-enlocale:en-usos:windows10-2004-x64system -
submitted
03/12/2022, 05:05
Static task
static1
Behavioral task
behavioral1
Sample
53ee1582c84b70371a35ff0850521050db0127391218ade6e398c4c72c4ad875.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
53ee1582c84b70371a35ff0850521050db0127391218ade6e398c4c72c4ad875.exe
Resource
win10v2004-20221111-en
General
-
Target
53ee1582c84b70371a35ff0850521050db0127391218ade6e398c4c72c4ad875.exe
-
Size
96KB
-
MD5
25485b5c193c4445302ca3a951f6e1d0
-
SHA1
1922e83e558a2200a98b1779d0776370d3a14f45
-
SHA256
53ee1582c84b70371a35ff0850521050db0127391218ade6e398c4c72c4ad875
-
SHA512
f86fef76bdedc835e4a1173b3aa3f97265750f856d39806d110c4076627514ecf4a3793cce036fadb7b3e9134933443cb304b932898deaee3359ae09e6f98b84
-
SSDEEP
1536:8V6/l1TwNq9tAna04OLQ+0DAjS9vnvCFTXob1Uai3LWyvojQKAdTspU:n/Hgq9UjS9vKFzCihLWywjQKA9OU
Malware Config
Signatures
-
Maps connected drives based on registry 3 TTPs 2 IoCs
Disk information is often read in order to detect sandboxing environments.
description ioc Process Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\Disk\Enum 53ee1582c84b70371a35ff0850521050db0127391218ade6e398c4c72c4ad875.exe Key value queried \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\disk\Enum\0 53ee1582c84b70371a35ff0850521050db0127391218ade6e398c4c72c4ad875.exe -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2552 set thread context of 4392 2552 53ee1582c84b70371a35ff0850521050db0127391218ade6e398c4c72c4ad875.exe 80 -
Suspicious use of SetWindowsHookEx 2 IoCs
pid Process 2552 53ee1582c84b70371a35ff0850521050db0127391218ade6e398c4c72c4ad875.exe 4392 53ee1582c84b70371a35ff0850521050db0127391218ade6e398c4c72c4ad875.exe -
Suspicious use of WriteProcessMemory 9 IoCs
description pid Process procid_target PID 2552 wrote to memory of 4392 2552 53ee1582c84b70371a35ff0850521050db0127391218ade6e398c4c72c4ad875.exe 80 PID 2552 wrote to memory of 4392 2552 53ee1582c84b70371a35ff0850521050db0127391218ade6e398c4c72c4ad875.exe 80 PID 2552 wrote to memory of 4392 2552 53ee1582c84b70371a35ff0850521050db0127391218ade6e398c4c72c4ad875.exe 80 PID 2552 wrote to memory of 4392 2552 53ee1582c84b70371a35ff0850521050db0127391218ade6e398c4c72c4ad875.exe 80 PID 2552 wrote to memory of 4392 2552 53ee1582c84b70371a35ff0850521050db0127391218ade6e398c4c72c4ad875.exe 80 PID 2552 wrote to memory of 4392 2552 53ee1582c84b70371a35ff0850521050db0127391218ade6e398c4c72c4ad875.exe 80 PID 2552 wrote to memory of 4392 2552 53ee1582c84b70371a35ff0850521050db0127391218ade6e398c4c72c4ad875.exe 80 PID 2552 wrote to memory of 4392 2552 53ee1582c84b70371a35ff0850521050db0127391218ade6e398c4c72c4ad875.exe 80 PID 2552 wrote to memory of 4392 2552 53ee1582c84b70371a35ff0850521050db0127391218ade6e398c4c72c4ad875.exe 80
Processes
-
C:\Users\Admin\AppData\Local\Temp\53ee1582c84b70371a35ff0850521050db0127391218ade6e398c4c72c4ad875.exe"C:\Users\Admin\AppData\Local\Temp\53ee1582c84b70371a35ff0850521050db0127391218ade6e398c4c72c4ad875.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2552 -
C:\Users\Admin\AppData\Local\Temp\53ee1582c84b70371a35ff0850521050db0127391218ade6e398c4c72c4ad875.exe742⤵
- Maps connected drives based on registry
- Suspicious use of SetWindowsHookEx
PID:4392
-