ransomware

kuiper

Alert when a public recovery tool comes out, when compatibility changes and when a new variant appears.

Summary

The source has no description for this family.

Recovery

No known public tool

Before any tool

  • Preserve the encrypted files, the ransom note and any backups before trying anything.
  • Test the tool on a copy of the files, in an isolated environment, following the vendor's instructions.
  • A decryptor for the family does not guarantee recovery for every variant.

Recovery guide

General guidance, valid for any family. · published on 10 Nov 2026

General guidance for the first hours, valid for any family. It does not replace an incident response team.

1. Contain

  • Disconnect the affected machines from the network (cable and Wi-Fi). If you cannot isolate them, shut them down to stop the spread.
  • Disconnect the backups too and check that they were not encrypted.
  • Change the passwords of administrative, VPN and service accounts from a clean machine: attackers usually hold stolen credentials.

2. Preserve the evidence

  • Do not delete the encrypted files or the ransom note. They identify the family, and a tool may appear later.
  • Keep the logs (firewall, VPN, domain controller, antivirus or EDR) and, if possible, a copy of the disks and memory of the affected machines.
  • Write down what happened and when: the timeline helps the investigation and the notifications.

3. Identify the family

  • Look the family up in the Vexday search by file extension, ransom note file name or sample hash.
  • Check whether a free tool exists on No More Ransom and on the vendor's official page.
  • A tool works for the family and sometimes only for some variants. Always test it on a copy of the files, in an isolated environment, following the vendor's instructions.

4. Recover safely

  • Restore from verified backups, only after removing the attacker's access. Restoring earlier can reinfect the environment.
  • When in doubt, rebuild the compromised machines from a trusted image.
  • Paying the ransom does not guarantee that the data comes back or that it will not be published.

5. Report the incident

  • Personal data: check your country's data protection law; many require notifying the authority and the data subjects within short deadlines.
  • National CSIRT: report the incident to your country's CSIRT or CERT.
  • Police: file a report with the cybercrime unit.
  • Cyber insurance: tell the insurer before hiring incident response; many policies require it.

Under attack: who to call

In Brazil, besides the CSIRTs
  • Personal data involved: notify the ANPD. Under the LGPD (art. 48), the controller notifies the ANPD and the data subjects of an incident that may cause relevant risk or harm, within 3 business days (ANPD Resolution CD/ANPD No. 15/2024). The data protection officer files it through SEI!ANPD. How to notify the ANPD
  • File a police report. Ransomware is a crime. Many states have police units specialized in cybercrime; keep the ransom note and the encrypted files as evidence.

CSIRTs · Brazil

The country's incident response teams (CSIRTs), from the ENISA and FIRST lists. Each one serves a constituency: check it before writing.

Another country: Argentina · Chile · Colombia · Costa Rica · Dominican Republic · Ecuador · Spain · Guatemala · Mexico · Panama · Peru · Portugal · El Salvador · Uruguay · Venezuela

Source: ENISA and FIRST lists · updated on 16 Nov 2026

Variants

No variant cataloged.

Extensions and ransom notes

No extension or note cataloged.

Groups using the family

No group with a documented link.

Indicators

867 indicators linked to this family

  • md5_hash · c5efbe6a9df102220ed99f8d8156c7fa · community indicator feed
  • sha256_hash · defd6b754c6fa5e1323d557ad6d1dd1707649a3ef60637e0ad9a806df82feb5f · community indicator feed
  • sha1_hash · 5e4e2dcd23d3a4abbd8d50bd7dcc2d03ae4dfeae · community indicator feed
  • sha1_hash · 3208c03639d81012d221578fa254d81433c7a15a · community indicator feed
  • md5_hash · 4e9b523f07c5e9ecd045597f5343c589 · community indicator feed
  • md5_hash · 67d734942ed7c5ddee2466ccb815530f · community indicator feed
  • sha256_hash · 233a34e56f0fb194bf3019e1fbe1f5fbd9ad23a800b7f5d3d58d4fc38ed44382 · community indicator feed
  • sha256_hash · 5414de616cb7cad3e8652004e8aff3a067ed97a30a781c2fe73bb5f029efac30 · community indicator feed
  • sha1_hash · 088bc52858afc282cf1324088272efdc343be603 · community indicator feed
  • sha256_hash · 08c9759bbc6fdf3dbd3873a15d1685af5433f937ab2a0990b93658d4dba896b3 · community indicator feed