This page covers Un1que, a member of the IEncrypt ransomware family that adds .un1que to every file it locks, so photo.jpg becomes photo.jpg.un1que. Instead of a single note, it writes a separate demand next to each locked file, named after it with _readme appended (for example photo.jpg.un1que_readme.txt ). The text tells the victim their network was breached, insists the files cannot be recovered without paying, and asks for an email that names the company. IEncrypt is aimed at businesses: each attack normally uses its own suffix, often derived from the victim organisation or machine name, and the family is traced back to BitPaymer. The .un1que build was logged in January 2020. Neither source documents data theft.
Sources: In-house research
File extensions: .un1que
Decryptor: We checked the public decryptor listings on 2026-10-26 and could not confirm whether one exists.
Data exfiltration risk: Undocumented — The notes describe a hacked and encrypted network but make no claim of stolen data, and no leak site is associated with this variant.
Systems typically targeted: Windows business networks
Do this first: Keep one of the per-file _readme notes and a matching .un1que file, and treat the incident as a network intrusion rather than a single infected PC.
From the ransom note un1que_readme.txt:
Hello [redacted] Your network was hacked and encrypted. No free decryption software is available on the web. Email us at WHITNEY.MCDOWELL[@]PROTONMAIL[.]COM (or) KOREY.COBB[@]TUTANOTA[.]COM to get the ransom amount. Keep our contacts safe. Disclosure can lead to impossibility of decryption. Please, use your company name as the email subject. TAIL: - KEY: -
Dealing with an active incident? Our incident response team is available 24/7.
Emergency response: +1 (877) 364-5161