Analysis
-
max time kernel
150s -
max time network
151s -
platform
windows10-2004_x64 -
resource
win10v2004-20240508-en -
resource tags
arch:x64arch:x86image:win10v2004-20240508-enlocale:en-usos:windows10-2004-x64system -
submitted
28-05-2024 03:37
Behavioral task
behavioral1
Sample
2024-05-28_559326fe6a5be56f834f8ab05f419984_cryptolocker.exe
Resource
win7-20240508-en
Behavioral task
behavioral2
Sample
2024-05-28_559326fe6a5be56f834f8ab05f419984_cryptolocker.exe
Resource
win10v2004-20240508-en
General
-
Target
2024-05-28_559326fe6a5be56f834f8ab05f419984_cryptolocker.exe
-
Size
34KB
-
MD5
559326fe6a5be56f834f8ab05f419984
-
SHA1
cadc14110fa586aeb274a232ddf24126e93a92ca
-
SHA256
e59245e83b7ce24f82683d2108e56fb5d63d03ac378106af15c140c662b47c33
-
SHA512
926c4595ca74462dbce8f6a968ca2ce7fc10b954c2f5ca6fdef66e0153057035ae5675d4f83e89834aed0650369ad360d9155f2f20a32679530a7737d2123413
-
SSDEEP
768:bFPm5zusFUB2preAr+Ofjg0S16avdrQFiLjJvtXl:bFPmpiif/oc+vXl
Malware Config
Signatures
-
Detection of CryptoLocker Variants 5 IoCs
resource yara_rule behavioral2/memory/3812-0-0x0000000008000000-0x000000000800E000-memory.dmp CryptoLocker_rule2 behavioral2/files/0x0008000000022f51-13.dat CryptoLocker_rule2 behavioral2/memory/3972-19-0x0000000008000000-0x000000000800E000-memory.dmp CryptoLocker_rule2 behavioral2/memory/3812-17-0x0000000008000000-0x000000000800E000-memory.dmp CryptoLocker_rule2 behavioral2/memory/3972-28-0x0000000008000000-0x000000000800E000-memory.dmp CryptoLocker_rule2 -
UPX dump on OEP (original entry point) 5 IoCs
resource yara_rule behavioral2/memory/3812-0-0x0000000008000000-0x000000000800E000-memory.dmp UPX behavioral2/files/0x0008000000022f51-13.dat UPX behavioral2/memory/3972-19-0x0000000008000000-0x000000000800E000-memory.dmp UPX behavioral2/memory/3812-17-0x0000000008000000-0x000000000800E000-memory.dmp UPX behavioral2/memory/3972-28-0x0000000008000000-0x000000000800E000-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-1337824034-2731376981-3755436523-1000\Control Panel\International\Geo\Nation 2024-05-28_559326fe6a5be56f834f8ab05f419984_cryptolocker.exe -
Executes dropped EXE 1 IoCs
pid Process 3972 lossy.exe -
resource yara_rule behavioral2/memory/3812-0-0x0000000008000000-0x000000000800E000-memory.dmp upx behavioral2/files/0x0008000000022f51-13.dat upx behavioral2/memory/3972-19-0x0000000008000000-0x000000000800E000-memory.dmp upx behavioral2/memory/3812-17-0x0000000008000000-0x000000000800E000-memory.dmp upx behavioral2/memory/3972-28-0x0000000008000000-0x000000000800E000-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 3812 wrote to memory of 3972 3812 2024-05-28_559326fe6a5be56f834f8ab05f419984_cryptolocker.exe 83 PID 3812 wrote to memory of 3972 3812 2024-05-28_559326fe6a5be56f834f8ab05f419984_cryptolocker.exe 83 PID 3812 wrote to memory of 3972 3812 2024-05-28_559326fe6a5be56f834f8ab05f419984_cryptolocker.exe 83
Processes
-
C:\Users\Admin\AppData\Local\Temp\2024-05-28_559326fe6a5be56f834f8ab05f419984_cryptolocker.exe"C:\Users\Admin\AppData\Local\Temp\2024-05-28_559326fe6a5be56f834f8ab05f419984_cryptolocker.exe"1⤵
- Checks computer location settings
- Suspicious use of WriteProcessMemory
PID:3812 -
C:\Users\Admin\AppData\Local\Temp\lossy.exe"C:\Users\Admin\AppData\Local\Temp\lossy.exe"2⤵
- Executes dropped EXE
PID:3972
-
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
-
Filesize
35KB
MD50115dea60f5592f7ebfbd4eca7c7a0d0
SHA135c10fcd582ad60cafcce8f779a8abe43f6902b7
SHA2563d4250b40fc822359601480b3206b8b51a1b9e4da293da9ddbd659b5575131f6
SHA512c2e01605ccef93da444cbf42122415da8d13354e66b351b08396b6f9bb8321fdb6a1afe8e12df62454c8fb91a811f13cbb5c06adc72f10d7bf92e3c6a5e41784