Analysis
-
max time kernel
150s -
max time network
147s -
platform
windows10-2004_x64 -
resource
win10v2004-20240508-en -
resource tags
arch:x64arch:x86image:win10v2004-20240508-enlocale:en-usos:windows10-2004-x64system -
submitted
25-05-2024 03:58
Static task
static1
Behavioral task
behavioral1
Sample
2024-05-25_868b71dbdde7f7972bbf310f02496703_cryptolocker.exe
Resource
win7-20240508-en
Behavioral task
behavioral2
Sample
2024-05-25_868b71dbdde7f7972bbf310f02496703_cryptolocker.exe
Resource
win10v2004-20240508-en
General
-
Target
2024-05-25_868b71dbdde7f7972bbf310f02496703_cryptolocker.exe
-
Size
31KB
-
MD5
868b71dbdde7f7972bbf310f02496703
-
SHA1
3ba1d4f60132d8f2934240e6aabcfba02b3ae80d
-
SHA256
871446ecce0e0186a2707c23072695359d288f975f7f9ec00e90c55d88386a10
-
SHA512
0d346b841206b62c0a57838971f53d1070a51136187cb811352d34bab213f4bdcd9fa77b3eb020b1d9d67b313d1f1d8ac883ef6b88d88195fe13f1c201a8a40b
-
SSDEEP
384:bG74uGLLQRcsdeQ72ngEr4K7YmE8j60nrlwfjDUGTjYr:bG74zYcgT/Ekd0ryfjfYr
Malware Config
Signatures
-
Detection of CryptoLocker Variants 5 IoCs
resource yara_rule behavioral2/memory/4256-0-0x0000000008000000-0x000000000800A000-memory.dmp CryptoLocker_rule2 behavioral2/files/0x000a0000000233c0-12.dat CryptoLocker_rule2 behavioral2/memory/392-17-0x0000000008000000-0x000000000800A000-memory.dmp CryptoLocker_rule2 behavioral2/memory/4256-18-0x0000000008000000-0x000000000800A000-memory.dmp CryptoLocker_rule2 behavioral2/memory/392-27-0x0000000008000000-0x000000000800A000-memory.dmp CryptoLocker_rule2 -
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-4124900551-4068476067-3491212533-1000\Control Panel\International\Geo\Nation 2024-05-25_868b71dbdde7f7972bbf310f02496703_cryptolocker.exe -
Executes dropped EXE 1 IoCs
pid Process 392 hasfj.exe -
Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s).
-
Suspicious use of WriteProcessMemory 3 IoCs
description pid Process procid_target PID 4256 wrote to memory of 392 4256 2024-05-25_868b71dbdde7f7972bbf310f02496703_cryptolocker.exe 83 PID 4256 wrote to memory of 392 4256 2024-05-25_868b71dbdde7f7972bbf310f02496703_cryptolocker.exe 83 PID 4256 wrote to memory of 392 4256 2024-05-25_868b71dbdde7f7972bbf310f02496703_cryptolocker.exe 83
Processes
-
C:\Users\Admin\AppData\Local\Temp\2024-05-25_868b71dbdde7f7972bbf310f02496703_cryptolocker.exe"C:\Users\Admin\AppData\Local\Temp\2024-05-25_868b71dbdde7f7972bbf310f02496703_cryptolocker.exe"1⤵
- Checks computer location settings
- Suspicious use of WriteProcessMemory
PID:4256 -
C:\Users\Admin\AppData\Local\Temp\hasfj.exe"C:\Users\Admin\AppData\Local\Temp\hasfj.exe"2⤵
- Executes dropped EXE
PID:392
-
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
-
Filesize
31KB
MD5bf83a6739eca779926499ebb5701e87f
SHA12c64813e2aa2638e4fe3c0c535d7bac3867b1c26
SHA256da0cc0c6f23f84a0ecbe1b1115cde4474a4eb75992f0996a129a212d20a2aab3
SHA512150b3578adb363ce10669e86016a40a469a176d6d042ce6a9d77a5d15643dec649928c9f10c80de90dda9470263bb7078f628565b779ef5213a653e9e6f01bd2