Rokku gives every file its own Salsa20 key, seals that key with RSA and stores it in the file's last bytes before renaming it with .rokku, so the single free test decryption on its Tor site proves nothing about the remaining files. Active in March and April 2016, it skips anything over 30 MB, wipes shadow copies and restore points, and leaves a TXT copy of README_HOW_TO_UNLOCK beside an HTML one in each affected folder. The payment page asked 0.2403 bitcoin and showed a QR code for sending it. Keys are generated locally, so encryption needs no network connection, and nothing stays in startup once the run ends. Its code layout resembles Chimera, though the two handle keys differently.
Sources: In-house research
File extensions: .rokku
Ransom note filenames: README_HOW_TO_UNLOCK.html, README_HOW_TO_UNLOCK.txt
Decryptor: No public decryptor was found.
Data exfiltration risk: Undocumented — Rokku encrypts offline without contacting a key server, and no data theft is tied to it.
Systems typically targeted: Windows PCs; document, image, media and project files under 30 MB are encrypted.
Do this first: Shadow copies and restore points are deleted, so go straight to offline backups. Each file carries its own key, so an attacker-decrypted test file says nothing about the rest. The binary leaves no persistence, so the notes and encrypted samples are the main evidence.
Dealing with an active incident? Our incident response team is available 24/7.
Emergency response: +1 (877) 364-5161