Analysis
-
max time kernel
150s -
max time network
147s -
platform
windows10-2004_x64 -
resource
win10v2004-20240426-en -
resource tags
arch:x64arch:x86image:win10v2004-20240426-enlocale:en-usos:windows10-2004-x64system -
submitted
27-05-2024 02:44
Behavioral task
behavioral1
Sample
2024-05-27_cf5042c19e5252ff98a1901705db7b5d_cryptolocker.exe
Resource
win7-20231129-en
Behavioral task
behavioral2
Sample
2024-05-27_cf5042c19e5252ff98a1901705db7b5d_cryptolocker.exe
Resource
win10v2004-20240426-en
General
-
Target
2024-05-27_cf5042c19e5252ff98a1901705db7b5d_cryptolocker.exe
-
Size
42KB
-
MD5
cf5042c19e5252ff98a1901705db7b5d
-
SHA1
7c5883dd18670b8295388411b5e22dd76fe160e1
-
SHA256
023fe380fbc3bdf1031ebd2a33fd8e60d36431c45bbbaa9ce1dbf9f3fcbd694f
-
SHA512
a312aaddfab9ab6844f4d14d034313a8530491b2ee29574a4c52561760a1dd974ce234b3671956dc909be7dff773238db89098731685e6ec890a5781577ad086
-
SSDEEP
384:ba74uGLLQRcsdeQ72ngEr4K7YmE8j6CQYnrz1ZhdaXFXSCVQTLfjDpXqxKHTEXE:ba74zYcgT/EkdCQgpwXFXSqQXfj0xKoU
Malware Config
Signatures
-
Detection of CryptoLocker Variants 5 IoCs
resource yara_rule behavioral2/memory/2508-0-0x0000000008000000-0x000000000800F000-memory.dmp CryptoLocker_rule2 behavioral2/files/0x000b00000002341e-13.dat CryptoLocker_rule2 behavioral2/memory/5108-18-0x0000000008000000-0x000000000800F000-memory.dmp CryptoLocker_rule2 behavioral2/memory/2508-17-0x0000000008000000-0x000000000800F000-memory.dmp CryptoLocker_rule2 behavioral2/memory/5108-27-0x0000000008000000-0x000000000800F000-memory.dmp CryptoLocker_rule2 -
UPX dump on OEP (original entry point) 5 IoCs
resource yara_rule behavioral2/memory/2508-0-0x0000000008000000-0x000000000800F000-memory.dmp UPX behavioral2/files/0x000b00000002341e-13.dat UPX behavioral2/memory/5108-18-0x0000000008000000-0x000000000800F000-memory.dmp UPX behavioral2/memory/2508-17-0x0000000008000000-0x000000000800F000-memory.dmp UPX behavioral2/memory/5108-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-4018855536-2201274732-320770143-1000\Control Panel\International\Geo\Nation 2024-05-27_cf5042c19e5252ff98a1901705db7b5d_cryptolocker.exe -
Executes dropped EXE 1 IoCs
pid Process 5108 hasfj.exe -
resource yara_rule behavioral2/memory/2508-0-0x0000000008000000-0x000000000800F000-memory.dmp upx behavioral2/files/0x000b00000002341e-13.dat upx behavioral2/memory/5108-18-0x0000000008000000-0x000000000800F000-memory.dmp upx behavioral2/memory/2508-17-0x0000000008000000-0x000000000800F000-memory.dmp upx behavioral2/memory/5108-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 2508 wrote to memory of 5108 2508 2024-05-27_cf5042c19e5252ff98a1901705db7b5d_cryptolocker.exe 82 PID 2508 wrote to memory of 5108 2508 2024-05-27_cf5042c19e5252ff98a1901705db7b5d_cryptolocker.exe 82 PID 2508 wrote to memory of 5108 2508 2024-05-27_cf5042c19e5252ff98a1901705db7b5d_cryptolocker.exe 82
Processes
-
C:\Users\Admin\AppData\Local\Temp\2024-05-27_cf5042c19e5252ff98a1901705db7b5d_cryptolocker.exe"C:\Users\Admin\AppData\Local\Temp\2024-05-27_cf5042c19e5252ff98a1901705db7b5d_cryptolocker.exe"1⤵
- Checks computer location settings
- Suspicious use of WriteProcessMemory
PID:2508 -
C:\Users\Admin\AppData\Local\Temp\hasfj.exe"C:\Users\Admin\AppData\Local\Temp\hasfj.exe"2⤵
- Executes dropped EXE
PID:5108
-
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
-
Filesize
42KB
MD5e407ed5a43b61e0009ceef3f72b2ac9f
SHA1be6f8555994fc02e3612fe920e0d0ade52f17bef
SHA256c52eee54a141348c5837920900ddc43e8b7722569dbe05d031fc53b1fc2154b4
SHA512c8aed99ae1c46504c7a39856feff2351198c12e1a6090962622681b1bc723295bf745202f81699883915a380c7d4766500d93c0356ba4950bdbf4ad06124b65e