Analysis
-
max time kernel
149s -
max time network
156s -
platform
windows7_x64 -
resource
win7-20240221-en -
resource tags
arch:x64arch:x86image:win7-20240221-enlocale:en-usos:windows7-x64system -
submitted
31/05/2024, 23:31
Behavioral task
behavioral1
Sample
2024-05-31_659b0a0c4bb346cfc5766ac544f8039d_cryptolocker.exe
Resource
win7-20240221-en
Behavioral task
behavioral2
Sample
2024-05-31_659b0a0c4bb346cfc5766ac544f8039d_cryptolocker.exe
Resource
win10v2004-20240426-en
General
-
Target
2024-05-31_659b0a0c4bb346cfc5766ac544f8039d_cryptolocker.exe
-
Size
40KB
-
MD5
659b0a0c4bb346cfc5766ac544f8039d
-
SHA1
9552471439a7316a42ba910fc7b66b64737b34df
-
SHA256
fe6cb76f7e34d5b02396a5bfc7d624e7af0323be4f56edb19616f9c5864e7ac5
-
SHA512
d30094e26bbf97cc2ebb7c11a005b2d24567af5a9ffbbb5b137b4d6e3eab1af5f58af7da45935f3d237951f49d8221c388584f051d7538be50d621b245d0ea0d
-
SSDEEP
768:q7PdFecFS5agQtOOtEvwDpjeMLZdzuqpXsiE8Wq/DpkITYfFt9m:qDdFJy3QMOtEvwDpjjWMl7Tqm
Malware Config
Signatures
-
Detection of CryptoLocker Variants 5 IoCs
resource yara_rule behavioral1/memory/856-0-0x0000000000500000-0x0000000000510000-memory.dmp CryptoLocker_rule2 behavioral1/files/0x00090000000143d1-11.dat CryptoLocker_rule2 behavioral1/memory/856-16-0x0000000000500000-0x0000000000510000-memory.dmp CryptoLocker_rule2 behavioral1/memory/2700-17-0x0000000000500000-0x0000000000510000-memory.dmp CryptoLocker_rule2 behavioral1/memory/2700-27-0x0000000000500000-0x0000000000510000-memory.dmp CryptoLocker_rule2 -
Detection of Cryptolocker Samples 5 IoCs
resource yara_rule behavioral1/memory/856-0-0x0000000000500000-0x0000000000510000-memory.dmp CryptoLocker_set1 behavioral1/files/0x00090000000143d1-11.dat CryptoLocker_set1 behavioral1/memory/856-16-0x0000000000500000-0x0000000000510000-memory.dmp CryptoLocker_set1 behavioral1/memory/2700-17-0x0000000000500000-0x0000000000510000-memory.dmp CryptoLocker_set1 behavioral1/memory/2700-27-0x0000000000500000-0x0000000000510000-memory.dmp CryptoLocker_set1 -
UPX dump on OEP (original entry point) 5 IoCs
resource yara_rule behavioral1/memory/856-0-0x0000000000500000-0x0000000000510000-memory.dmp UPX behavioral1/files/0x00090000000143d1-11.dat UPX behavioral1/memory/856-16-0x0000000000500000-0x0000000000510000-memory.dmp UPX behavioral1/memory/2700-17-0x0000000000500000-0x0000000000510000-memory.dmp UPX behavioral1/memory/2700-27-0x0000000000500000-0x0000000000510000-memory.dmp UPX -
Executes dropped EXE 1 IoCs
pid Process 2700 asih.exe -
Loads dropped DLL 1 IoCs
pid Process 856 2024-05-31_659b0a0c4bb346cfc5766ac544f8039d_cryptolocker.exe -
resource yara_rule behavioral1/memory/856-0-0x0000000000500000-0x0000000000510000-memory.dmp upx behavioral1/files/0x00090000000143d1-11.dat upx behavioral1/memory/856-16-0x0000000000500000-0x0000000000510000-memory.dmp upx behavioral1/memory/2700-17-0x0000000000500000-0x0000000000510000-memory.dmp upx behavioral1/memory/2700-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 856 wrote to memory of 2700 856 2024-05-31_659b0a0c4bb346cfc5766ac544f8039d_cryptolocker.exe 28 PID 856 wrote to memory of 2700 856 2024-05-31_659b0a0c4bb346cfc5766ac544f8039d_cryptolocker.exe 28 PID 856 wrote to memory of 2700 856 2024-05-31_659b0a0c4bb346cfc5766ac544f8039d_cryptolocker.exe 28 PID 856 wrote to memory of 2700 856 2024-05-31_659b0a0c4bb346cfc5766ac544f8039d_cryptolocker.exe 28
Processes
-
C:\Users\Admin\AppData\Local\Temp\2024-05-31_659b0a0c4bb346cfc5766ac544f8039d_cryptolocker.exe"C:\Users\Admin\AppData\Local\Temp\2024-05-31_659b0a0c4bb346cfc5766ac544f8039d_cryptolocker.exe"1⤵
- Loads dropped DLL
- Suspicious use of WriteProcessMemory
PID:856 -
C:\Users\Admin\AppData\Local\Temp\asih.exe"C:\Users\Admin\AppData\Local\Temp\asih.exe"2⤵
- Executes dropped EXE
PID:2700
-
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
-
Filesize
40KB
MD5231249ee75fe02d6a5b1bc28e34a09c7
SHA1413f15d0c2deee582a1f8d7dd63cc56f8d2fb73c
SHA256833713c4ae7187d29886ef13cb6edc2c463434226ec045667b4ae2ea96c86914
SHA5124e3bbdc98df1866a5cdcab91c30c7ecf8ea50946b01134820b0ea798befeb5362f99154e03ad44dc10a486785f634a26bf2277ed0e9156999696e065e8a951e6