Ransomware Groups 0APT and KryBit Engage in Public Feud, Leaking Each Other's Data

Ransomware Turf War: 0APT and KryBit Groups Hack Each Other in Public Feud, Leaking Ops Data

LOW
April 29, 2026
4m read
Threat ActorRansomware

Related Entities

Threat Actors

0APTKryBit

Other

HalcyonOliver Newbury

Full Report

Executive Summary

A public and retaliatory feud between two ransomware groups, 0APT and KryBit, has resulted in both operations being compromised and their internal data leaked. The conflict, occurring in late March and early April 2026, saw 0APT first leak data from KryBit's administrator panel. KryBit quickly retaliated by hacking 0APT, defacing its leak site, and exposing its entire operation. The counter-leak revealed that 0APT's claims of over 190 victims were fraudulent and, embarrassingly, that its infrastructure was hosted on an Android phone. This public infighting provides a rare glimpse into the amateur side of the cybercrime ecosystem and will almost certainly compel both groups to cease operations, rebrand, and rebuild their infrastructure.

Threat Overview

The turf war provides valuable intelligence on the structure and operations of lower-tier ransomware groups.

  • Initial Attack: 0APT breached KryBit and leaked its admin panel, exposing details about its operators, five affiliates, and around 20 potential victims. Ransom demands were noted to be between $40,000 and $100,000.
  • Retaliation: KryBit responded by hacking 0APT's infrastructure. They defaced the leak site with the message, "Next time, don't play with the big boys."
  • Data Dump: The next day, KryBit leaked 0APT's full dataset. This revealed that 0APT had faked the vast majority of its claimed victims from January 2026 and that no data had actually been exfiltrated from them. The most damaging revelation was that 0APT's infrastructure was running on an Android phone's internal SD card, indicating a highly amateurish setup.

Technical Analysis

The incident highlights poor operational security (OPSEC) on both sides. For two cybercrime groups to successfully hack each other suggests fundamental security flaws in their infrastructure and practices. 0APT's infrastructure running on an Android phone is a particularly stark example of amateurism. Such a setup would be highly unstable, insecure, and easily traceable compared to the robust, bulletproof hosting typically used by professional cybercrime syndicates.

The conflict itself is a form of Data from Private Repositories (T1530), where the private repositories are the groups' own administrative panels and backend servers.

MITRE ATT&CK Techniques (as perpetrated by the groups against each other)

Impact Assessment

  • Disruption of Operations: Both 0APT and KryBit have been effectively dismantled by these mutual leaks. Their operational infrastructure, affiliate networks, and victim data have been exposed, forcing them to go offline.
  • Loss of Credibility: In the ransomware ecosystem, credibility is key to coercing payment. By exposing 0APT as a fraud and both groups as having poor security, their ability to extort victims is severely diminished. Affiliates are also unlikely to work with them in the future.
  • Intelligence Gain for Law Enforcement: The leaked data, including operator details and victim lists, provides valuable intelligence for law enforcement agencies investigating these groups.
  • Market Dynamics: This event illustrates the intense competition and financial pressure within the crowded ransomware market. As noted by Oliver Newbury of Halcyon, such infighting suggests these groups are struggling financially, as credibility is essential for their business model.

IOCs — Directly from Articles

No specific Indicators of Compromise (IOCs) were provided in the source articles.

Cyber Observables — Hunting Hints

This event is less about hunting for enterprise threats and more about intelligence gathering on the cybercrime ecosystem. However, some general observables for identifying amateur ransomware operations can be inferred:

Type
other
Value
Infrastructure hosted on consumer-grade hardware or services
Description
As seen with the Android phone, amateur groups may use cheap, non-resilient hosting, which can sometimes be easier to trace.
Type
other
Value
Inconsistent or fabricated victim data on leak sites
Description
Cross-referencing claims on leak sites with public breach notifications can help identify fraudulent actors.
Type
domain
Value
Domains registered with non-bulletproof registrars
Description
Professional groups use registrars that ignore abuse complaints. Amateur groups may use standard registrars, making takedowns easier.

Detection & Response

N/A - This article describes a conflict between threat actors, not an attack on an enterprise.

Mitigation

N/A - This article describes a conflict between threat actors, not an attack on an enterprise. The primary takeaway for defenders is the intelligence gained about the internal dynamics and varying sophistication levels within the ransomware ecosystem.

Timeline of Events

1
March 28, 2026
The feud begins, with 0APT reportedly breaching and leaking data from KryBit.
2
April 12, 2026
The public conflict between the two groups concludes, with KryBit having retaliated and leaked 0APT's data.
3
April 29, 2026
This article was published

Timeline of Events

1
March 28, 2026

The feud begins, with 0APT reportedly breaching and leaking data from KryBit.

2
April 12, 2026

The public conflict between the two groups concludes, with KryBit having retaliated and leaked 0APT's data.

Sources & References

Article Author

Jason Gomes

Jason Gomes

• Cybersecurity Practitioner

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.

Threat Intelligence & AnalysisSecurity Orchestration (SOAR/XSOAR)Incident Response & Digital ForensicsSecurity Operations Center (SOC)SIEM & Security AnalyticsCyber Fusion & Threat SharingSecurity Automation & IntegrationManaged Detection & Response (MDR)

Tags

Ransomware0APTKryBitThreat ActorInfightingCybercrimeOPSEC

📢 Share This Article

Help others stay informed about cybersecurity threats

🎯 MITRE ATT&CK Mapped

Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.

🧠 Enriched & Analyzed

Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.

🛡️ Actionable Guidance

Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.

🔗 STIX Visualizer

Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.

Sigma Generator

Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.