KeyLock is .NET ransomware for Windows, reported in late 2023, that targets companies. Each locked file gains .keylock on top of its own name ( 1.jpg ends up as 1.jpg.keylock ), the desktop background tells the victim to look for the README file, and every folder gets a note named with lowercase README-id-, then the logged-in user name, then .txt. That note says the key is kept on a remote server, will unlock up to three small files for free as proof, wants Bitcoin, and lists keychain[@]onionmail.org and keybranch[@]mailfence.com for contact. If nobody replies within 72 hours, the attackers say they will publish company files and sell databases and personal records, although no leak site has turned up. Cut the affected machine off the network, keep the note and a sample of encrypted files, and check remote-access and outbound logs for signs of theft. A later build, Whole, has its own page.
Sources: In-house research
File extensions: .keylock
Ransom note filenames: README-id-[username].txt
Contact addresses: keybranch[@]mailfence[.]com, keychain[@]onionmail[.]org
Operator domains: hxxps[://]t[.]me/key_chain
Decryptor: No public decryptor was found. Checked 2026-11-11.
Data exfiltration risk: Likely — The note threatens to publish company files and sell databases and personal data if there is no contact within 72 hours. No leak site or independent proof of theft has been found.
Systems typically targeted: Windows systems at companies; the note talks about files on the victim's server and about customers and partners. Databases are named as the data most likely to be sold.
Do this first: The note file name includes the logged-in user or a victim ID, so save the exact file found in each folder. Treat the publication threat as possible and review outbound traffic and remote-access logs from before encryption. Check other hosts for files ending in .keylock or .whole.
From the ransom note README-id-[username].txt:
########################################## ######## YOUR FILES ARE ENCRYPTED ###### ########################################## - Your files have been encrypted with strong encryption algorithms and modified and now have the '.keylock' extension! The file structure was not damaged. Don't worry your unique encryption key is stored securely on our server and your data can be decrypted quickly and securely. […]
Checked by: Proven Data research
Dealing with an active incident? Our incident response team is available 24/7.
Emergency response: +1 (877) 364-5161