Beast ransomware hides a 666 control panel for hands-on encryption attacks
- Severity
- High
- Sources
- 1
What happened
AttackIQ's analysis of a 32-bit Beast ransomware sample (SHA-256 4c44ac1eea4bc7f4ea542d611b5658d7ac2729d79abe750da83f1581cd832eaf) describes ChaCha20 file encryption with Curve25519 key protection, intermittent encryption at 25% of 128 KiB chunks, a .moon extension and a 160-byte footer marker. It stops 52 processes and 73 services, uses Restart Manager exploitation, deletes shadow copies via WMI, and scans TCP 445 from ARP-derived private subnets. Defenders should alert on WMI shadow copy deletion, mass service stops and SMB scanning, block the listed IoCs including mutex BEAST HERE? and the HKCU Run key, and keep offline backups; AttackIQ has released an emulation for testing controls.
For security analysts · Written by AI from 1 source · Wrong?
What to do
- Alert on WMI shadow copy deletion, mass service stops and bursts of SMB scanning on port 445.
- Block the listed indicators of compromise, including the file hash, the BEAST HERE? mutex and the .moon extension.
- Keep backups offline and limit admin rights.
- Use AttackIQ's released Beast emulation to test whether existing controls detect the malware.
Written by AI from the sources, checked against them
Full story timeline · 1 update
Who reported · 1 outlet
Who and what is in it
Threat actors
Companies