Analysis
-
max time kernel
110s -
max time network
143s -
platform
windows10-2004_x64 -
resource
win10v2004-20220812-en -
resource tags
arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system -
submitted
07/11/2022, 03:43
Static task
static1
Behavioral task
behavioral1
Sample
bd33533bfcb783cb67a451d55c0f14230d4f61c53b45702e30230e3f051e4157.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
bd33533bfcb783cb67a451d55c0f14230d4f61c53b45702e30230e3f051e4157.exe
Resource
win10v2004-20220812-en
General
-
Target
bd33533bfcb783cb67a451d55c0f14230d4f61c53b45702e30230e3f051e4157.exe
-
Size
88KB
-
MD5
04ad265c9d429d0f07a79b4d5b35adee
-
SHA1
3a5270d40219b446d27a4fe1371ec2c069185824
-
SHA256
bd33533bfcb783cb67a451d55c0f14230d4f61c53b45702e30230e3f051e4157
-
SHA512
fc629ce84ce992a6592bdba5d507a2d076de1fbae4034058045cb98649ca74c95ac1917c67243ef9fa10265a47f90781db413db7f29f8c70340089b64ec461ed
-
SSDEEP
1536:nCirdxnVGdg25ny7r3lkE5B+v7DLIAqqdlrgv:7Gdg2hUrVpBq7DLIAqqdlm
Malware Config
Signatures
-
Checks computer location settings 2 TTPs 1 IoCs
Looks up country code configured in the registry, likely geofence.
description ioc Process Key value queried \REGISTRY\USER\S-1-5-21-2891029575-1462575-1165213807-1000\Control Panel\International\Geo\Nation bd33533bfcb783cb67a451d55c0f14230d4f61c53b45702e30230e3f051e4157.exe -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2296 set thread context of 4960 2296 bd33533bfcb783cb67a451d55c0f14230d4f61c53b45702e30230e3f051e4157.exe 76 -
Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s). Likely ransomware behaviour.
-
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 2296 bd33533bfcb783cb67a451d55c0f14230d4f61c53b45702e30230e3f051e4157.exe -
Suspicious use of WriteProcessMemory 7 IoCs
description pid Process procid_target PID 2296 wrote to memory of 4960 2296 bd33533bfcb783cb67a451d55c0f14230d4f61c53b45702e30230e3f051e4157.exe 76 PID 2296 wrote to memory of 4960 2296 bd33533bfcb783cb67a451d55c0f14230d4f61c53b45702e30230e3f051e4157.exe 76 PID 2296 wrote to memory of 4960 2296 bd33533bfcb783cb67a451d55c0f14230d4f61c53b45702e30230e3f051e4157.exe 76 PID 2296 wrote to memory of 4960 2296 bd33533bfcb783cb67a451d55c0f14230d4f61c53b45702e30230e3f051e4157.exe 76 PID 2296 wrote to memory of 4960 2296 bd33533bfcb783cb67a451d55c0f14230d4f61c53b45702e30230e3f051e4157.exe 76 PID 2296 wrote to memory of 4960 2296 bd33533bfcb783cb67a451d55c0f14230d4f61c53b45702e30230e3f051e4157.exe 76 PID 2296 wrote to memory of 4960 2296 bd33533bfcb783cb67a451d55c0f14230d4f61c53b45702e30230e3f051e4157.exe 76
Processes
-
C:\Users\Admin\AppData\Local\Temp\bd33533bfcb783cb67a451d55c0f14230d4f61c53b45702e30230e3f051e4157.exe"C:\Users\Admin\AppData\Local\Temp\bd33533bfcb783cb67a451d55c0f14230d4f61c53b45702e30230e3f051e4157.exe"1⤵
- Checks computer location settings
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2296 -
C:\Users\Admin\AppData\Local\Temp\bd33533bfcb783cb67a451d55c0f14230d4f61c53b45702e30230e3f051e4157.exeC:\Users\Admin\AppData\Local\Temp\bd33533bfcb783cb67a451d55c0f14230d4f61c53b45702e30230e3f051e4157.exe2⤵PID:4960
-