Analysis
-
max time kernel
150s -
max time network
152s -
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, 14:31
Behavioral task
behavioral1
Sample
2024-05-22_1d7578e4eacf4817d86ffad967345fd9_cryptolocker.exe
Resource
win7-20240221-en
Behavioral task
behavioral2
Sample
2024-05-22_1d7578e4eacf4817d86ffad967345fd9_cryptolocker.exe
Resource
win10v2004-20240508-en
General
-
Target
2024-05-22_1d7578e4eacf4817d86ffad967345fd9_cryptolocker.exe
-
Size
51KB
-
MD5
1d7578e4eacf4817d86ffad967345fd9
-
SHA1
f2a434ad498753ff130d1f5f955c89ad4a557467
-
SHA256
3b576b0afac0ed30322bd31694b766a82860e604e1116dc27075ccbbb7d05413
-
SHA512
1c54fe82cfc173b8efa6f766bb8d51425b10795eaad20abae1a253f1c3b64d5c60f02adf20457f0bfe38045d35342440738f7c03cf262a57d1923d12c483880e
-
SSDEEP
768:bODOw9UiamWUB2preAr+OfjH/0S16avdrQFiLjJvtXs:bODOw9acifAoc+vXs
Malware Config
Signatures
-
Detection of CryptoLocker Variants 5 IoCs
resource yara_rule behavioral2/memory/4664-0-0x0000000008000000-0x000000000800F000-memory.dmp CryptoLocker_rule2 behavioral2/files/0x0008000000022f51-13.dat CryptoLocker_rule2 behavioral2/memory/1512-17-0x0000000008000000-0x000000000800F000-memory.dmp CryptoLocker_rule2 behavioral2/memory/4664-25-0x0000000008000000-0x000000000800F000-memory.dmp CryptoLocker_rule2 behavioral2/memory/1512-27-0x0000000008000000-0x000000000800F000-memory.dmp CryptoLocker_rule2 -
UPX dump on OEP (original entry point) 5 IoCs
resource yara_rule behavioral2/memory/4664-0-0x0000000008000000-0x000000000800F000-memory.dmp UPX behavioral2/files/0x0008000000022f51-13.dat UPX behavioral2/memory/1512-17-0x0000000008000000-0x000000000800F000-memory.dmp UPX behavioral2/memory/4664-25-0x0000000008000000-0x000000000800F000-memory.dmp UPX behavioral2/memory/1512-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-1337824034-2731376981-3755436523-1000\Control Panel\International\Geo\Nation 2024-05-22_1d7578e4eacf4817d86ffad967345fd9_cryptolocker.exe -
Executes dropped EXE 1 IoCs
pid Process 1512 lossy.exe -
resource yara_rule behavioral2/memory/4664-0-0x0000000008000000-0x000000000800F000-memory.dmp upx behavioral2/files/0x0008000000022f51-13.dat upx behavioral2/memory/1512-17-0x0000000008000000-0x000000000800F000-memory.dmp upx behavioral2/memory/4664-25-0x0000000008000000-0x000000000800F000-memory.dmp upx behavioral2/memory/1512-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 4664 wrote to memory of 1512 4664 2024-05-22_1d7578e4eacf4817d86ffad967345fd9_cryptolocker.exe 83 PID 4664 wrote to memory of 1512 4664 2024-05-22_1d7578e4eacf4817d86ffad967345fd9_cryptolocker.exe 83 PID 4664 wrote to memory of 1512 4664 2024-05-22_1d7578e4eacf4817d86ffad967345fd9_cryptolocker.exe 83
Processes
-
C:\Users\Admin\AppData\Local\Temp\2024-05-22_1d7578e4eacf4817d86ffad967345fd9_cryptolocker.exe"C:\Users\Admin\AppData\Local\Temp\2024-05-22_1d7578e4eacf4817d86ffad967345fd9_cryptolocker.exe"1⤵
- Checks computer location settings
- Suspicious use of WriteProcessMemory
PID:4664 -
C:\Users\Admin\AppData\Local\Temp\lossy.exe"C:\Users\Admin\AppData\Local\Temp\lossy.exe"2⤵
- Executes dropped EXE
PID:1512
-
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
-
Filesize
51KB
MD536e21ac963d70f18f7776c77b96db93f
SHA1f34cba3e454183371416c7dadd5dce874a2f3684
SHA256b485c8c7b3cf3921e86e4e7bfeab0270a0d051b1fa5c2705934b11fa8af73b51
SHA512c27d03b0d0bf72d2a311771e12ac2b11821a845443c7228561083c205f6f00e4054b61ced0b5625bce130b95c047f54238df658ca51dae1a13ed5b07fa4ebf66