Analysis
- max time kernel
150s - max time network
156s - platform
windows7_x64 - resource
win7-20240221-en - resource tags
arch:x64arch:x86image:win7-20240221-enlocale:en-usos:windows7-x64system - submitted
02/06/2024, 22:25
Static task
static1
2 signatures
Behavioral task
behavioral1
Sample
2024-06-02_6c4ac46916d32700e41fb9bc73e9418c_cryptolocker.exe
Resource
win7-20240221-en
5 signatures
150 seconds
Behavioral task
behavioral2
Sample
2024-06-02_6c4ac46916d32700e41fb9bc73e9418c_cryptolocker.exe
Resource
win10v2004-20240426-en
5 signatures
150 seconds
General
- Target 2024-06-02_6c4ac46916d32700e41fb9bc73e9418c_cryptolocker.exe
- Size 44KB
- Sample240602-2b5alaac79
- SHA256 9e55b49f7a5d313f08f4e1c395dba8a7aea35f73ba800b4a4c8f297532081708
- MD5 6c4ac46916d32700e41fb9bc73e9418c
- SHA1 132f0c12ddcd496bc639be6d570ba4027d6f6d4d
- SHA512 78eb644f8c2099f3e81dbd71b94ee4c60bcf58a8de7aea3bb39d9e64fe3d7be847c179f8d6695cd90a553d27e0ed778712073036ec14b95dcf9d1d2b53f3816c
- SSDEEP 768:bCDOw9UiaKHfjnD0S16avdrQFiLjJvtAH0v:bCDOw9aMDooc+vAUv
- MD5 SHA1 SHA512 SSDEEP
Score
9/10
Malware Config
Signatures
- Detection of CryptoLocker Variants 5 IoCs
resource yara_rule behavioral1/files/0x00090000000143d1-24.dat CryptoLocker_rule2 behavioral1/memory/2612-16-0x0000000008000000-0x000000000800A000-memory.dmp CryptoLocker_rule2 behavioral1/memory/1612-15-0x0000000008000000-0x000000000800A000-memory.dmp CryptoLocker_rule2 behavioral1/memory/1612-0-0x0000000008000000-0x000000000800A000-memory.dmp CryptoLocker_rule2 behavioral1/memory/2612-26-0x0000000008000000-0x000000000800A000-memory.dmp CryptoLocker_rule2 - Executes dropped EXE 1 IoCs
pid Process 2612 lossy.exe - Loads dropped DLL 1 IoCs
pid Process 1612 2024-06-02_6c4ac46916d32700e41fb9bc73e9418c_cryptolocker.exe - 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 1612 wrote to memory of 2612 1612 2024-06-02_6c4ac46916d32700e41fb9bc73e9418c_cryptolocker.exe 28 PID 1612 wrote to memory of 2612 1612 2024-06-02_6c4ac46916d32700e41fb9bc73e9418c_cryptolocker.exe 28 PID 1612 wrote to memory of 2612 1612 2024-06-02_6c4ac46916d32700e41fb9bc73e9418c_cryptolocker.exe 28 PID 1612 wrote to memory of 2612 1612 2024-06-02_6c4ac46916d32700e41fb9bc73e9418c_cryptolocker.exe 28
Processes
-
C:\Users\Admin\AppData\Local\Temp\2024-06-02_6c4ac46916d32700e41fb9bc73e9418c_cryptolocker.exe"C:\Users\Admin\AppData\Local\Temp\2024-06-02_6c4ac46916d32700e41fb9bc73e9418c_cryptolocker.exe"1⤵
- Loads dropped DLL
- Suspicious use of WriteProcessMemory
PID:1612 -
C:\Users\Admin\AppData\Local\Temp\lossy.exe"C:\Users\Admin\AppData\Local\Temp\lossy.exe"2⤵
- Executes dropped EXE
PID:2612
-
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
- Path C:\Users\Admin\AppData\Local\Temp\lossy.exe
- Size 44KB
- SHA256 f8bf9867816eebf508c7bb51e8522b68e57aeb0dd15bb6992ad41aca04f08467
- MD5 49f4df06febd97a23a3f7fe691f5bff7
- SHA1 bdfc82d2e3600728d82f78fc191563135ef39a8d
- SHA512 e74221fa3294bff51edeca7f04658541666487fa49ae0ecd1e319f5cc959b1c1af3b024c9f6dc1d68d8eddc0fe8f7a7d6f2be82a57baaaff4990d384890231fd
- SSDEEP 768:bCDOw9UiaKHfjnD0S16avdrQFiLjJvtAH0F:bCDOw9aMDooc+vAUF
- MD5 SHA1 SHA512 SSDEEP