Analysis
-
max time kernel
149s -
max time network
153s -
platform
windows7_x64 -
resource
win7-20231215-en -
resource tags
arch:x64arch:x86image:win7-20231215-enlocale:en-usos:windows7-x64system -
submitted
03/02/2024, 19:33
Behavioral task
behavioral1
Sample
2024-02-03_bf9fdbca7e93c0429e2706f2b202135f_cryptolocker.exe
Resource
win7-20231215-en
Behavioral task
behavioral2
Sample
2024-02-03_bf9fdbca7e93c0429e2706f2b202135f_cryptolocker.exe
Resource
win10v2004-20231215-en
General
-
Target
2024-02-03_bf9fdbca7e93c0429e2706f2b202135f_cryptolocker.exe
-
Size
101KB
-
MD5
bf9fdbca7e93c0429e2706f2b202135f
-
SHA1
f5529f0c0ba4af77297afee5ba6c336ce591461e
-
SHA256
44b540b9cbbd6890aa27c6001200b191348687c1c674413b4586e9c90a8c742d
-
SHA512
7e72f00cb975d71b353308ad51e6c6c8dbddc1ed70967aaca4682a464295dfb07b4b28a75739101e6cdc443f6de826f3e9f8345c0e33ff24e3c99d6db52ad07c
-
SSDEEP
1536:qkmnpomddpMOtEvwDpjJGYQbN/PKwNgpwqWsviy6ixa:AnBdOOtEvwDpj6zV
Malware Config
Signatures
-
Detection of CryptoLocker Variants 5 IoCs
resource yara_rule behavioral1/memory/2204-0-0x0000000000500000-0x000000000050F000-memory.dmp CryptoLocker_rule2 behavioral1/files/0x000a000000012238-11.dat CryptoLocker_rule2 behavioral1/memory/1888-16-0x0000000000500000-0x000000000050F000-memory.dmp CryptoLocker_rule2 behavioral1/memory/2204-15-0x0000000000500000-0x000000000050F000-memory.dmp CryptoLocker_rule2 behavioral1/memory/1888-26-0x0000000000500000-0x000000000050F000-memory.dmp CryptoLocker_rule2 -
Detection of Cryptolocker Samples 5 IoCs
resource yara_rule behavioral1/memory/2204-0-0x0000000000500000-0x000000000050F000-memory.dmp CryptoLocker_set1 behavioral1/files/0x000a000000012238-11.dat CryptoLocker_set1 behavioral1/memory/1888-16-0x0000000000500000-0x000000000050F000-memory.dmp CryptoLocker_set1 behavioral1/memory/2204-15-0x0000000000500000-0x000000000050F000-memory.dmp CryptoLocker_set1 behavioral1/memory/1888-26-0x0000000000500000-0x000000000050F000-memory.dmp CryptoLocker_set1 -
UPX dump on OEP (original entry point) 5 IoCs
resource yara_rule behavioral1/memory/2204-0-0x0000000000500000-0x000000000050F000-memory.dmp UPX behavioral1/files/0x000a000000012238-11.dat UPX behavioral1/memory/1888-16-0x0000000000500000-0x000000000050F000-memory.dmp UPX behavioral1/memory/2204-15-0x0000000000500000-0x000000000050F000-memory.dmp UPX behavioral1/memory/1888-26-0x0000000000500000-0x000000000050F000-memory.dmp UPX -
Executes dropped EXE 1 IoCs
pid Process 1888 asih.exe -
Loads dropped DLL 1 IoCs
pid Process 2204 2024-02-03_bf9fdbca7e93c0429e2706f2b202135f_cryptolocker.exe -
resource yara_rule behavioral1/memory/2204-0-0x0000000000500000-0x000000000050F000-memory.dmp upx behavioral1/files/0x000a000000012238-11.dat upx behavioral1/memory/1888-16-0x0000000000500000-0x000000000050F000-memory.dmp upx behavioral1/memory/2204-15-0x0000000000500000-0x000000000050F000-memory.dmp upx behavioral1/memory/1888-26-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 2204 wrote to memory of 1888 2204 2024-02-03_bf9fdbca7e93c0429e2706f2b202135f_cryptolocker.exe 28 PID 2204 wrote to memory of 1888 2204 2024-02-03_bf9fdbca7e93c0429e2706f2b202135f_cryptolocker.exe 28 PID 2204 wrote to memory of 1888 2204 2024-02-03_bf9fdbca7e93c0429e2706f2b202135f_cryptolocker.exe 28 PID 2204 wrote to memory of 1888 2204 2024-02-03_bf9fdbca7e93c0429e2706f2b202135f_cryptolocker.exe 28
Processes
-
C:\Users\Admin\AppData\Local\Temp\2024-02-03_bf9fdbca7e93c0429e2706f2b202135f_cryptolocker.exe"C:\Users\Admin\AppData\Local\Temp\2024-02-03_bf9fdbca7e93c0429e2706f2b202135f_cryptolocker.exe"1⤵
- Loads dropped DLL
- Suspicious use of WriteProcessMemory
PID:2204 -
C:\Users\Admin\AppData\Local\Temp\asih.exe"C:\Users\Admin\AppData\Local\Temp\asih.exe"2⤵
- Executes dropped EXE
PID:1888
-
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
-
Filesize
101KB
MD5384f4e0ab9b4b013a3d2cf0a74bc1ab9
SHA154a60180f864e751ff80865873066e9461029cea
SHA256d3e1dbff0820ce99e4c005877ee1c5c9d501a95ac9bf112e19da806ff59f5a18
SHA51295ead6f59a23d78a5064ecff24fd74b033553cd6fa0e74863f757cc21a513639830aa33283c731f9e5c547abdd7dec7e6e54037db0902239e2effc1f80fffc32