Analysis
-
max time kernel
150s -
max time network
151s -
platform
windows10-2004_x64 -
resource
win10v2004-20240426-en -
resource tags
arch:x64arch:x86image:win10v2004-20240426-enlocale:en-usos:windows10-2004-x64system -
submitted
08-06-2024 07:04
Behavioral task
behavioral1
Sample
2024-06-08_3bf485761dd9a09e91c9fb6d968deb71_cryptolocker.exe
Resource
win7-20240221-en
Behavioral task
behavioral2
Sample
2024-06-08_3bf485761dd9a09e91c9fb6d968deb71_cryptolocker.exe
Resource
win10v2004-20240426-en
General
-
Target
2024-06-08_3bf485761dd9a09e91c9fb6d968deb71_cryptolocker.exe
-
Size
57KB
-
MD5
3bf485761dd9a09e91c9fb6d968deb71
-
SHA1
293f3d9a6e5ab495dbe1fa78e3d35d34c6fd9373
-
SHA256
3f34a18e027dd2b798bc28341c948df1772ed552090c6041ffe71fd592175fc0
-
SHA512
c02ff2b3dbb38972f2fdfc704e584d207b0d86a4816aa03b824b164cc4a57d62176a17ff4cb5c39df1d325aa8a681ba745f84981e40a3a507f589e476baa77d5
-
SSDEEP
768:bP9g/WItCSsAfFaeOcfXVr3BPOz5CFBmNuFgUjlgzCY:bP9g/xtCS3Dxx0nCY
Malware Config
Signatures
-
Detection of CryptoLocker Variants 2 IoCs
resource yara_rule behavioral2/memory/4732-0-0x0000000000400000-0x000000000040E000-memory.dmp CryptoLocker_rule2 behavioral2/files/0x0008000000023403-13.dat CryptoLocker_rule2 -
UPX dump on OEP (original entry point) 2 IoCs
resource yara_rule behavioral2/memory/4732-0-0x0000000000400000-0x000000000040E000-memory.dmp UPX behavioral2/files/0x0008000000023403-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-1162180587-977231257-2194346871-1000\Control Panel\International\Geo\Nation 2024-06-08_3bf485761dd9a09e91c9fb6d968deb71_cryptolocker.exe -
Executes dropped EXE 1 IoCs
pid Process 5064 gewos.exe -
resource yara_rule behavioral2/memory/4732-0-0x0000000000400000-0x000000000040E000-memory.dmp upx behavioral2/files/0x0008000000023403-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 4732 wrote to memory of 5064 4732 2024-06-08_3bf485761dd9a09e91c9fb6d968deb71_cryptolocker.exe 81 PID 4732 wrote to memory of 5064 4732 2024-06-08_3bf485761dd9a09e91c9fb6d968deb71_cryptolocker.exe 81 PID 4732 wrote to memory of 5064 4732 2024-06-08_3bf485761dd9a09e91c9fb6d968deb71_cryptolocker.exe 81
Processes
-
C:\Users\Admin\AppData\Local\Temp\2024-06-08_3bf485761dd9a09e91c9fb6d968deb71_cryptolocker.exe"C:\Users\Admin\AppData\Local\Temp\2024-06-08_3bf485761dd9a09e91c9fb6d968deb71_cryptolocker.exe"1⤵
- Checks computer location settings
- Suspicious use of WriteProcessMemory
PID:4732 -
C:\Users\Admin\AppData\Local\Temp\gewos.exe"C:\Users\Admin\AppData\Local\Temp\gewos.exe"2⤵
- Executes dropped EXE
PID:5064
-
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
-
Filesize
58KB
MD5d04326b598b450c027e1e5cf681d35c9
SHA13770ada6ec453b0995ade6ade3eeef699f659d96
SHA2564ba62121f38d2ef456729e744aa48dc0bf03d5d5f0f9127b125e20bf503cdaba
SHA512cd84b39bc3340f86c27d3f6f86c1fb3f701add8e4c71df6e6611a2433c37be975f569b731a8c581c8b1198925c3a4dcecd3f2a19cf01c81455a4220dbfcf48b2