Analysis
-
max time kernel
149s -
max time network
153s -
platform
windows7_x64 -
resource
win7-20240221-en -
resource tags
arch:x64arch:x86image:win7-20240221-enlocale:en-usos:windows7-x64system -
submitted
11/03/2024, 01:36
Behavioral task
behavioral1
Sample
2024-03-11_d5d6ccc5244b709c8bc189873248101d_cryptolocker.exe
Resource
win7-20240221-en
Behavioral task
behavioral2
Sample
2024-03-11_d5d6ccc5244b709c8bc189873248101d_cryptolocker.exe
Resource
win10v2004-20240226-en
General
-
Target
2024-03-11_d5d6ccc5244b709c8bc189873248101d_cryptolocker.exe
-
Size
63KB
-
MD5
d5d6ccc5244b709c8bc189873248101d
-
SHA1
613b0827d3d8c0c6a6e8ae447b406a013b2b4ce0
-
SHA256
a9e9deb6d949e0697b3e65e3321e38209a5c6c02b488109cb337fc3a3ee1dde3
-
SHA512
3201a25212749add75e4f7dd9cbf89e09e4baefcfa5ac1583adbf833b0bf1f8f0259a527e046a94922d3e775aab1637105371be5bbf1c4c6a956d77cd6b77647
-
SSDEEP
768:zQz7yVEhs9+syJP6ntOOtEvwDpjFelaB7yBEY9Su8F5mnVzCBRb:zj+soPSMOtEvwDpj4kpmeLmnZ+
Malware Config
Signatures
-
Detection of CryptoLocker Variants 6 IoCs
resource yara_rule behavioral1/memory/2240-0-0x0000000000500000-0x0000000000510000-memory.dmp CryptoLocker_rule2 behavioral1/files/0x000c000000012262-11.dat CryptoLocker_rule2 behavioral1/memory/2240-15-0x0000000000500000-0x0000000000510000-memory.dmp CryptoLocker_rule2 behavioral1/memory/2240-14-0x00000000026B0000-0x00000000026C0000-memory.dmp CryptoLocker_rule2 behavioral1/memory/2872-17-0x0000000000500000-0x0000000000510000-memory.dmp CryptoLocker_rule2 behavioral1/memory/2872-27-0x0000000000500000-0x0000000000510000-memory.dmp CryptoLocker_rule2 -
Detection of Cryptolocker Samples 5 IoCs
resource yara_rule behavioral1/memory/2240-0-0x0000000000500000-0x0000000000510000-memory.dmp CryptoLocker_set1 behavioral1/files/0x000c000000012262-11.dat CryptoLocker_set1 behavioral1/memory/2240-15-0x0000000000500000-0x0000000000510000-memory.dmp CryptoLocker_set1 behavioral1/memory/2872-17-0x0000000000500000-0x0000000000510000-memory.dmp CryptoLocker_set1 behavioral1/memory/2872-27-0x0000000000500000-0x0000000000510000-memory.dmp CryptoLocker_set1 -
UPX dump on OEP (original entry point) 5 IoCs
resource yara_rule behavioral1/memory/2240-0-0x0000000000500000-0x0000000000510000-memory.dmp UPX behavioral1/files/0x000c000000012262-11.dat UPX behavioral1/memory/2240-15-0x0000000000500000-0x0000000000510000-memory.dmp UPX behavioral1/memory/2872-17-0x0000000000500000-0x0000000000510000-memory.dmp UPX behavioral1/memory/2872-27-0x0000000000500000-0x0000000000510000-memory.dmp UPX -
Executes dropped EXE 1 IoCs
pid Process 2872 misid.exe -
Loads dropped DLL 1 IoCs
pid Process 2240 2024-03-11_d5d6ccc5244b709c8bc189873248101d_cryptolocker.exe -
resource yara_rule behavioral1/memory/2240-0-0x0000000000500000-0x0000000000510000-memory.dmp upx behavioral1/files/0x000c000000012262-11.dat upx behavioral1/memory/2240-15-0x0000000000500000-0x0000000000510000-memory.dmp upx behavioral1/memory/2872-17-0x0000000000500000-0x0000000000510000-memory.dmp upx behavioral1/memory/2872-27-0x0000000000500000-0x0000000000510000-memory.dmp upx -
Suspicious use of WriteProcessMemory 4 IoCs
description pid Process procid_target PID 2240 wrote to memory of 2872 2240 2024-03-11_d5d6ccc5244b709c8bc189873248101d_cryptolocker.exe 28 PID 2240 wrote to memory of 2872 2240 2024-03-11_d5d6ccc5244b709c8bc189873248101d_cryptolocker.exe 28 PID 2240 wrote to memory of 2872 2240 2024-03-11_d5d6ccc5244b709c8bc189873248101d_cryptolocker.exe 28 PID 2240 wrote to memory of 2872 2240 2024-03-11_d5d6ccc5244b709c8bc189873248101d_cryptolocker.exe 28
Processes
-
C:\Users\Admin\AppData\Local\Temp\2024-03-11_d5d6ccc5244b709c8bc189873248101d_cryptolocker.exe"C:\Users\Admin\AppData\Local\Temp\2024-03-11_d5d6ccc5244b709c8bc189873248101d_cryptolocker.exe"1⤵
- Loads dropped DLL
- Suspicious use of WriteProcessMemory
PID:2240 -
C:\Users\Admin\AppData\Local\Temp\misid.exe"C:\Users\Admin\AppData\Local\Temp\misid.exe"2⤵
- Executes dropped EXE
PID:2872
-
Network
MITRE ATT&CK Matrix
Replay Monitor
Loading Replay Monitor...
Downloads
-
Filesize
63KB
MD5a9e5f2bd0c8c43311fb545ddd3dca977
SHA1c3ed8eae761c5984bcf3b14625dd01d9d885582f
SHA2563f63817fd37e929214a92f4ace1188dda52e82b2aef526e6d32302204d93ba69
SHA512d64860c8577f1c3643e498e4e4bf7edf50bd7ccc96d0ce64fa1dc27b0c588423645a9e7b33bef9617b54cf88d635b8897fe9b9a963e7e5bbd8c73b44349af3de