Analysis
-
max time kernel
150s -
max time network
150s -
platform
windows10-2004_x64 -
resource
win10v2004-20240419-en -
resource tags
arch:x64arch:x86image:win10v2004-20240419-enlocale:en-usos:windows10-2004-x64system -
submitted
30/04/2024, 21:08
Behavioral task
behavioral1
Sample
2024-04-30_3c967c0086bc366cebc97f5fb9c2dec1_cryptolocker.exe
Resource
win7-20240220-en
Behavioral task
behavioral2
Sample
2024-04-30_3c967c0086bc366cebc97f5fb9c2dec1_cryptolocker.exe
Resource
win10v2004-20240419-en
General
-
Target
2024-04-30_3c967c0086bc366cebc97f5fb9c2dec1_cryptolocker.exe
-
Size
55KB
-
MD5
3c967c0086bc366cebc97f5fb9c2dec1
-
SHA1
8983df67f5eee2d5b91975526011cfd7c8a978a7
-
SHA256
0c808ba475b732bb6c9ccd8b9bd6a1bd6d7ce5932775eaccc3b81b6c50c69773
-
SHA512
a7fdebae1e666a066d1a0e3287bc17811c765de03c919360a007f52fb471b04546dcb5e4d5d358ce292bcc9c347bc7777715c99f8bcc5a52ddfd03411c0c250c
-
SSDEEP
768:bP9g/WItCSsAfFaeOcfXVr3BPOz5CFBmNuFgUjNw:bP9g/xtCS3Dxx0D
Malware Config
Signatures
-
Detection of CryptoLocker Variants 2 IoCs
resource yara_rule behavioral2/memory/3980-0-0x0000000000400000-0x000000000040E000-memory.dmp CryptoLocker_rule2 behavioral2/files/0x000b000000023b7f-13.dat CryptoLocker_rule2 -
UPX dump on OEP (original entry point) 2 IoCs
resource yara_rule behavioral2/memory/3980-0-0x0000000000400000-0x000000000040E000-memory.dmp UPX behavioral2/files/0x000b000000023b7f-13.dat UPX -
Checks computer location settings 2 TTPs 1 IoCs
Looks up country code configured in the registry, likely geofence.
description ioc Process Key value queried \REGISTRY\USER\S-1-5-21-3726321484-1950364574-433157660-1000\Control Panel\International\Geo\Nation 2024-04-30_3c967c0086bc366cebc97f5fb9c2dec1_cryptolocker.exe -
Executes dropped EXE 1 IoCs
pid Process 2360 gewos.exe -
resource yara_rule behavioral2/memory/3980-0-0x0000000000400000-0x000000000040E000-memory.dmp upx behavioral2/files/0x000b000000023b7f-13.dat upx -
Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s).
-
Suspicious use of WriteProcessMemory 3 IoCs
description pid Process procid_target PID 3980 wrote to memory of 2360 3980 2024-04-30_3c967c0086bc366cebc97f5fb9c2dec1_cryptolocker.exe 83 PID 3980 wrote to memory of 2360 3980 2024-04-30_3c967c0086bc366cebc97f5fb9c2dec1_cryptolocker.exe 83 PID 3980 wrote to memory of 2360 3980 2024-04-30_3c967c0086bc366cebc97f5fb9c2dec1_cryptolocker.exe 83
Processes
-
C:\Users\Admin\AppData\Local\Temp\2024-04-30_3c967c0086bc366cebc97f5fb9c2dec1_cryptolocker.exe"C:\Users\Admin\AppData\Local\Temp\2024-04-30_3c967c0086bc366cebc97f5fb9c2dec1_cryptolocker.exe"1⤵
- Checks computer location settings
- Suspicious use of WriteProcessMemory
PID:3980 -
C:\Users\Admin\AppData\Local\Temp\gewos.exe"C:\Users\Admin\AppData\Local\Temp\gewos.exe"2⤵
- Executes dropped EXE
PID:2360
-
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
-
Filesize
55KB
MD511f3d6992163f7600bcf8517f0322280
SHA150990c827f81c8aca391b222e0def1e747d0f522
SHA2569546483489c7452fe798193e5e5d9f4e8df000d69233ad6361dd3b634dad0557
SHA512c5e02e0ac0f8a22dd09090741a3d97d65e87aed8a4ab791c5f7575ac1af81080c7e9306af5682c4d6fa7a82d8c3f061585507af7880f99ab5fdc69830741f0ec