Analysis
-
max time kernel
150s -
max time network
151s -
platform
windows10-2004_x64 -
resource
win10v2004-20240508-en -
resource tags
arch:x64arch:x86image:win10v2004-20240508-enlocale:en-usos:windows10-2004-x64system -
submitted
22-05-2024 22:51
Static task
static1
Behavioral task
behavioral1
Sample
2024-05-22_8fda39ba31c541dbb41f1893f4181ca8_cryptolocker.exe
Resource
win7-20240508-en
Behavioral task
behavioral2
Sample
2024-05-22_8fda39ba31c541dbb41f1893f4181ca8_cryptolocker.exe
Resource
win10v2004-20240508-en
General
-
Target
2024-05-22_8fda39ba31c541dbb41f1893f4181ca8_cryptolocker.exe
-
Size
44KB
-
MD5
8fda39ba31c541dbb41f1893f4181ca8
-
SHA1
d66fa97bd8ff78ce030d03dde1eb47038f1651e1
-
SHA256
aa05942e31d1652c99794711862c7e7c8389b86236f9996b816102cc0a588e29
-
SHA512
0f2ea0f0797d4b8844be868ff538ac92b30ad42ff2bbb1241543e21d618cfcef3674b5d345f29f0bea17cd30da4141c1b468693f619f00a393dd8920c1b34d7f
-
SSDEEP
384:bm74uGLLQRcsdeQ72ngEr4K7YmE8jo0nrlwfjDUIDJ:bm74zYcgT/Ekn0ryfjvJ
Malware Config
Signatures
-
Detection of CryptoLocker Variants 5 IoCs
Processes:
resource yara_rule behavioral2/memory/4648-0-0x0000000008000000-0x000000000800D000-memory.dmp CryptoLocker_rule2 C:\Users\Admin\AppData\Local\Temp\hasfj.exe CryptoLocker_rule2 behavioral2/memory/4648-17-0x0000000008000000-0x000000000800D000-memory.dmp CryptoLocker_rule2 behavioral2/memory/2184-18-0x0000000008000000-0x000000000800D000-memory.dmp CryptoLocker_rule2 behavioral2/memory/2184-26-0x0000000008000000-0x000000000800D000-memory.dmp CryptoLocker_rule2 -
Checks computer location settings 2 TTPs 1 IoCs
Looks up country code configured in the registry, likely geofence.
Processes:
2024-05-22_8fda39ba31c541dbb41f1893f4181ca8_cryptolocker.exedescription ioc process Key value queried \REGISTRY\USER\S-1-5-21-2539840389-1261165778-1087677076-1000\Control Panel\International\Geo\Nation 2024-05-22_8fda39ba31c541dbb41f1893f4181ca8_cryptolocker.exe -
Executes dropped EXE 1 IoCs
Processes:
hasfj.exepid process 2184 hasfj.exe -
Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s).
-
Suspicious use of WriteProcessMemory 3 IoCs
Processes:
2024-05-22_8fda39ba31c541dbb41f1893f4181ca8_cryptolocker.exedescription pid process target process PID 4648 wrote to memory of 2184 4648 2024-05-22_8fda39ba31c541dbb41f1893f4181ca8_cryptolocker.exe hasfj.exe PID 4648 wrote to memory of 2184 4648 2024-05-22_8fda39ba31c541dbb41f1893f4181ca8_cryptolocker.exe hasfj.exe PID 4648 wrote to memory of 2184 4648 2024-05-22_8fda39ba31c541dbb41f1893f4181ca8_cryptolocker.exe hasfj.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\2024-05-22_8fda39ba31c541dbb41f1893f4181ca8_cryptolocker.exe"C:\Users\Admin\AppData\Local\Temp\2024-05-22_8fda39ba31c541dbb41f1893f4181ca8_cryptolocker.exe"1⤵
- Checks computer location settings
- Suspicious use of WriteProcessMemory
PID:4648 -
C:\Users\Admin\AppData\Local\Temp\hasfj.exe"C:\Users\Admin\AppData\Local\Temp\hasfj.exe"2⤵
- Executes dropped EXE
PID:2184
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
-
Filesize
45KB
MD55826965a6698f12ceacd905e776b709e
SHA1dbd86b91c02e8a94552f3899d78ee8b056e241cb
SHA256f44bde9e92b6659931edb616435e44ef4269853d7701312ea4f5d77d6a793dea
SHA5129bfaac4a2356a15fe1d0dbd89de85d55502494f955bc97b032e4cfb611102e535d0963ae211ef3e605f5b63f84b3a8fb8c2bbee73572f301bbce38b3153f0faa