Analysis
- max time kernel
150s - max time network
153s - platform
windows10-2004_x64 - resource
win10v2004-20240611-en - resource tags
arch:x64arch:x86image:win10v2004-20240611-enlocale:en-usos:windows10-2004-x64system - submitted
13/06/2024, 03:49
Static task
static1
2 signatures
Behavioral task
behavioral1
Sample
2024-06-13_b58f811325c6b68c7dc02c24d6950f86_cryptolocker.exe
Resource
win7-20240611-en
5 signatures
150 seconds
Behavioral task
behavioral2
Sample
2024-06-13_b58f811325c6b68c7dc02c24d6950f86_cryptolocker.exe
Resource
win10v2004-20240611-en
5 signatures
150 seconds
General
- Target 2024-06-13_b58f811325c6b68c7dc02c24d6950f86_cryptolocker.exe
- Size 44KB
- Sample240613-edlvpsxank
- SHA256 14512f682a657e89b4d507d2c0d189f05698f379b2738b1862ba561a57a9e1ec
- MD5 b58f811325c6b68c7dc02c24d6950f86
- SHA1 055bc380c44ab07061f7ff5f9c8c1ed088a81066
- SHA512 72d013e1f9a337f7723ac84f0e1f1b7b2905b9c7010c876817f5c2828435a4a63949683407da67e0d33b72a47b37937df662b692981aa61e26811a3608b84c0f
- SSDEEP 768:bCDOw9UiaKHfjnD0S16avdrQFiLjJvtAHtBh:bCDOw9aMDooc+vANX
- MD5 SHA1 SHA512 SSDEEP
Score
9/10
Malware Config
Signatures
- Detection of CryptoLocker Variants 5 IoCs
resource yara_rule behavioral2/memory/2220-0-0x0000000008000000-0x000000000800A000-memory.dmp CryptoLocker_rule2 behavioral2/files/0x000700000002336e-13.dat CryptoLocker_rule2 behavioral2/memory/2220-17-0x0000000008000000-0x000000000800A000-memory.dmp CryptoLocker_rule2 behavioral2/memory/452-18-0x0000000008000000-0x000000000800A000-memory.dmp CryptoLocker_rule2 behavioral2/memory/452-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-200405930-3877336739-3533750831-1000\Control Panel\International\Geo\Nation 2024-06-13_b58f811325c6b68c7dc02c24d6950f86_cryptolocker.exe - Executes dropped EXE 1 IoCs
pid Process 452 lossy.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 2220 wrote to memory of 452 2220 2024-06-13_b58f811325c6b68c7dc02c24d6950f86_cryptolocker.exe 81 PID 2220 wrote to memory of 452 2220 2024-06-13_b58f811325c6b68c7dc02c24d6950f86_cryptolocker.exe 81 PID 2220 wrote to memory of 452 2220 2024-06-13_b58f811325c6b68c7dc02c24d6950f86_cryptolocker.exe 81
Processes
-
C:\Users\Admin\AppData\Local\Temp\2024-06-13_b58f811325c6b68c7dc02c24d6950f86_cryptolocker.exe"C:\Users\Admin\AppData\Local\Temp\2024-06-13_b58f811325c6b68c7dc02c24d6950f86_cryptolocker.exe"1⤵
- Checks computer location settings
- Suspicious use of WriteProcessMemory
PID:2220 -
C:\Users\Admin\AppData\Local\Temp\lossy.exe"C:\Users\Admin\AppData\Local\Temp\lossy.exe"2⤵
- Executes dropped EXE
PID:452
-
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
- Path C:\Users\Admin\AppData\Local\Temp\lossy.exe
- Size 44KB
- SHA256 c28071f0760067c4f94f08769f9e10e8390274826106c76792a928d99810d84d
- MD5 16f17def4eacb40aa63a6169990f37e1
- SHA1 adafcf2687e461bacfd145d25a75238ed2c9f3e2
- SHA512 2f993ed71e33017b51591ecddbbb01aa2828c396ba79c840bc4e3c5978471bf92dee93ffdc5920be73c54d7b84b3953cade258ef8e40dc5be9539447a77805ef
- SSDEEP 768:bCDOw9UiaKHfjnD0S16avdrQFiLjJvtAHtBY:bCDOw9aMDooc+vAN6
- MD5 SHA1 SHA512 SSDEEP