ransomware

Everbe Ransomware

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

Public tool under conditions

ToolVariantRecovery
Bleeping Computer · InsaneCrypt Decrypterverified on 11 Nov 2026whole familyconditional — Everbe 1.0 (extensions .[everbe@airmail.cc].everbe, .embrace or .pain), with an encrypted + original pair to find the key by brute force.

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

Guidance specific to this family. · published on 11 Nov 2026

A guide to Everbe built from the tools' official pages, read on 11 November 2026. Use it together with the general guide: containing the attack and preserving evidence come before any tool.

1. Confirm it is Everbe

  • InsaneCrypt: files with the .insane extension. Everbe 1.0: extensions .everbe, .embrace or .pain and the note !=How_recovery_files=!.txt in each folder.
  • Extensions cited by the sources: .embrace, .(everbe@airmail.cc).everbe, pain, .(yoursalvations@protonmail.ch).neverdies@tutanota.com, .everbe, .pain.
  • Ransom notes cited by the sources: !=How_recovery_files=!.txt.
  • Different families can use the same extension. If in doubt, check the Vexday search.

2. Free tool

  • Bleeping Computer · InsaneCrypt Decrypter, works under conditions: Everbe 1.0 (extensions .(everbe@airmail.cc).everbe, .embrace or .pain), with an encrypted + original pair to find the key by brute force. Official page
  • What you need: For Everbe 1.0, an encrypted file and its original version, used by the tool's Bruteforcer to find the key.
  • Limits: For desuCrypt, covers the variant that uses the .insane extension; for Everbe, version 1.0 cited by NMR.

3. Use the tool safely

  1. Copy the encrypted files to another disk and work only on the copy. Keep the originals untouched.
  2. Download the tool only from the official page above, never from another site.
  3. Run the tool on a machine isolated from the network, following the vendor's manual.
  4. Open a few recovered files to check them before deleting anything.

Warnings the vendor highlights:

  • Brute-forcing the key can take quite a while.
  • The encrypted files remain on the disk; only remove them after checking the decrypted ones.
  • Skipped files may be due to lack of access permission.

4. If it does not work

  • Do not delete the encrypted files or the ransom note: new keys and tools can come out later. Follow the family on Vexday to be notified.
  • Get help from an incident response team and follow the general guide to contain, recover and report the incident.
  • Paying the ransom does not guarantee you get your data back.

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

extension: .embrace .everbe .[everbe@airmail.cc].everbe pain .[yoursalvations@protonmail.ch].neverdies@tutanota.com
note: !=How_recovery_files=!.txt

source: public recovery-tool catalogue

Groups using the family

No group with a documented link.

Indicators

No indicator linked to this family.