Revision (v3.0 / 2026-10-21): Restructured so general readers can follow it, and §5 recast as “How to counter this”. Cybernews’s article (archived) and IDMerit’s statement were re-read. Added: IDMerit acknowledged that ports associated with independent data sources “could have been open”; Cybernews’s note (the finder was an outside contributor, and it learned of the payment exchange later); and the US class action’s filing and dismissal. Sources suspected of being AI-generated, and a network of KYC blogs of unclear ownership, were removed. v2.0 (2026-07-03) had already recast the first version, which treated the exposure as established, as a dispute.
Summary
IDMerit denied that it owns, controls or stores customer data or the data held by independent data sources, and said there was no exposure in its own environment. It did, however, acknowledge that certain ports associated with independent data sources could have been open. Cybernews’s basis for attribution was clues such as collection names and its team’s belief; neither side has published records showing who owned the database. If you cannot show from records whose custody found data was in, closing the database does not settle who must notify, or who is responsible.
A pre-execution check means checking, before data is placed, whose custody and which contract it falls under against the ledger, and keeping a record. Detection means noticing after an open database is found. The dates below are when the researcher, Cybernews or the court confirmed or disclosed a point, not when data was placed in the database.
but whose it was stays unsettled
What got through
- What got through
- Personal data apparently used for identity verification was placed in a password-less MongoDB database and kept readable from the internet (per Cybernews). Whether the party that placed it was IDMerit or a data source is disputed.
- What was stopped
- The database was closed the day after the researcher’s notification (November 12, 2025).
- What reached the receiving side
- In general, identity-check data flows across vendors, data sources and the links between them. When an open database is found, whose custody it is in cannot be told from the database itself.
- Not disclosed
- Records, such as hostnames, that directly identify the database’s owner; how the ports IDMerit acknowledged could have been open relate to the database that was found; any regulator finding. The figures and contents are Cybernews’s claims and have not been independently confirmed.
Pre-execution check
Whatever the route, the condition for telling them apart is that whoever places data checks, before placing it, whose custody the data is in and under which contract it was entrusted, against the ledger kept by the party that entrusted it, and records where it was placed.
Finding an open database does not settle whose data it was; without records of custody, notification and responsibility stay undecided.
- Who approves
- The party that entrusted the data (such as a financial institution that outsources identity checks). For the vendor and the data sources beyond it, it sets by contract which data may be stored (or not) and where, and keeps that in a ledger. It does not rely on the vendor’s own “we don’t store it” statement.
- Where it is checked
- The mechanism that places and stores data (the procedures that create or copy a database). It refuses to place data under a custodian or location that is not in the ledger.
- What is recorded
- For each set of data, who controls it, the basis it was entrusted on (the contract), and where and for how long it was placed, kept in a form that can be shown to a third party later, so that you can answer from records whether it was yours when challenged.
Detection worked, and the database was closed the day after notification. But “an open database existed” and “whose custody the data was in” are separate facts, and without records neither the side denying it nor the side reporting it could show the second. A similar case, where personal data was left outside the core, is Sumsub.
What Lemma does
Lemma builds the pre-execution check into the side that places and stores data. It does not look for intrusions; before the data is placed, it checks the custodian and contract against the ledger and keeps that record in a form a third party can verify later.
Industries and operations to watch
- IndustryFinance & FinTech
- Financial institutions, payment and crypto businesses that outsource identity checks by API. Users’ data also reaches the data sources beyond the vendor.
- OperationLookup & data access
- Querying outside data sources about users for identity checks. Each query moves data across organisations.
Current controls vs Lemma
The route in this case is column 1 (placing and storing data), but who placed it has not been disclosed. Column 2 is deciding whose data it is after an open database is found, which is the heart of this dispute. Column 3 is storage at the data sources beyond the vendor; it is close to the ports IDMerit acknowledged could have been open, but their relation to the database found has not been disclosed.
| Control | Placing and storing data | Identifying the owner after an open database is found | Storage at data sources beyond the vendor |
|---|---|---|---|
| The vendor’s “we don’t store it” | Partial | Not relevant | Not effective |
| Data-processing contracts (storage, location) | Partial | Not effective | Partial |
| Checking databases’ exposure settings | Not relevant | Not effective | Not relevant |
| Discovery and reporting by researchers | Not relevant | Partial | Not relevant |
| Lemma (pre-execution check) | Effective | Effective | Partial |
The vendor’s statement can account for the vendor’s own environment, not the data sources beyond it. Contracts, even when set, do not settle a dispute without records outsiders can check. Checking exposure settings finds open databases, but not whose they are. Researchers’ discovery and reporting got the database closed the next day, but whose it was was never settled. Lemma checks custodian and contract against the ledger before placing, and keeps a record you can answer from when challenged.
Note: Lemma’s check works only when it is built into the mechanism that places and stores data and the ledger is managed apart from the party placing the data. Records do not settle a dispute if the records themselves can be falsified, so they must be kept in a form that can be checked independently of the parties. Asking for records from data sources beyond the vendor also makes contract negotiations heavier. The table compares what each control checks; it does not show whether this incident would have been stopped. Lemma does not detect or prevent intrusions.
Three things to confirm in an organisation that outsources identity checks
- Can you name the data sources your vendor queries and where data is stored?
- Do you confirm your vendor’s “we don’t store it” with records, not just the statement?
- If told your users’ data had been found, could you answer from records whether it was in your custody?
Facts and timeline
- Who
- IDMerit, based in California, which connects to 440+ data sources in 180+ countries to provide identity verification by API (per the company).
- Discovery
- An outside researcher working with Cybernews found a password-less MongoDB database on November 11, 2025. It was closed the day after notification, on November 12. Publication came on February 18, 2026.
- Claimed scale (unverified)
- About 3 billion records; about 1 billion broken down by country and said to contain sensitive personal data, with the rest likely logs. About 1TB, 26 countries; about 203 million in the US and 124 million in Mexico, among others.
- Data types (claimed)
- Names, addresses, dates of birth, national ID numbers, phone numbers, email addresses, gender, telecom metadata and more.
- Basis for attribution
- Cybernews wrote that “our team believes the exposed database belongs to IDMerit”, citing clues such as collection names in some countries (“idmtelco”). It did not publish hostnames or similar evidence directly identifying the owner.
- IDMerit’s denial
- It does not own, control or store customer data or data held by independent data sources. Its review found no exposure, vulnerability or unauthorised access in the IDMerit environment. It did acknowledge that certain ports associated with independent data sources could have been open, potentially exposing databases. It said that when it asked for the report it was asked for money, and suspected a ransom motive.
- Cybernews’s note
- The finder was an outside contributor, and Cybernews did not know until February 26 about the exchange between the finder and IDMerit over payment for the findings. Its internal researchers reviewed the technical material and found the findings legitimate.
Glossary
Data source — An outside holder of data, such as a telecom or public records, that an identity-verification company queries. Such companies connect to many sources to return a result.
Custody — Whose control data is under, and who is responsible for protecting it. Breach notification and liability follow from custody.
MongoDB — A widely used database. Depending on its settings, it can be readable from the internet without a password.
Timeline
- A researcher finds the password-less database and reports it.
- The database is closed.
- Cybernews publishes. The next day it retitles the piece “IDMerit data breach” and rewrites the database as “owned by IDMerit”.
- Biometric Update publishes IDMerit’s denial.
- Cybernews learns of the payment exchange between the finder and IDMerit (per its note).
- A class action against IDMerit is filed in the US District Court for the Southern District of California.
- The plaintiff voluntarily dismisses the case; no ruling was made.
The figures and contents are Cybernews’s claims and have not been independently verified. IDMerit’s denial is not backed by records that outsiders can check either. As of October 2026, there has been no regulator finding and no disclosure identifying the database’s owner. This Brief does not rule on either side’s claims. What has not been disclosed does not mean there were no controls.
After disclosure
- Cybernews: Maintained that the findings were legitimate, and noted that it does not sell fixes.
- IDMerit: Around the same time published blog posts on its no-storage design, without referring to the case directly.
Sources
- Primary, finder’s reportCybernews “IDMerit data breach: 1 billion records of personal data exposed in KYC data leak”
- Primary, court docketUS District Court Andrizzi v. IDMerit LLC, No. 3:26-cv-01527 (S.D. Cal., filed 2026-03-11, dismissed 06-03)
- Primary, complaintUS District Court Complaint in Andrizzi v. IDMerit LLC
2 more (reporting, analysis)
- Reporting, carries IDMerit’s statementBiometric Update “IDMerit disputes report of 1B records exposed in unsecured ID verification database”
- Reporting, carries IDMerit’s statementFox News “1 billion identity records exposed in ID verification data leak”
References: “The last layer left for cyber defense in the age of AI”
The facts of this case are disputed between the parties, and this Brief does not rule on either side’s claims.