A new ransomware variant known as C77L (also referenced as X77C) has emerged, detected in November 2025 in infection reports shared through cybersecurity communities. This version appends a unique 10-character random string followed by the “.OXOfUbfa” extension to encrypted files (e.g., photo.jpg.3n3Q2PsdhA.OXOfUbfa) and drops a ransom note titled “#Restore-My-Files.txt.”
Victims are informed that their data has been stolen and encrypted, and they are warned that leaks will occur within 72 hours if contact is not established. The attackers use email (rickgerli98@gmail.com) and Telegram (@Us9890) as communication channels, claiming they will decrypt three files for free as proof of authenticity.
This C77L build demonstrates the group’s continued evolution — blending data exfiltration, timed extortion, and encryption to pressure victims into paying quickly.
Our C77L Decryptor — Forensic Data Restoration & Analysis
Our threat response engineers have developed a specialized decryptor framework to safely assess and attempt recovery from C77L ransomware infections. This decryptor combines forensic-grade analysis with a controlled restoration process to maintain data integrity and evidence preservation.
Key features of our decryptor:
Executes within a sandboxed recovery environment to isolate the infection.
Identifies the variant signature (e.g., extension format, ransom ID, or contact string).
Conducts a Proof-of-Concept (PoC) decryption test on sample files before full restoration.
Generates chain-of-custody and integrity reports for insurance or legal documentation.
It supports both cloud-linked and air-gapped operation modes, ensuring compatibility for enterprise and high-security systems. Every recovery attempt begins with read-only data validation, ensuring no corruption of encrypted evidence.
Disconnect infected devices from local networks, Wi-Fi, and backups immediately.
Do not rename, delete, or move encrypted files — they are critical for key analysis.
Collect all forensic evidence: ransom notes, malware samples, and relevant system logs.
Perform a memory dump (RAM capture) — encryption keys or process handles may remain in memory.
Avoid contacting attackers via email or Telegram directly; instead, involve professional negotiators or recovery experts.
Data Recovery & Decryption Options
Standard Recovery Routes
Offline or Immutable Backups Restoration from verified backups remains the most reliable recovery option. Confirm the backup’s integrity and ensure all infected machines are isolated before reintroducing clean data.
Free Decryptor Status Currently, there is no public decryptor for the latest C77L variant. However, earlier versions have occasionally been cracked through law enforcement decryption key releases. Victims should monitor trusted portals like No More Ransom for updates.
Professional Recovery Methods
Analyst-Guided Decryption Service Our analysts analyze the encrypted data and ransom note, perform key reconstruction testing, and if viable, proceed with full-scale restoration under controlled forensic conditions.
Ransom Payment (Not Recommended) C77L actors typically increase ransom costs after the 72-hour window. Paying does not guarantee safe recovery and funds further criminal development.
How to Use Our C77L Decryptor — Step-by-Step
Step 1 — Identify the Infection Look for encrypted files ending in random 10-character extensions plus .OXOfUbfa and locate the ransom note #Restore-My-Files.txt.
Step 2 — Secure the Environment Disconnect infected systems from networks, storage servers, and external drives.
Step 3 — Engage Our Response Team Submit 2–3 encrypted samples and the ransom note via our secure intake portal for variant fingerprinting.
Step 4 — Launch the Decryptor Run the decryptor tool with administrative privileges; internet access is optional depending on whether cloud key validation is used.
Step 5 — Enter the Decryption ID Input the unique ID from the ransom note (e.g., C6DD06F8) to align with your encryption key batch.
Step 6 — Begin Restoration After key confirmation, the decryptor restores files to a separate directory while generating proof-of-integrity logs.
C2 connections to attacker infrastructure via Gmail and Telegram APIs
Disabling of Windows Shadow Copies and recovery features
Tactics, Techniques & Procedures (TTPs)
Initial Access: Phishing attachments, RDP exploitation, or cracked software.
Execution: File encryption using AES + RSA hybrid cipher.
Persistence: Ransom note autorun entries and wallpaper modifications.
Exfiltration: Theft of sensitive files prior to encryption.
Defense Evasion: Shadow copy deletion and log clearing.
Impact: Encrypted systems, public data leaks, and potential data resale.
Victim Landscape
Geography:
Industries Targeted:
Timeline:
Conclusion
The C77L ransomware family continues to evolve, blending traditional encryption with aggressive double-extortion tactics. This latest variant adds modern communication channels like Telegram and Gmail, shortens ransom deadlines, and includes “free decryption” samples to lure victims into trust. Its moderate ransom demands make it appealing for broad, fast-moving campaigns. Organizations must prioritize rapid isolation, evidence preservation, and engagement with professional decryption services instead of direct contact. Preventative defense — including patched systems, restricted remote access, and redundant offline backups — remains the only long-term safeguard against the ongoing C77L/X77C wave.
Frequently Asked Questions
Currently, there is no public decryptor. Victims should preserve samples and monitor No More Ransom for developments.
No. It is a psychological tactic to build trust before extortion.
Disconnect affected devices, preserve evidence, and contact a verified ransomware response team.
Implement 2FA on remote systems, update software regularly, block unsafe file types in email filters, and maintain immutable backups.
It’s rarely effective and often illegal in some jurisdictions. Always consult cyber law and insurance professionals before considering it.
Expert-Built SolutionWeHave Decryptor: Fast and Reliable Recovery Our cybersecurity team has reverse-engineered key aspects of the SolutionWeHave ransomware encryption routine. By studying its cryptographic structure and analyzing attack patterns, we developed a specialized decryptor that has successfully recovered data for numerous victims worldwide. This decryptor is optimized for Windows, Linux, and VMware ESXi environments, ensuring…
In our recovery lab today at Lockbit Decryptor, we isolated the MORTAR ransomware strain, identified by victim-specific ID extensions (e.g., .4RcrXfvVksS5ACA) and the README-[ID].txt note. Our forensic analysis confirms this is a sophisticated, enterprise-targeting ransomware operation. This strain employs a robust hybrid cryptosystem. Critically, our analysis indicates that this variant correctly implements the cryptographic primitives,…
Introduction The cybersecurity landscape has witnessed the emergence of Black ransomware as a significant threat, infiltrating systems, encrypting vital files, and demanding ransom in exchange for decryption keys. As the frequency and sophistication of these attacks escalate, individuals and organizations are grappling with the daunting task of data recovery. This comprehensive guide provides an in-depth…
Overview Gunra ransomware has emerged as a formidable cyber threat, infiltrating systems, encrypting vital files, and extorting victims by demanding ransom payments. As these attacks grow increasingly sophisticated and widespread, both individuals and enterprises face enormous challenges in regaining access to their data. This comprehensive guide explores the nature of Gunra ransomware, its effects, and…
Our Solara Decryptor: Engineered for Fast & Accurate Recovery Solara ransomware, based on the Chaos framework, encrypts user files, adds the .solara extension, and leaves behind a ransom note named read_it.txt. Our cybersecurity team has reverse-engineered its encryption logic and developed a professional-grade decryptor capable of restoring files on Windows environments. Designed for precision, our…
