Analysis
-
max time kernel
150s -
max time network
150s -
platform
windows10-2004_x64 -
resource
win10v2004-20240426-en -
resource tags
arch:x64arch:x86image:win10v2004-20240426-enlocale:en-usos:windows10-2004-x64system -
submitted
29-05-2024 01:24
Behavioral task
behavioral1
Sample
2024-05-29_a2e9b8c9c08c42204b16ecac24acb7f3_cryptolocker.exe
Resource
win7-20240221-en
Behavioral task
behavioral2
Sample
2024-05-29_a2e9b8c9c08c42204b16ecac24acb7f3_cryptolocker.exe
Resource
win10v2004-20240426-en
General
-
Target
2024-05-29_a2e9b8c9c08c42204b16ecac24acb7f3_cryptolocker.exe
-
Size
41KB
-
MD5
a2e9b8c9c08c42204b16ecac24acb7f3
-
SHA1
6261ed66ca57319374fdf926e05dbf726b43135d
-
SHA256
6934a9ee12b9a291a5ddd539e033e7e71872fc2e67b93317ed964116464ae972
-
SHA512
2f623b874a9c49b26bf3e64552e84269c2e24867334cfe14997bb66453c147024cd8a6bd2509073bcc98105e7aa8fd0b2370fd91ca176af5b0e40eae01647cfc
-
SSDEEP
768:ba74zYcgT/EkdCQgpwXFXSqQXfj0xKsmoX:ba6YcA/Xk3wXFXSqAJqX
Malware Config
Signatures
-
Detection of CryptoLocker Variants 4 IoCs
resource yara_rule behavioral2/memory/2040-0-0x0000000008000000-0x000000000800F000-memory.dmp CryptoLocker_rule2 behavioral2/files/0x0008000000023442-13.dat CryptoLocker_rule2 behavioral2/memory/2040-17-0x0000000008000000-0x000000000800F000-memory.dmp CryptoLocker_rule2 behavioral2/memory/4080-26-0x0000000008000000-0x000000000800F000-memory.dmp CryptoLocker_rule2 -
UPX dump on OEP (original entry point) 4 IoCs
resource yara_rule behavioral2/memory/2040-0-0x0000000008000000-0x000000000800F000-memory.dmp UPX behavioral2/files/0x0008000000023442-13.dat UPX behavioral2/memory/2040-17-0x0000000008000000-0x000000000800F000-memory.dmp UPX behavioral2/memory/4080-26-0x0000000008000000-0x000000000800F000-memory.dmp UPX -
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-4018855536-2201274732-320770143-1000\Control Panel\International\Geo\Nation 2024-05-29_a2e9b8c9c08c42204b16ecac24acb7f3_cryptolocker.exe -
Executes dropped EXE 1 IoCs
pid Process 4080 hasfj.exe -
resource yara_rule behavioral2/memory/2040-0-0x0000000008000000-0x000000000800F000-memory.dmp upx behavioral2/files/0x0008000000023442-13.dat upx behavioral2/memory/2040-17-0x0000000008000000-0x000000000800F000-memory.dmp upx behavioral2/memory/4080-26-0x0000000008000000-0x000000000800F000-memory.dmp upx -
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 2040 wrote to memory of 4080 2040 2024-05-29_a2e9b8c9c08c42204b16ecac24acb7f3_cryptolocker.exe 85 PID 2040 wrote to memory of 4080 2040 2024-05-29_a2e9b8c9c08c42204b16ecac24acb7f3_cryptolocker.exe 85 PID 2040 wrote to memory of 4080 2040 2024-05-29_a2e9b8c9c08c42204b16ecac24acb7f3_cryptolocker.exe 85
Processes
-
C:\Users\Admin\AppData\Local\Temp\2024-05-29_a2e9b8c9c08c42204b16ecac24acb7f3_cryptolocker.exe"C:\Users\Admin\AppData\Local\Temp\2024-05-29_a2e9b8c9c08c42204b16ecac24acb7f3_cryptolocker.exe"1⤵
- Checks computer location settings
- Suspicious use of WriteProcessMemory
PID:2040 -
C:\Users\Admin\AppData\Local\Temp\hasfj.exe"C:\Users\Admin\AppData\Local\Temp\hasfj.exe"2⤵
- Executes dropped EXE
PID:4080
-
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
-
Filesize
41KB
MD5ee09a313db17a60979db62736bb00573
SHA167f6a03648322238b6b49f6f6ff4f9469f2cfd46
SHA256565f4281f31a4967c24cae81b4c5f1641b17ef2e30d1e133aa3f83da9ad172e2
SHA512344cf17a7d6dfa475362da6fdbfeaccd264cf3bd65100ff89614a1f5d6163d5ccc8a1d976c918d38998a4e787185918e3567d1e17118682ac65141fb59f32d48