Analysis
-
max time kernel
150s -
max time network
150s -
platform
windows10-2004_x64 -
resource
win10v2004-20240508-en -
resource tags
arch:x64arch:x86image:win10v2004-20240508-enlocale:en-usos:windows10-2004-x64system -
submitted
11-06-2024 06:26
Behavioral task
behavioral1
Sample
2024-06-11_50fee36ccbc9a9ef4614035256602050_cryptolocker.exe
Resource
win7-20240221-en
Behavioral task
behavioral2
Sample
2024-06-11_50fee36ccbc9a9ef4614035256602050_cryptolocker.exe
Resource
win10v2004-20240508-en
General
-
Target
2024-06-11_50fee36ccbc9a9ef4614035256602050_cryptolocker.exe
-
Size
52KB
-
MD5
50fee36ccbc9a9ef4614035256602050
-
SHA1
ce64ff85c1e350ee28fef53a0ec80c197bc8e9f8
-
SHA256
f9d777135947b48bc5b5e4a91a08d351a35c3f746234c5c55e64b02e0fefaa23
-
SHA512
f46c2ceaa79d279f0f8370f7a2065ebb135785a0ad75901e37e33588d3a7a07cf854bc6042358552f23e10b99bc93a96b1d2a92167fe26854b8ec3b2f1962a7d
-
SSDEEP
768:bODOw9UiamWUB2preAr+OfjH/0S16avdrQFiLjJvtO7:bODOw9acifAoc+v4
Malware Config
Signatures
-
Detection of CryptoLocker Variants 5 IoCs
resource yara_rule behavioral2/memory/636-0-0x0000000008000000-0x000000000800F000-memory.dmp CryptoLocker_rule2 behavioral2/files/0x00090000000233fd-13.dat CryptoLocker_rule2 behavioral2/memory/636-18-0x0000000008000000-0x000000000800F000-memory.dmp CryptoLocker_rule2 behavioral2/memory/5020-17-0x0000000008000000-0x000000000800F000-memory.dmp CryptoLocker_rule2 behavioral2/memory/5020-27-0x0000000008000000-0x000000000800F000-memory.dmp CryptoLocker_rule2 -
UPX dump on OEP (original entry point) 5 IoCs
resource yara_rule behavioral2/memory/636-0-0x0000000008000000-0x000000000800F000-memory.dmp UPX behavioral2/files/0x00090000000233fd-13.dat UPX behavioral2/memory/636-18-0x0000000008000000-0x000000000800F000-memory.dmp UPX behavioral2/memory/5020-17-0x0000000008000000-0x000000000800F000-memory.dmp UPX behavioral2/memory/5020-27-0x0000000008000000-0x000000000800F000-memory.dmp 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-4124900551-4068476067-3491212533-1000\Control Panel\International\Geo\Nation 2024-06-11_50fee36ccbc9a9ef4614035256602050_cryptolocker.exe -
Executes dropped EXE 1 IoCs
pid Process 5020 lossy.exe -
resource yara_rule behavioral2/memory/636-0-0x0000000008000000-0x000000000800F000-memory.dmp upx behavioral2/files/0x00090000000233fd-13.dat upx behavioral2/memory/636-18-0x0000000008000000-0x000000000800F000-memory.dmp upx behavioral2/memory/5020-17-0x0000000008000000-0x000000000800F000-memory.dmp upx behavioral2/memory/5020-27-0x0000000008000000-0x000000000800F000-memory.dmp 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 636 wrote to memory of 5020 636 2024-06-11_50fee36ccbc9a9ef4614035256602050_cryptolocker.exe 81 PID 636 wrote to memory of 5020 636 2024-06-11_50fee36ccbc9a9ef4614035256602050_cryptolocker.exe 81 PID 636 wrote to memory of 5020 636 2024-06-11_50fee36ccbc9a9ef4614035256602050_cryptolocker.exe 81
Processes
-
C:\Users\Admin\AppData\Local\Temp\2024-06-11_50fee36ccbc9a9ef4614035256602050_cryptolocker.exe"C:\Users\Admin\AppData\Local\Temp\2024-06-11_50fee36ccbc9a9ef4614035256602050_cryptolocker.exe"1⤵
- Checks computer location settings
- Suspicious use of WriteProcessMemory
PID:636 -
C:\Users\Admin\AppData\Local\Temp\lossy.exe"C:\Users\Admin\AppData\Local\Temp\lossy.exe"2⤵
- Executes dropped EXE
PID:5020
-
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
-
Filesize
52KB
MD564a6aa33328616162f8ebc1d26571b99
SHA101d039a86705e62f55a7777a37c6ac62167da927
SHA256a1cb4023348373ea56b404511027ca524e3d92317f8b748ae545ae32ee26cfbd
SHA5124ac4408a7672164067c498035421aabeb8308979cc10d5fb7df5d644efbf65b87b0047bfed0ff932fbf62417600848b18595f00209a343d71bdd64d079494829