Analysis
-
max time kernel
150s -
max time network
158s -
platform
windows10-2004_x64 -
resource
win10v2004-20220812-en -
resource tags
arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system -
submitted
24-11-2022 07:46
Static task
static1
Behavioral task
behavioral1
Sample
4c64ed9fbed77e1c5c945e1a4bc6eee105975e10188db6c2c8c93b71d766c2f2.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
4c64ed9fbed77e1c5c945e1a4bc6eee105975e10188db6c2c8c93b71d766c2f2.exe
Resource
win10v2004-20220812-en
General
-
Target
4c64ed9fbed77e1c5c945e1a4bc6eee105975e10188db6c2c8c93b71d766c2f2.exe
-
Size
522KB
-
MD5
788ae412f028ea4e151589900078c753
-
SHA1
9b881f979d1e864fd508900b8cbddfa65256c952
-
SHA256
4c64ed9fbed77e1c5c945e1a4bc6eee105975e10188db6c2c8c93b71d766c2f2
-
SHA512
cb3b6491f4f4eb280719b4e69d8eaa10b06d60c21f394ac1a33e4dfd94d0b48748c8dc1abc374704771255ff0e9abe1c43159c2455e6a036581f694081497f12
-
SSDEEP
6144:a3b43RAVAfjoluC2f2rflM+uyjKMql+9mb8YpbmQy1CrxQqD9RSaSz+8O5AQfMKe:4EkwjoPtr9qBMixy18xQqpx8O5AQf
Malware Config
Signatures
-
Suspicious use of WriteProcessMemory 6 IoCs
Processes:
4c64ed9fbed77e1c5c945e1a4bc6eee105975e10188db6c2c8c93b71d766c2f2.exedescription pid process target process PID 2264 wrote to memory of 3124 2264 4c64ed9fbed77e1c5c945e1a4bc6eee105975e10188db6c2c8c93b71d766c2f2.exe 4c64ed9fbed77e1c5c945e1a4bc6eee105975e10188db6c2c8c93b71d766c2f2.exe PID 2264 wrote to memory of 3124 2264 4c64ed9fbed77e1c5c945e1a4bc6eee105975e10188db6c2c8c93b71d766c2f2.exe 4c64ed9fbed77e1c5c945e1a4bc6eee105975e10188db6c2c8c93b71d766c2f2.exe PID 2264 wrote to memory of 3124 2264 4c64ed9fbed77e1c5c945e1a4bc6eee105975e10188db6c2c8c93b71d766c2f2.exe 4c64ed9fbed77e1c5c945e1a4bc6eee105975e10188db6c2c8c93b71d766c2f2.exe PID 2264 wrote to memory of 5060 2264 4c64ed9fbed77e1c5c945e1a4bc6eee105975e10188db6c2c8c93b71d766c2f2.exe 4c64ed9fbed77e1c5c945e1a4bc6eee105975e10188db6c2c8c93b71d766c2f2.exe PID 2264 wrote to memory of 5060 2264 4c64ed9fbed77e1c5c945e1a4bc6eee105975e10188db6c2c8c93b71d766c2f2.exe 4c64ed9fbed77e1c5c945e1a4bc6eee105975e10188db6c2c8c93b71d766c2f2.exe PID 2264 wrote to memory of 5060 2264 4c64ed9fbed77e1c5c945e1a4bc6eee105975e10188db6c2c8c93b71d766c2f2.exe 4c64ed9fbed77e1c5c945e1a4bc6eee105975e10188db6c2c8c93b71d766c2f2.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\4c64ed9fbed77e1c5c945e1a4bc6eee105975e10188db6c2c8c93b71d766c2f2.exe"C:\Users\Admin\AppData\Local\Temp\4c64ed9fbed77e1c5c945e1a4bc6eee105975e10188db6c2c8c93b71d766c2f2.exe"1⤵
- Suspicious use of WriteProcessMemory
PID:2264 -
C:\Users\Admin\AppData\Local\Temp\4c64ed9fbed77e1c5c945e1a4bc6eee105975e10188db6c2c8c93b71d766c2f2.exestart2⤵PID:3124
-
C:\Users\Admin\AppData\Local\Temp\4c64ed9fbed77e1c5c945e1a4bc6eee105975e10188db6c2c8c93b71d766c2f2.exewatch2⤵PID:5060