Analysis
-
max time kernel
149s -
max time network
152s -
platform
windows7_x64 -
resource
win7-20231215-en -
resource tags
arch:x64arch:x86image:win7-20231215-enlocale:en-usos:windows7-x64system -
submitted
17/02/2024, 08:00
Behavioral task
behavioral1
Sample
2024-02-17_f7eba65c66fbf0bc75ce966fbcfbfb96_cryptolocker.exe
Resource
win7-20231215-en
Behavioral task
behavioral2
Sample
2024-02-17_f7eba65c66fbf0bc75ce966fbcfbfb96_cryptolocker.exe
Resource
win10v2004-20231222-en
General
-
Target
2024-02-17_f7eba65c66fbf0bc75ce966fbcfbfb96_cryptolocker.exe
-
Size
56KB
-
MD5
f7eba65c66fbf0bc75ce966fbcfbfb96
-
SHA1
adacc0c94dbbeaca0f2b43f734fcbafc90e5264b
-
SHA256
0cf90b6681e4acf2aeaf9c64786bd6c9b5b7c55fc9e8986a3c6cea3777e0f768
-
SHA512
cf13dcc9bbbb66ab2a6352774e17c42a0b833512243dc56659325968a49ce1da9e7a4a7420e174b60f5553800e8d041cdfbebe8591b0843ecc2cdaf36a035185
-
SSDEEP
768:zQz7yVEhs9+syJP6ntOOtEvwDpjFeV0ZOfcpyR:zj+soPSMOtEvwDpj4yM
Malware Config
Signatures
-
Detection of CryptoLocker Variants 5 IoCs
resource yara_rule behavioral1/memory/2228-0-0x0000000000500000-0x0000000000510000-memory.dmp CryptoLocker_rule2 behavioral1/files/0x0008000000012262-11.dat CryptoLocker_rule2 behavioral1/memory/2228-16-0x0000000000500000-0x0000000000510000-memory.dmp CryptoLocker_rule2 behavioral1/memory/2720-17-0x0000000000500000-0x0000000000510000-memory.dmp CryptoLocker_rule2 behavioral1/memory/2720-27-0x0000000000500000-0x0000000000510000-memory.dmp CryptoLocker_rule2 -
Detection of Cryptolocker Samples 5 IoCs
resource yara_rule behavioral1/memory/2228-0-0x0000000000500000-0x0000000000510000-memory.dmp CryptoLocker_set1 behavioral1/files/0x0008000000012262-11.dat CryptoLocker_set1 behavioral1/memory/2228-16-0x0000000000500000-0x0000000000510000-memory.dmp CryptoLocker_set1 behavioral1/memory/2720-17-0x0000000000500000-0x0000000000510000-memory.dmp CryptoLocker_set1 behavioral1/memory/2720-27-0x0000000000500000-0x0000000000510000-memory.dmp CryptoLocker_set1 -
UPX dump on OEP (original entry point) 5 IoCs
resource yara_rule behavioral1/memory/2228-0-0x0000000000500000-0x0000000000510000-memory.dmp UPX behavioral1/files/0x0008000000012262-11.dat UPX behavioral1/memory/2228-16-0x0000000000500000-0x0000000000510000-memory.dmp UPX behavioral1/memory/2720-17-0x0000000000500000-0x0000000000510000-memory.dmp UPX behavioral1/memory/2720-27-0x0000000000500000-0x0000000000510000-memory.dmp UPX -
Executes dropped EXE 1 IoCs
pid Process 2720 misid.exe -
Loads dropped DLL 1 IoCs
pid Process 2228 2024-02-17_f7eba65c66fbf0bc75ce966fbcfbfb96_cryptolocker.exe -
resource yara_rule behavioral1/memory/2228-0-0x0000000000500000-0x0000000000510000-memory.dmp upx behavioral1/files/0x0008000000012262-11.dat upx behavioral1/memory/2228-16-0x0000000000500000-0x0000000000510000-memory.dmp upx behavioral1/memory/2720-17-0x0000000000500000-0x0000000000510000-memory.dmp upx behavioral1/memory/2720-27-0x0000000000500000-0x0000000000510000-memory.dmp upx -
Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s).
-
Suspicious use of WriteProcessMemory 4 IoCs
description pid Process procid_target PID 2228 wrote to memory of 2720 2228 2024-02-17_f7eba65c66fbf0bc75ce966fbcfbfb96_cryptolocker.exe 28 PID 2228 wrote to memory of 2720 2228 2024-02-17_f7eba65c66fbf0bc75ce966fbcfbfb96_cryptolocker.exe 28 PID 2228 wrote to memory of 2720 2228 2024-02-17_f7eba65c66fbf0bc75ce966fbcfbfb96_cryptolocker.exe 28 PID 2228 wrote to memory of 2720 2228 2024-02-17_f7eba65c66fbf0bc75ce966fbcfbfb96_cryptolocker.exe 28
Processes
-
C:\Users\Admin\AppData\Local\Temp\2024-02-17_f7eba65c66fbf0bc75ce966fbcfbfb96_cryptolocker.exe"C:\Users\Admin\AppData\Local\Temp\2024-02-17_f7eba65c66fbf0bc75ce966fbcfbfb96_cryptolocker.exe"1⤵
- Loads dropped DLL
- Suspicious use of WriteProcessMemory
PID:2228 -
C:\Users\Admin\AppData\Local\Temp\misid.exe"C:\Users\Admin\AppData\Local\Temp\misid.exe"2⤵
- Executes dropped EXE
PID:2720
-
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
-
Filesize
56KB
MD5de27db50e749d3903d0f9413e3e2a706
SHA1a4e0eadded15c8a33f558353e5075bfd3a5bb8f3
SHA2567babbf3970b48267aedf66ed4743b785185b5911eab4ac24f5426822ebb749ef
SHA5123e46591c7909c35681ca7fc1073da927c0b214ea472b33bebd6a0e17fea5c9cf37196eda4d8059b31801c0d4c24853ea1e1b27a8affe091f2ec7a79a7ed12d1e