Writing · · 7 min read
SBI told its investors. Who tells the 3,897?
India’s largest bank found its customers’ details on the dark web and filed a notice with the stock exchanges. What we know, what we do not, and what it teaches anyone who keeps a customer list.
By Liju Abdul Karim, Founder & MD, BRev Digital, Dubai

On 21 October 2026 the State Bank of India told the stock exchanges about an “incident involving data loss”. A first look at about 375,000 records found on the dark web had turned up 3,897 records holding customers’ personal details. The bank said it expects no material impact on its operations, its finances or its business continuity.
That sentence is written for shareholders, and it is probably true. But the people inside those 3,897 records are not shareholders. When the Internet Freedom Foundation wrote to the bank the same day, it could find no notice, advisory or message to them.
What happened
- 16 October. SBI was alerted by its threat-intelligence provider, the Defence Cyber Agency and CERT-In, India’s computer emergency response team, that customer information appeared to be on the dark web.
- The claim. A group calling itself “Siriusim” said it had released 3.75 lakh (375,000) rows of SBI data and 2,722 PDF documents, including loan applications and account-opening forms. That claim is unverified.
- What SBI found. In its preliminary analysis, 3,897 records with personal information: names, mobile numbers, dates of birth, gender, email and home addresses, branch and CIF (customer) identifiers, lead IDs, and details attached to loan and lead records.
- 21 October. SBI filed its disclosure, activated its incident-response process and hired an independent, CERT-In-empanelled firm to establish whether the data is genuine, how complete it is, and where it came from.
- What it is not, so far. No passwords, PINs or balances have been reported in the set, and SBI says account balances are safe.
What we do not know yet
| Question | Answer today |
|---|---|
| Where did the data leave from? | Not established. SBI has not said whether its own systems were breached. |
| How many people? | Unknown. 3,897 is a count of records, not people; one person can appear in several. |
| The other 371,000 rows and the 2,722 PDFs? | Not addressed in the disclosure. |
| Will customers be told? | The disclosure does not say. |
The leak is rarely the vault. It is the copy.
Look at the field list again: lead IDs and loan and lead metadata. That is the shape of the place a loan enquiry lives before it becomes an account: a sales pipeline, a direct-selling agent, a CRM export, a spreadsheet sent to a partner. This is my inference, not a finding; SBI has named no source. But it is a pattern I have watched my whole career. The core system is the most guarded copy of the data. The leak comes from the least guarded one.
SBI has met this before. In January 2019, TechCrunch reported that the server behind SBI Quick, the text-message and missed-call balance service, sat in a Mumbai data centre with no password. Anyone who found it could read outgoing messages with balances, phone numbers and partial account numbers, close to three million of them on a single day. The core bank was not touched then either. A copy was.
My first job was application and network support at Saint-Gobain in Andheri, Mumbai: Active Directory, the RSA server for secure sign-in, the NAS that held everyone’s files. It taught me that security is a list of who may do what. Incidents like this one add a second list, and it is the harder one: where every copy lives.
“No material impact” is a sentence for investors
India’s rules today are built around telling the regulators. CERT-In’s 2022 directions ask for a report within six hours; the RBI’s cyber framework asks for one within two to six. Telling the customer is a different matter. Section 8(6) of the Digital Personal Data Protection Act, 2023 will require a company to inform the Data Protection Board and each affected person, but under the staggered start that duty only takes effect in May 2027. The RBI’s March 2026 advisory recommends SMS, email and in-app notices to affected customers. It is a recommendation.
So a bank can do everything the rules require today and the customer still learns about it from the news. For the person whose name, mobile number, date of birth, address and loan enquiry are on a forum, the material impact is the next phone call from “the bank” that already knows all of it.
Every AI tool is another copy
I build AI systems for a living, so I will say the uncomfortable part. When a team pastes a customer list into a public AI chat to “clean it up” or “find the duplicates”, it has made one more copy, outside its own walls, that nobody has on the list. Nobody meant harm. That is how most copies are made.
This is why, at BRev Digital, when the data is sensitive we put the AI on the firm’s own machines, where the copy stays inside the building and the list of who may read it is still the firm’s own list.
If you keep customer data, check this week
- Count the copies. The production database, the backups, the exports, the CRM, the agent or vendor, the spreadsheet in someone’s email, the AI tools.
- For each copy, write three things: who may read it, who may export it, and when it is deleted.
- Ask your vendors the same three questions, in writing.
- Write the customer message now, before you need it: what happened, which fields, what you will never ask them for, and the number to call.
If you bank with SBI
Be wary of any call, SMS, email or WhatsApp message that quotes your loan, your address or your customer number back to you. Knowing those details proves nothing now. SBI says it never asks for an OTP, PIN, password or user ID. In India, report fraud on the national cyber crime helpline, 1930, or at cybercrime.gov.in, and to your branch.
How many copies of your customer list exist right now? If the answer takes longer than a minute, start there.
Sources
- Internet Freedom Foundation, “SBI told investors its data breach doesn’t matter. What about the 3,897 customers it affected?”, 21 October 2026 (the filing, the timeline, DPDP s. 8(6), CERT-In and RBI rules, RBI Advisory 3/2026)
- Business Today, 21 October 2026 (the fields SBI listed)
- IBTimes India (SBI on balances)
- Open, “SBI dark-web exposure explained” (records versus people)
- TechRadar Pro
- PYMNTS on TechCrunch’s January 2019 SBI Quick report and Business Insider India