30,797 victim claims · 335 groups · 2020-01-01 to 2026-08-22 · generated 22 Aug 2026
Leak-site publication dates, not intrusion dates. A spike is a disclosure event, not necessarily an attack wave. The final point is a partial month and will read low.
Cumulative mode is the one that answers succession questions. When one brand's curve flattens and another's takes off at the same moment, that is the shape of a handoff.
| Group | Claims | Status | First seen |
|---|
Rows are groups ordered by first appearance, columns are months, cell brightness is volume. A row going dark while a new row lights up directly underneath is the visual signature of a rebrand handoff. Check the lineage field on a group profile before calling it one.
A proxy for new-brand emergence. Rebrands enter here too, so a rise is not automatically more crews.
Clustering at the right edge is normal and means nothing. Clustering earlier marks exits, takedowns or rebrands.
| Group | Claims | Status | Last seen |
|---|
Searches victim name, website and the leak-site description text.
Pick a brand, see which others look like they took over from it, click one to extend the chain. Walk it backwards to ask who came before instead.
Debut at scale. The successor's first month is already at operating volume. Across brands with 25 or more claims the median first month is claims and the median brand debuts at of its eventual peak, so arriving fully formed is rare. Two conditions must both hold: at the brand's own ceiling and at the predecessor's operating scale, because a brand that posts once and vanishes trivially satisfies the first. Caught conti to royal, where royal opened at 43 claims, 10.8 times conti's median month.
Baton pass. The successor's share of the pair's combined monthly volume moves from near zero to near one while the predecessor gives way. Scale-free by construction, which is the point: blacksuit opened at 3 claims against an eventual 34, so any measure relative to its own peak reads that as noise even though royal was collapsing from 25 to 1 in the very same months. A novelty gate suppresses brands that were already running at scale and simply carried on when a big one died.
Shared victims. The same victim claimed by both brands. The weakest signal despite looking like the strongest. One affiliate posting to two panels, two crews extorting the same victim independently, both buying from the same access broker, and outright false claims all produce it. It is also completely absent from the clearest rebrand in the data: royal and blacksuit share zero victims.
Targeting continuity. Country and sector mix carrying over. Nonzero on 98.8 percent of eligible pairs, because almost every brand hits a US-heavy manufacturing and services mix, so its bar sits at the 95th percentile and it never orders this list and can never carry a lead alone.
Recorded. What the source file states. The only non-inferred tier, and sparse: 14 links. It does not record royal to blacksuit or blacksuit to chaos, so absence here means nothing.
Ranking is strength first, corroboration second: the strongest fired signal plus 35 percent of the others. Counting signals instead would let three weak ones outrank one decisive one. Thresholds sit at each signal's own distribution across all eligible pairs, so a badge means unusual, not merely present.
Validation, and why the flattering number was thrown out. Scoring against the lineage field inside the ransomware.live file returns 10 of 10, but that field is itself derived from leak-site data, so the test is partly circular. The honest test is this site's own curated lineage file, which is built from vendor reporting and code analysis independently of posting patterns. Those results are below and they are much more modest.
Two structural limits that number exposes. First, the curated file records code lineage as well as operational handoff. An edge like "Crysis derived from Dharma" describes malware ancestry and leaves no signature in posting behaviour whatsoever; this tool measures when an operation moves between brands, which is a different question. Second, most curated edges cannot be tested at all, because the brands predate leak sites or never posted enough to score. That is a coverage ceiling, not a tuning problem.
What it cannot do. Identify people. Separate a rebrand from an affiliate migration, or either from two unrelated crews with similar targeting. Detect a successor that never posted, or one below the 8-claim scoring floor. Confidence does not accumulate along a chain: each step is an independent lead, so a four-brand chain is less certain than any single step in it, not more.
Fetched from ransomware.live now, through this site's own relay. Everything else in this console is a fixed snapshot built on 22 Aug 2026; this tab is the only part that changes on its own.
Recent cyberattacks are incident reports collected by ransomware.live from public reporting. They are a different kind of record from the victim claims in the rest of this console: not leak-site posts, and not necessarily ransomware.
Source: ransomware.live leak-site monitoring. Figures are victim claims published by criminal groups and may include duplicates, re-posts or false claims; they are not confirmed incidents. Leak sites also undercount, because victims who pay quickly are often never posted, so real incident volume is higher than anything shown here. Dates are leak-site publication dates, the field the API calls attackdate, not the date the scraper saw the post and not the intrusion date. Country is missing on a large share of records and sector on more, so both breakdowns are floors and never censuses. Rebrands appear as separate groups, so brand counts are a weak proxy for the number of active crews: check the lineage field on a profile before reading a decline as a death. Coverage before 2022 is thinner than later years because the scraper ecosystem matured over time, which makes growth-since-2020 claims unsafe. 142 records dated before 2020-01-01 are held out of this console and remain in the master files. Group status is derived here, not published by anyone: Active means a claim within 30 days of the newest record, Slowing within 90, Dormant within a year, Inactive beyond that.