Analysis
-
max time kernel
124s -
max time network
146s -
platform
windows10-2004_x64 -
resource
win10v2004-20240426-en -
resource tags
arch:x64arch:x86image:win10v2004-20240426-enlocale:en-usos:windows10-2004-x64system -
submitted
14/05/2024, 04:30
Behavioral task
behavioral1
Sample
2024-05-14_48a2b4ded03f37a671ba06eeca645455_cryptolocker.exe
Resource
win7-20240221-en
Behavioral task
behavioral2
Sample
2024-05-14_48a2b4ded03f37a671ba06eeca645455_cryptolocker.exe
Resource
win10v2004-20240426-en
General
-
Target
2024-05-14_48a2b4ded03f37a671ba06eeca645455_cryptolocker.exe
-
Size
51KB
-
MD5
48a2b4ded03f37a671ba06eeca645455
-
SHA1
e7242e42b4cc9b27356b179c35f99fb680777372
-
SHA256
acd21330821937a8e5c830cb1d6b396a085962870b23df696783cd67096216ec
-
SHA512
cfb66f5df7988307b5f47812e7c52b10fee641ad02e7603a2330f86b1c41ab5bd97764126def62a5d1fdd08d172fde3c7cf4196116a3ff9ab24a1b2009d74ab0
-
SSDEEP
768:bODOw9UiamWUB2preAr+OfjH/0S16avdrQFiLjJvtOL:bODOw9acifAoc+v4
Malware Config
Signatures
-
Detection of CryptoLocker Variants 5 IoCs
resource yara_rule behavioral2/memory/4800-0-0x0000000008000000-0x000000000800F000-memory.dmp CryptoLocker_rule2 behavioral2/files/0x0006000000023288-13.dat CryptoLocker_rule2 behavioral2/memory/3516-18-0x0000000008000000-0x000000000800F000-memory.dmp CryptoLocker_rule2 behavioral2/memory/4800-17-0x0000000008000000-0x000000000800F000-memory.dmp CryptoLocker_rule2 behavioral2/memory/3516-27-0x0000000008000000-0x000000000800F000-memory.dmp CryptoLocker_rule2 -
UPX dump on OEP (original entry point) 5 IoCs
resource yara_rule behavioral2/memory/4800-0-0x0000000008000000-0x000000000800F000-memory.dmp UPX behavioral2/files/0x0006000000023288-13.dat UPX behavioral2/memory/3516-18-0x0000000008000000-0x000000000800F000-memory.dmp UPX behavioral2/memory/4800-17-0x0000000008000000-0x000000000800F000-memory.dmp UPX behavioral2/memory/3516-27-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-3906287020-2915474608-1755617787-1000\Control Panel\International\Geo\Nation 2024-05-14_48a2b4ded03f37a671ba06eeca645455_cryptolocker.exe -
Executes dropped EXE 1 IoCs
pid Process 3516 lossy.exe -
resource yara_rule behavioral2/memory/4800-0-0x0000000008000000-0x000000000800F000-memory.dmp upx behavioral2/files/0x0006000000023288-13.dat upx behavioral2/memory/3516-18-0x0000000008000000-0x000000000800F000-memory.dmp upx behavioral2/memory/4800-17-0x0000000008000000-0x000000000800F000-memory.dmp upx behavioral2/memory/3516-27-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 4800 wrote to memory of 3516 4800 2024-05-14_48a2b4ded03f37a671ba06eeca645455_cryptolocker.exe 82 PID 4800 wrote to memory of 3516 4800 2024-05-14_48a2b4ded03f37a671ba06eeca645455_cryptolocker.exe 82 PID 4800 wrote to memory of 3516 4800 2024-05-14_48a2b4ded03f37a671ba06eeca645455_cryptolocker.exe 82
Processes
-
C:\Users\Admin\AppData\Local\Temp\2024-05-14_48a2b4ded03f37a671ba06eeca645455_cryptolocker.exe"C:\Users\Admin\AppData\Local\Temp\2024-05-14_48a2b4ded03f37a671ba06eeca645455_cryptolocker.exe"1⤵
- Checks computer location settings
- Suspicious use of WriteProcessMemory
PID:4800 -
C:\Users\Admin\AppData\Local\Temp\lossy.exe"C:\Users\Admin\AppData\Local\Temp\lossy.exe"2⤵
- Executes dropped EXE
PID:3516
-
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
-
Filesize
52KB
MD5da2a7c383493e53e46c2c54b896021a9
SHA10c3e80c1703270146f715c4224c0b3045af0b3a8
SHA2569a35c7da03cafc1f4e762450c6ddc636b500539e7a812b8342d8043590b5f5ba
SHA51282de20dab6730b2dc14c968ab6eddaa1a10fb6c7373c12e773fbad723d76034f6fcab2e8d1d8d1b86c870444836034f5679540cb86e9d71bde199183af096b26