Prometheus
Alert when a public recovery tool comes out, when compatibility changes and when a new variant appears.
Summary
Ransomware written in .NET, apparently derived from the codebase of win.hakbit (Thanos) ransomware.
Text from the open source (public malware catalogue or MITRE ATT&CK), unedited: it may be outdated or cover only one variant.
Recovery
Public tool under conditions
| Tool | Variant | Recovery |
|---|---|---|
| Cycraft · Prometheus Decryptorverified on 11 Nov 2026 | whole family | confirmed — Prometheus (in the examples, .PROM[prometheushelp@mail.ch] files); finds the password by brute-forcing the tickcount, validating by file type (list of supported formats) or by a user-supplied pattern. |
| Avast · Prometheus Decryptorverified on 11 Nov 2026 | whole family | conditional — Only some variants, with an original and encrypted pair; cited extensions such as .[cmd_bad@keemail.me].crypt, .reofgv, .y9sx7x, .BRINKS_PWNED, .9ten0p and .[ID-<PC-ID>].unlock. |
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
A guide to Prometheus 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 Prometheus
- In the manual's examples, encrypted files get the suffix .PROM(prometheushelp@mail.ch) after the original extension.
- Extensions with the attacker's e-mail (.(cmd_bad@keemail.me).crypt) or random ones (.reofgv, .y9sx7x) and a note such as UNLOCK_FILES_INFO.txt or HOW_TO_DECYPHER_FILES.txt on the desktop.
- Extensions cited by the sources: .(cmd_bad@keemail.me).VIPxxx, .(cmd_bad@keemail.me).crypt, .(cmd_bad@keemail.me).CRYSTAL, .(KingKong2@tuta.io).crypt, .reofgv, .y9sx7x, .(black_privat@tuta.io).CRYSTAL, .BRINKS_PWNED, .9ten0p, .uo8bpy.
- Ransom notes cited by the sources: HOW_TO_DECYPHER_FILES.txt, UNLOCK_FILES_INFO.txt, Инструкция.txt.
- Different families can use the same extension. If in doubt, check the Vexday search.
2. Free tools
- Cycraft · Prometheus Decryptor, works: Prometheus (in the examples, .PROM(prometheushelp@mail.ch) files); finds the password by brute-forcing the tickcount, validating by file type (list of supported formats) or by a user-supplied pattern. Official page
- What you need: An encrypted file in a format the tool recognizes (or a known piece of the content, as text or bytes); the GUI version is for Windows.
- Limits: Only finds the key in formats whose magic number it recognizes, unless the user supplies a pattern; it may point to wrong keys and the brute force can take long; the current-tickcount option is Windows only.
- Avast · Prometheus Decryptor, works under conditions: Only some variants, with an original and encrypted pair; cited extensions such as .(cmd_bad@keemail.me).crypt, .reofgv, .y9sx7x, .BRINKS_PWNED, .9ten0p and .(ID-<PC-ID>).unlock. Official page
- What you need: A file pair (an original and its encrypted copy). Cracking the password uses all CPU cores and may take tens of hours; it is done once per PC.
- Limits: Avast says only some Prometheus variants can be decrypted.
3. Use the tool safely
- Copy the encrypted files to another disk and work only on the copy. Keep the originals untouched.
- Download the tool only from the official page above, never from another site.
- Set aside a file pair: the original (from a backup, an e-mail or another machine) and the same file encrypted.
- Run the tool on a machine isolated from the network, following the vendor's manual.
- Open a few recovered files to check them before deleting anything.
Warnings the vendor highlights:
- Validation by file type may accept a wrong key: check the result.
- The search can be long; the current file can be skipped.
- Only some variants are decryptable.
- Cracking the password takes up the whole CPU for a long time.
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
- 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.
- CERT.br · Computer Emergency Response Team BrazilFIRST
- Apura CSIRT · Apura DFIR / CSIRT TeamFIRSTServes: Companies
- CAIS/RNP · Brazilian Academic and Research Network CSIRTFIRSTServes: Research and education
- CSIRT-INTER · Banco Inter Computer Security Incident Response TeamFIRSTServes: Financial sector
- CSIRT PETROBRASFIRSTServes: Industrial sector
- CSIRT Soow Sigma · CSIRT Soow Sigma - Computer Security Incident Response TeamFIRSTServes: Government, Public and private sectors
- CTIR Gov-BR · Cyber Incident Prevention, Handling and Response Center of Brazilian GovernmentFIRSTServes: Government, Public and private sectors
- NTTDATA-BR-CERTFIRSTServes: Companies
- Nubank CSIRT · Nu CSIRTFIRSTServes: Financial sector
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: .61gutq .9ten0p .[black_privat@tuta.io].CRYSTAL .BRINKS_PWNED .[cmd_bad@keemail.me].crypt .[cmd_bad@keemail.me].CRYSTAL .[cmd_bad@keemail.me].VIPxxx .hard .iml .[KingKong2@tuta.io].crypt .PROM[prometheushelp@mail.ch] .reofgv .secure .secure[milleni5000@qq.com] .unlock .uo8bpy .y9sx7x
note: HOW_TO_DECYPHER_FILES.txt UNLOCK_FILES_INFO.txt Инструкция.txt
source:
Groups using the family
- prometheus operates the family · corroborated, high confidence
Detection
The detection packages of the groups that operate or use the family: the indicators (IOCs) and YARA rules from open intelligence, to hunt for the group in your own environment. The package is published per group, not per family.
- prometheus: 1 YARA rule(s) — see the group's detection
Source: open intelligence on the groups. The YARA rules and the full package are on the SOC, MSSP and Enterprise plans.
Related families
Code lineage: Hakbit → Prometheus
- Prometheus is a variant of Hakbit · corroborated, high confidence
"Variant of" means one family's code derives from the other's, per the source of each link. It does not mean the operators are the same.
Indicators
No indicator linked to this family.