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.
The turf war provides valuable intelligence on the structure and operations of lower-tier ransomware groups.
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.
T1190 - Exploit Public-Facing Application: The most likely method used by each group to breach the other's web-based leak site or admin panel.T1078 - Valid Accounts: One group may have guessed, brute-forced, or otherwise obtained credentials for the other's backend.T1498 - Network Denial of Service: While not explicitly mentioned, defacement is a form of DoS, making the service unavailable.T1530 - Data from Private Repositories: Both groups collected and leaked data from each other's private infrastructure.No specific Indicators of Compromise (IOCs) were provided in the source articles.
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:
otherInfrastructure hosted on consumer-grade hardware or servicesotherInconsistent or fabricated victim data on leak sitesdomainDomains registered with non-bulletproof registrarsN/A - This article describes a conflict between threat actors, not an attack on an enterprise.
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.
The feud begins, with 0APT reportedly breaching and leaking data from KryBit.
The public conflict between the two groups concludes, with KryBit having retaliated and leaked 0APT's data.

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.
Help others stay informed about cybersecurity threats
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.
Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.
Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.
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 detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.