Group-IB Exposes Five Brokers Fabricating Breach Alerts From Old Leaks

Group-IB identified five dark web brokers posting 500–1,000 fake corporate breach ads monthly using recycled Facebook 2021, Eatigo, and Truecaller leak data.
Group-IB Exposes Five Brokers Fabricating Breach Alerts From Old Leaks
Table of Contents
    Add a header to begin generating the table of contents

    Gulf region banks and financial institutions have been triggering full incident response workflows — legal review, breach notification preparation, executive escalation — on corporate breach alerts that Group-IB now documents as fabricated. Research published May 20, 2026, identifies five Chinese-speaking dark web brokers that collectively post 500 to 1,000 fraudulent corporate breach advertisements each month. The underlying data is not fresh; it is repackaged from three publicly known historical leaks.

    Five Brokers, Thousands of Fraudulent Breach Listings

    Group-IB analyzed more than 17,000 broker messages across Telegram channels and dark web forums to identify the operations and document their methods. The five brokers are: Aiqianjin, a Telegram channel with approximately 5,000 subscribers; Yiqun Data, operating on Telegram with 431 subscribers; Phoenix Overseas Resources, with more than 400 Telegram subscribers; Exchange Market/Deepmix, active on dark web forums since 2013; and Chang’An Sleepless Night, operating through a dark web marketplace.

    Aiqianjin and Four Partners: The Scale of a Fraudulent Breach Ecosystem

    If the advertised intrusions were real, five brokers collectively producing 500 to 1,000 breach disclosures per month would represent a volume of successful corporate compromises that has never been observed in the history of documented cybercrime. Group-IB’s cross-referencing analysis confirmed the advertisements are not real. The brokers construct fake breach samples by combining records from three historical public exposures: the Facebook leak of April 2021 that exposed 553 million user records, the Eatigo restaurant platform data dump from October 2020, and the Truecaller directory exposure from April 2022. Names, phone numbers, password hashes, and email addresses from these separate multi-year-old incidents are recombined and reformatted to resemble freshly exfiltrated corporate databases.

    How Group-IB Identifies Recycled Data

    The fabrications carry structural artifacts that distinguish recycled data from genuine breach samples when analyzed systematically. Password hashes from the Eatigo dataset appear alongside contact details from Truecaller for the same alleged individual victim — a pairing that would be impossible if the records came from a single compromised organization. Field names inside presented “corporate” databases include values no real enterprise schema would contain, such as “bond investment volume” or “forex account balance,” added to calibrate the samples toward financial sector audiences. Mixed-language field values and systematic errors in Arabic-translated data appear consistently across samples, inconsistent with how legitimate business records from Arabic-speaking organizations would be structured.

    Facebook 2021, Eatigo 2020, Truecaller 2022: The Three Source Datasets Behind the Fabrications

    All three source datasets are years-old public exposures that have circulated through breach-tracking databases and dark web repositories since their original disclosures. Group-IB identified the source fingerprints by matching field formats, hash structures, and record patterns against known breach characteristics from its reference database. The brokers modify column names, inject fictional business-specific fields, and present the recombined data inside sample previews formatted to resemble enterprise database exports — specifically designed to pass the kind of superficial inspection an incident response analyst might run on an initial alert before engaging deeper investigation resources.

    The Real Operational Cost: Phantom Breach Response

    The financial and operational damage is concrete even when no actual breach occurred. A breach alert flagged by a dark web monitoring service triggers a defined corporate response: legal counsel is engaged to assess notification obligations, breach notification timelines under applicable regulations begin running, executives are briefed, and security analysts begin scoping the potential exposure. That process consumes hours of security team capacity and real budget on an event that never happened.

    Group-IB notes the brokers specifically target Gulf region financial institutions — banks, bonds operations, foreign exchange services, and investment platforms. Regulatory frameworks in the region, including requirements under ADGM, DFSA, and Saudi SAMA, make the appearance of a breach expensive enough that organizations face real pressure to pay for verification or suppression. The fabrications are constructed to exploit that regulatory cost structure by mimicking the kind of breach a Gulf financial institution would find most credible and most urgent to investigate.

    Defending Against Threat Intelligence Pollution

    The core defense Group-IB identifies is cross-referencing: comparing advertised sample records against known historical breach fingerprints before committing incident response resources. Organizations that receive breach alerts sourced from unvalidated dark web monitoring should treat unverified samples as unconfirmed until the underlying data has been checked against known public leaks. Breach monitoring services that can integrate systematic deduplication against historical exposure databases provide substantially stronger signal than services that pass raw dark web listings directly to enterprise alert queues without provenance validation.

    The Group-IB research also highlights a broader threat to threat intelligence reliability: as fabricated breach listings grow in volume and sophistication, security operations teams face an increasing false-positive load that competes with response capacity for real incidents occurring at the same time.

    Related Posts