# Ransomware Double-Claiming: Same Victim Listed Under Multiple Leak-Site Flags (Bitdefender 2026 Extortion-Ecosystem Analysis)

> Bitdefender research tracking 49 distinct victim organizations that generated 98 leak-site claims over a five-month period (January-June 2026) identifies five mechanisms behind a 2026 trend in which the same ransomware victim is listed under different group names: cartel/multi-brand structures, affiliate non-payment data resale, true repeat victimization, access-broker credential resale, and outright fabrication/plagiarism. The findings supply incident-response triage guidance for assessing duplicate extortion claims and warn that fabricated claims (e.g. 0APT's 549 fake claims) materially distort ecosystem-level victim counts.

- **Published:** 2026-06-17T00:00:00Z
- **Last reviewed:** 2026-06-17T00:00:00Z
- **Canonical:** https://intel.threadlinqs.com/threat/TL-2026-0844
- **Card image:** https://intel.threadlinqs.com/og/threat/threat-intel-ransomware-victim-double-claiming-tl-2026-0844.webp?v=e561f529 (Threadlinqs threat intel: Claimed Twice Ransomware Double-Claims: Analysis & Hunting (TL-2026-0844) — Medium severity, 20 IOCs, 9 detection rules.)
- **ID:** TL-2026-0844
- **Severity:** MEDIUM
- **Category:** RANSOMWARE
- **Status:** ACTIVE
- **Detections:** 9 (1 shown free below) · **IOCs:** 20

## Description

This is ecosystem and tradecraft (TTP) threat intelligence rather than a single-vulnerability advisory. Bitdefender threat researchers assembled a deliberately curated set of 49 confirmed duplicate-victim cases — organizations whose names appeared on two or more ransomware leak sites under different group brands — totaling 98 leak-site claims across a five-month tracking window in the first half of 2026. The study identifies five distinct mechanisms that produce a 'claimed twice' outcome, each carrying a different operational meaning for defenders and incident responders.

Mechanism 1 — Cartel / multi-brand structure ('one attack, counted twice'): Two brands operating inside the same criminal network post the same breach. The DragonForce cartel (which publicly announced its cartel model on 19 March 2025 and offers affiliates up to 80% of proceeds) absorbed displaced RansomHub affiliates after RansomHub's infrastructure went offline on 1 April 2025; Qilin exhibited a 'gravitational pull consistent with the absorption of displaced affiliates.' Same-day dual postings most often indicate this shared-network structure or shared initial access.

Mechanism 2 — Affiliate non-payment data resale: An unpaid affiliate relocates a stolen dataset to a competing platform. The Change Healthcare case is the canonical example: an affiliate who executed the breach via ALPHV/BlackCat allegedly never received their cut after the victim paid, and the same data then reappeared via RansomHub. These dual claims typically appear days-to-weeks apart, reflecting affiliate churn and re-extortion.

Mechanism 3 — Repeat victimization (genuine multiple breaches): An organization is breached, treats it as a one-off cleanup, never remediates the underlying exposure, and is breached again — frequently by a different group. These claims tend to be months apart. The triage signal is whether the organization's security posture actually changed between incidents.

Mechanism 4 — Access-broker resale: A single set of valid credentials obtained during a first breach is sold by an initial-access broker to multiple buyers, who each independently extort the victim. Paying one group does not bind another, because distinct actors hold distinct copies and operate without any shared agreement.

Mechanism 5 — Fabrication / plagiarism: Groups invent or copy victims without legitimate access. 0APT posted 91 victims in 48 hours in late January 2026, then 458 the following month; its leak site was reportedly being run from a mobile phone and its download links piped random data — the fraud was exposed when rival group KryBit breached 0APT's infrastructure. Post-Operation Cronos, LockBit falsely attributed Evolve Bank data as purported Federal Reserve victim data. Dispossessor wholesale reposted victim lists from Cl0p, LockBit, and Hunters International.

Quantitative impact: Q1 2026 raw victim counts showed 3,014 victims (a 15% year-over-year increase); removing 0APT's 549 fabricated claims reduced the total to 2,465 (a 6% year-over-year decrease) — meaning one fabricated brand was 'the entire distance between ransomware surged and ransomware fell.' Across the 49-victim study set, the median gap between first and second claim was 12 days (mean ~23 days, maximum 96 days), with 5 same-day claims, 16 within the first week, 12 in the 8-30 day band, and 16 at 31+ days.

Incident-response triage framework: (1) Verify proof-of-breach data samples — a group that posts a victim name without a sample has only 'demonstrated the ability to type'; (2) determine whether samples are new or recycled from earlier leaks; (3) assess group relationships via shared infrastructure, cartel ties, and succession timing; (4) evaluate whether the organization's security posture changed since the first breach (if not, it is repeat victimization). Second claims should be routed through counsel before any disclosure decision, and defenders must distinguish data-handling failures (where payment is ineffective) from systemic security gaps.

## MITRE ATT&CK

- T1583 Acquire Infrastructure
- T1583.004 Server
- T1585 Establish Accounts
- T1586 Compromise Accounts
- T1588.002 Tool
- T1608 Stage Capabilities
- T1078 Valid Accounts
- T1133 External Remote Services
- T1190 Exploit Public-Facing Application
- T1199 Trusted Relationship
- T1078 Valid Accounts
- T1213 Data from Information Repositories
- T1567 Exfiltration Over Web Service
- T1567.002 Exfiltration to Cloud Storage
- T1486 Data Encrypted for Impact
- T1657 Financial Theft

## Free detection (Splunk SPL, Microsoft KQL, Sigma)

**Valid-Account Reuse From New Source After Prior Breach — Initial Access (SPL)** (`TL-2026-0844-SPL-001`)

Detects an interactive/remote logon (Windows RDP LogonType 10, or external remote-service auth) succeeding with an account previously involved in a confirmed breach, originating from a source IP not seen for that account before. This is the access-broker resale / affiliate-reuse pattern (Mechanism 4 / Mechanism 2): the same valid credential set is replayed by a second buyer, producing a second extortion event for one organization. Pair with a lookup of breach-exposed accounts to suppress noise.

- **Languages:** Splunk SPL, Microsoft KQL, Sigma
- **ATT&CK:** T1078, T1133, T1190
- **Data sources:** windows_security, wineventlog, sentinel_securityevent
- **Severity:** high
- **Confidence:** medium

### Splunk SPL

```spl
index=wineventlog sourcetype="WinEventLog:Security" EventCode=4624 (Logon_Type=10 OR Logon_Type=3) Account_Name!="*$"
| lookup breached_credentials.csv user AS Account_Name OUTPUT exposed_date breach_id
| where isnotnull(exposed_date)
| iplocation Source_Network_Address
| stats earliest(_time) AS first_seen latest(_time) AS last_seen dc(Source_Network_Address) AS src_count values(Source_Network_Address) AS src_ips values(Country) AS countries by Account_Name breach_id
| where src_count > 1
| eval days_since_breach=round((first_seen - strptime(exposed_date,"%Y-%m-%d"))/86400,0)
| table Account_Name breach_id exposed_date src_ips countries src_count first_seen last_seen
| sort - src_count
```

### Microsoft KQL

```kql
let breached = datatable(user:string, exposed_date:datetime, breach_id:string)['svc-backup-mock', datetime(2026-01-15), 'TL-2026-0844-B1'];
SecurityEvent
| where TimeGenerated > ago(90d)
| where EventID == 4624 and LogonType in (3, 10)
| where AccountType == 'User' and not(Account endswith '$')
| join kind=inner (breached) on $left.TargetUserName == $right.user
| summarize FirstSeen=min(TimeGenerated), LastSeen=max(TimeGenerated), SrcCount=dcount(IpAddress), SrcIps=make_set(IpAddress) by TargetUserName, breach_id, exposed_date
| where SrcCount > 1
| extend DaysSinceBreach = datetime_diff('day', FirstSeen, exposed_date)
| project TargetUserName, breach_id, exposed_date, SrcIps, SrcCount, DaysSinceBreach, FirstSeen, LastSeen
```

### Sigma

```yaml
title: Valid-Account Reuse From New Source Reusing Previously-Breached Credential
id: 7c2a1f64-9b3d-4e21-8a77-1f0c5e9d4a01
status: experimental
description: Detects logon with an account known to have been exposed in a prior breach from a source not previously associated with that account, indicating access-broker resale or affiliate credential reuse driving a second extortion claim.
references:
    - https://www.bitdefender.com/en-us/blog/businessinsights/claimed-twice-five-reasons-same-ransomware-victim-appears-under-two-flags
author: Threadlinqs Team
date: 2026/06/17
tags:
    - attack.initial_access
    - attack.persistence
    - attack.t1078
    - attack.t1133
logsource:
    product: windows
    service: security
detection:
    selection:
        EventID: 4624
        LogonType:
            - 3
            - 10
    filter_machine:
        TargetUserName|endswith: '$'
    condition: selection and not filter_machine
falsepositives:
    - Legitimate use of shared service accounts from multiple jump hosts
    - VPN concentrators presenting NAT'd source addresses
level: medium
```

**Known false positives:**

- Shared service accounts legitimately used from multiple administrative jump hosts
- VPN/NAT egress presenting many source IPs for one account

**Tuning notes:** Maintain the breached_credentials lookup from your IR records and force-rotate exposed accounts; exclude known VPN/NAT egress ranges and approved jump-host IPs to cut false positives. Lower the src_count threshold only if exposed accounts are tightly scoped.

### 8 more detection rules (Splunk SPL, Microsoft KQL, Sigma), unlock with TL Creds

- Public-Facing Service Exploitation Preceding Valid-Account Foothold — Initial Access (KQL) (locked: unlock with TL Creds)
- Trusted-Relationship Repository Access + Mass Document Reads — Post-Exploitation (KQL) (locked: unlock with TL Creds)
- Large Outbound Web-Service Exfiltration to Anomalous Cloud Host — Exfil/Impact (KQL) (locked: unlock with TL Creds)
- Fabricated / Plagiarized Leak-Site Claim — Name-Only or Implausible Velocity (Sigma) (locked: unlock with TL Creds)
- Same Victim Posted Under Two Brands Same-Day — Cartel / Shared-Access (Sigma) (locked: unlock with TL Creds)
- Duplicate Victim Claim With Recycled Sample / Timing-Heuristic Triage (Sigma) (locked: unlock with TL Creds)
- Bulk Information-Repository Collection + Local Staging Archive — Post-Exploitation (SPL) (locked: unlock with TL Creds)
- Identical Exfil-Bundle Hash Reappearing Under Distinct Actors — Recycled-Data / Resale (SPL) (locked: unlock with TL Creds)

Sign up free to unlock the detection rules: https://threadlinqs.com/?modal=signup

## Sources

- [Claimed Twice: Five Reasons the Same Ransomware Victim Shows Up Under Two Flags](https://www.bitdefender.com/en-us/blog/businessinsights/claimed-twice-five-reasons-same-ransomware-victim-appears-under-two-flags)
- [Bitdefender Threat Debrief | June 2026](https://www.bitdefender.com/en-us/blog/businessinsights/bitdefender-threat-debrief-june-2026)
- [Ransomware Attacks Against the US: 2026 Insights](https://www.bitdefender.com/en-gb/blog/businessinsights/ransomware-attacks-targeting-us-organizations-2026)
- [The Godfather of Ransomware? Inside DragonForce's Cartel Ambitions](https://www.levelblue.com/blogs/spiderlabs-blog/the-godfather-of-ransomware-inside-dragonforces-cartel-ambitions)
- [Ransomware Spotlight: DragonForce](https://www.trendmicro.com/vinfo/us/security/news/ransomware-spotlight/ransomware-spotlight-dragonforce)
- [DragonForce Ransomware Cartel vs. Everybody](https://blog.barracuda.com/2025/06/09/dragonforce-ransomware-cartel-vs--everybody)
- [The DragonForce Cartel: Scattered Spider at the gate](https://www.acronis.com/en/tru/posts/the-dragonforce-cartel-scattered-spider-at-the-gate/)

## Full data

The other 8 detection rules (Splunk SPL / Microsoft KQL / Sigma) unlock with TL Creds; a free account includes daily creds: https://threadlinqs.com/?modal=signup
Indicator values unlock with TL Creds, at a lower price on Red and Purple; AI agents can query rules and IOCs through the Threadlinqs MCP server (Purple): https://intel.threadlinqs.com/mcp

Canonical: https://intel.threadlinqs.com/threat/TL-2026-0844
