Analysis
-
max time kernel
148s -
max time network
148s -
platform
windows7_x64 -
resource
win7-20240221-en -
resource tags
arch:x64arch:x86image:win7-20240221-enlocale:en-usos:windows7-x64system -
submitted
30/04/2024, 02:42
Behavioral task
behavioral1
Sample
2024-04-30_5dfffa0e6b477b33db6949f0378fb8cf_cryptolocker.exe
Resource
win7-20240221-en
Behavioral task
behavioral2
Sample
2024-04-30_5dfffa0e6b477b33db6949f0378fb8cf_cryptolocker.exe
Resource
win10v2004-20240419-en
General
-
Target
2024-04-30_5dfffa0e6b477b33db6949f0378fb8cf_cryptolocker.exe
-
Size
97KB
-
MD5
5dfffa0e6b477b33db6949f0378fb8cf
-
SHA1
9b7fc32a7555e375665f87be4ab31a9fac65705c
-
SHA256
fe803f968d7bf4fa05f7d119a2ab969dd26c27747829d6232bbcd835b0b9388c
-
SHA512
784eef14f114708c4c3d60773bfda6a17832e07a215fccb469be1b00361addd149dbdb3c51bd7fa114ad7723305e644d892634d09adc489010d18df2d063d588
-
SSDEEP
1536:qkmnpomddpMOtEvwDpjJGYQbN/PKwNgpYy95:AnBdOOtEvwDpj6zU
Malware Config
Signatures
-
Detection of CryptoLocker Variants 5 IoCs
resource yara_rule behavioral1/memory/1700-0-0x0000000000500000-0x000000000050F000-memory.dmp CryptoLocker_rule2 behavioral1/files/0x000c000000013187-11.dat CryptoLocker_rule2 behavioral1/memory/1700-16-0x0000000000500000-0x000000000050F000-memory.dmp CryptoLocker_rule2 behavioral1/memory/2192-17-0x0000000000500000-0x000000000050F000-memory.dmp CryptoLocker_rule2 behavioral1/memory/2192-27-0x0000000000500000-0x000000000050F000-memory.dmp CryptoLocker_rule2 -
Detection of Cryptolocker Samples 5 IoCs
resource yara_rule behavioral1/memory/1700-0-0x0000000000500000-0x000000000050F000-memory.dmp CryptoLocker_set1 behavioral1/files/0x000c000000013187-11.dat CryptoLocker_set1 behavioral1/memory/1700-16-0x0000000000500000-0x000000000050F000-memory.dmp CryptoLocker_set1 behavioral1/memory/2192-17-0x0000000000500000-0x000000000050F000-memory.dmp CryptoLocker_set1 behavioral1/memory/2192-27-0x0000000000500000-0x000000000050F000-memory.dmp CryptoLocker_set1 -
UPX dump on OEP (original entry point) 5 IoCs
resource yara_rule behavioral1/memory/1700-0-0x0000000000500000-0x000000000050F000-memory.dmp UPX behavioral1/files/0x000c000000013187-11.dat UPX behavioral1/memory/1700-16-0x0000000000500000-0x000000000050F000-memory.dmp UPX behavioral1/memory/2192-17-0x0000000000500000-0x000000000050F000-memory.dmp UPX behavioral1/memory/2192-27-0x0000000000500000-0x000000000050F000-memory.dmp UPX -
Executes dropped EXE 1 IoCs
pid Process 2192 asih.exe -
Loads dropped DLL 1 IoCs
pid Process 1700 2024-04-30_5dfffa0e6b477b33db6949f0378fb8cf_cryptolocker.exe -
resource yara_rule behavioral1/memory/1700-0-0x0000000000500000-0x000000000050F000-memory.dmp upx behavioral1/files/0x000c000000013187-11.dat upx behavioral1/memory/1700-16-0x0000000000500000-0x000000000050F000-memory.dmp upx behavioral1/memory/2192-17-0x0000000000500000-0x000000000050F000-memory.dmp upx behavioral1/memory/2192-27-0x0000000000500000-0x000000000050F000-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 1700 wrote to memory of 2192 1700 2024-04-30_5dfffa0e6b477b33db6949f0378fb8cf_cryptolocker.exe 28 PID 1700 wrote to memory of 2192 1700 2024-04-30_5dfffa0e6b477b33db6949f0378fb8cf_cryptolocker.exe 28 PID 1700 wrote to memory of 2192 1700 2024-04-30_5dfffa0e6b477b33db6949f0378fb8cf_cryptolocker.exe 28 PID 1700 wrote to memory of 2192 1700 2024-04-30_5dfffa0e6b477b33db6949f0378fb8cf_cryptolocker.exe 28
Processes
-
C:\Users\Admin\AppData\Local\Temp\2024-04-30_5dfffa0e6b477b33db6949f0378fb8cf_cryptolocker.exe"C:\Users\Admin\AppData\Local\Temp\2024-04-30_5dfffa0e6b477b33db6949f0378fb8cf_cryptolocker.exe"1⤵
- Loads dropped DLL
- Suspicious use of WriteProcessMemory
PID:1700 -
C:\Users\Admin\AppData\Local\Temp\asih.exe"C:\Users\Admin\AppData\Local\Temp\asih.exe"2⤵
- Executes dropped EXE
PID:2192
-
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
-
Filesize
97KB
MD5c0f358b4d4ff9e6343d9ca0b06003410
SHA16562e0c847e8f8d1b56fa7b765194d34efca625b
SHA256e659e079ba4cb0ade7f7e663ac898d9c06ff5b2ad27e74917f9a6309cdcaeac8
SHA512fdb37cad8c5e583e3766802a576ac940b1e10b18df34098807e7ccefd9e26185f92d2408844e9d69bd2299cbdc059de8b53833c5f4981583ae4d062920d583ce