Skip to navigation

Threat reportRansomwareTL-2026-0844

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

mediumACTIVE

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.

Key facts

IdentifiersTL-2026-0844
Also known asClaimed Twice, Double-Claiming, Double Extortion Re-Claiming, Ransomware Victim Re-Listing
SeverityMEDIUM
Affected productsCross-sector Ransomware-targeted organizations (victims of prior breaches)
MalwareBlackCat (ELF), BlackCat - S1068, Clop - S0611, LockBit, Qilin, RansomHub, beast
MITRE ATT&CK techniquesT1078 Valid Accounts, T1133 External Remote Services, T1190 Exploit Public-Facing Application, T1199 Trusted Relationship, T1213 Data from Information Repositories, T1486 Data Encrypted for Impact, T1567 Exfiltration Over Web Service, T1567.002 Exfiltration to Cloud Storage, T1583 Acquire Infrastructure, T1583.004 Server, T1585 Establish Accounts, T1586 Compromise Accounts and 3 more in the attack flow
MotivationFINANCIAL
Target sectorshealthcare, financial, government, cross-sector
Target regionsNorth America, Europe, Global
Detection rules9 (1 shown free)
Sources7 cited sources

Detection coverage

As of 2026-06-17, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-0844 across Splunk SPL, Microsoft KQL and Sigma, covering 20 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.

Free detection: Valid-Account Reuse From New Source After Prior Breach — Initial Access (SPL)

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

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

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

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. Sign up free to unlock the detection rules or query them with the Threadlinqs MCP server (Purple)
  • Public-Facing Service Exploitation Preceding Valid-Account Foothold — Initial Access (KQL) · unlock with TL Creds
  • Trusted-Relationship Repository Access + Mass Document Reads — Post-Exploitation (KQL) · unlock with TL Creds
  • Large Outbound Web-Service Exfiltration to Anomalous Cloud Host — Exfil/Impact (KQL) · unlock with TL Creds
  • Fabricated / Plagiarized Leak-Site Claim — Name-Only or Implausible Velocity (Sigma) · unlock with TL Creds
  • Same Victim Posted Under Two Brands Same-Day — Cartel / Shared-Access (Sigma) · unlock with TL Creds
  • Duplicate Victim Claim With Recycled Sample / Timing-Heuristic Triage (Sigma) · unlock with TL Creds
  • Bulk Information-Repository Collection + Local Staging Archive — Post-Exploitation (SPL) · unlock with TL Creds
  • Identical Exfil-Bundle Hash Reappearing Under Distinct Actors — Recycled-Data / Resale (SPL) · unlock with TL Creds

Indicators of compromise

As of 2026-06-17, Threadlinqs Intelligence tracks 20 indicators of compromise for TL-2026-0844.

20 indicators of compromise · unlock with TL Creds. Compare plans

Technical analysis

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.

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 techniques by tactic:

Initial Access

T1078 Valid Accounts; T1133 External Remote Services; T1190 Exploit Public-Facing Application; T1199 Trusted Relationship

Persistence

T1078 Valid Accounts

Collection

T1213 Data from Information Repositories

Impact

T1486 Data Encrypted for Impact; T1657 Financial Theft

Exfiltration

T1567 Exfiltration Over Web Service; T1567.002 Exfiltration to Cloud Storage

Resource Development

T1583 Acquire Infrastructure; T1583.004 Server; T1585 Establish Accounts; T1586 Compromise Accounts; T1588.002 Tool; T1608 Stage Capabilities

Remediation

Immediate actions

  • On any duplicate leak-site claim, demand and verify proof-of-breach data samples before reacting; a name-only post proves nothing.
  • Compare any second-claim sample against the first breach's leaked data to determine whether it is new or recycled.
  • Route any second extortion claim through legal counsel before making disclosure or notification decisions.

Workarounds

  • Treat ecosystem victim-count statistics with skepticism; deduplicate and exclude fabricated/plagiarized claims before trend reporting.
  • Use claim-timing heuristics: same-day = cartel/shared access; days-to-weeks = affiliate churn/re-extortion; months-apart = likely repeat victimization.

Longer-term hardening

  • After any breach, fully remediate the underlying root cause (vulnerability, exposed service, leaked credentials) rather than treating the incident as a one-off cleanup, to prevent repeat victimization.
  • Force-rotate and invalidate all credentials exposed in a breach, since access brokers resell the same valid credentials to multiple buyers.
  • Distinguish data-handling problems (where paying is ineffective because distinct actors hold distinct copies) from systemic security gaps, and prioritize closing the security gap.
  • Maintain leak-site and cartel-succession tracking so dual claims can be correlated to shared infrastructure or brand absorption.

Affected and fixed versions

  • Cross-sector — Ransomware-targeted organizations (victims of prior breaches)
    Vulnerable versions: Organizations that fail to remediate root cause or rotate exposed credentials after a first breach
    Fixed in: Organizations that fully remediate root cause and invalidate exposed credentials post-incident

Timeline

  • Change Healthcare breach data allegedly reappears via RansomHub after the original ALPHV/BlackCat affiliate is stiffed on payment in ALPHV's exit scam — an early, widely cited case of affiliate non-payment resale producing a second leak-site claim for one intrusion.
  • The Dispossessor group engages in wholesale reposting of victim lists lifted from Cl0p, LockBit, and Hunters International without holding any original access — a documented precedent for fabricated/recycled duplicate claims.
  • DragonForce publicly announces its shift to a ransomware cartel model, inviting affiliates to operate under their own brands while using DragonForce tooling — a structural precursor to multi-brand duplicate claims.
  • Qilin spikes to 71 victims in a single month, closely correlated with a new partnership/affiliate-migration announcement — illustrating how affiliates moving between programs reclaim the same victims under a new flag.
  • RansomHub infrastructure goes offline; DragonForce claims RansomHub joined the cartel and stands up a portal for migrating affiliates, seeding 'one attack, counted twice' dual-brand postings.
  • 0APT posts 91 victims in 48 hours in late January 2026, the start of a fabrication wave later shown to be fake (mobile-phone-hosted leak site, random-data download links).
  • 0APT posts 458 victims the following month; fabricated claims account for 549 of Q1 2026 totals, single-handedly flipping the apparent year-over-year trend from +15% to -6%.
  • Rival group KryBit breaches 0APT's infrastructure and leaks its logs, confirming 0APT's claims were fabricated (leak site run from a mobile phone, fake/random download links).
  • Q1 2026 closes with 3,014 raw victim claims (15% YoY increase); after removing 0APT's 549 fabricated claims the deduplicated total is 2,465 (6% YoY decrease).
  • Bitdefender publishes 'Claimed Twice', analyzing 49 distinct victims / 98 leak-site claims over a five-month window and codifying five double-claiming mechanisms plus an IR triage framework.

Sources cited

Previous and next in ransomware

Drafted by the Threadlinqs research pipeline from 7 sources; published ; last updated —.

Threadlinqs Intelligence — Real-Time Threat Detection Platform

// threat_feed
$ sort --newest
Showing all threats

Live intelligence console

Threat level

Latest Threats