SBI told investors its data breach doesn’t matter. What about the 3,897 customers it affected?
retained text
[Donate Now](https://static.internetfreedom.in/donate) # tl;dr On 21 October 2026, the State Bank of India informed the BSE and NSE that it had experienced an incident involving the loss of certain data. The bank learnt of it on 16 October through alerts from its threat intelligence vendor, the Defence Cyber Agency and CERT-In, after the data had already appeared on the dark web. Of about 3.75 lakh records found there, SBI identified 3,897 customer records containing names, mobile numbers, dates of birth, addresses, CIF identifiers and loan details. The filing tells investors there is no material impact on the bank's core business. It does not say whether a single affected customer has been told. The law that would require SBI to do so, Section 8(6) of the Digital Personal Data Protection Act, 2023, will come into force only in May 2027. The RBI's own advisory of March 2026 already recommends that banks notify affected customers. We have sent a representation to SBI, marking copies to the RBI and CERT-In, asking that every affected customer be informed without delay. # Background On 21 October 2026, SBI filed a disclosure with the BSE and the National Stock Exchange under Regulation 30 of the SEBI (Listing Obligations and Disclosure Requirements) Regulations, 2015, titled "Incident involving Data Loss". It states that on 16 October the bank received communications from its threat intelligence service provider, the Defence Cyber Agency and CERT-In about the suspected exposure of customer data on the dark web. A preliminary analysis of about 3.75 lakh records found there identified 3,897 customer records containing personally identifiable information. These reportedly include registered mobile numbers, dates of birth, names, gender, email addresses, residential addresses, branch and CIF identifiers, lead IDs, and metadata linked to loan and lead records and other related files. The bank says it is still to establish whether the data is authentic and complete, where it came from and how far the exposure extends. It has activated its cyber incident response protocols and engaged an independent CERT-In empanelled agency to investigate. The filing adds that the incident has no material impact on SBI's core business operations, financial performance or business continuity. The leak was public before SBI said anything about it. On 16 October, the cyber security monitoring account CyberPulse56 posted on X that a threat actor calling itself "Siriusim" claimed to have released 3.75 lakh rows of data in CSV format and 2,722 PDF documents linked to SBI. The dataset was said to include personal customer information, loan applications, supporting documents and account opening applications. On 19 October, India Today Tech reported that SBI had not addressed the claim. The bank's filing came two days later. SBI is not alone. In July 2026, Bank of Baroda began a forensic investigation after a compromised employee email account allowed unauthorised access to its data. # Analysis # A disclosure written for shareholders A Regulation 30 filing exists to keep the market informed, and SBI's filing does that. It tells the exchanges that the bank's business is unaffected. What it does not do is tell the 3,897 customers whose records the bank has itself identified that their mobile numbers, dates of birth and home addresses are on the dark web. We looked for a customer notice, a press release or an advisory from SBI and found none. If SBI has written to these customers, it should say so publicly. If it has not, it should do so today. This matters because of how banking fraud works in India. A caller who knows your name, date of birth, branch, CIF number and the loan you applied for will sound like an official of your bank. The standard advice never to share an OTP assumes that a customer can tell a fraudster apart from the bank. Leaked data erodes that ability, and only notice from the bank lets the customer know to be on guard. # What the filing leaves out The filing accounts for 3,897 of about 3.75 lakh records. It does not say what the remaining records contain or whom they concern. It refers to "other related files" but does not address the 2,722 PDF documents the threat actor claims to have released. Loan and account opening applications ordinarily carry copies of identity and address documents. If these documents are genuine, the number of people affected may be far higher than 3,897. The filing also does not say how the data left the bank. The presence of lead IDs and loan lead metadata raises the question whether it passed through the lead management side of lending, where vendors and direct selling agents routinely handle customer data. Five days passed between the alerts and the filing. # A law that is not yet in force Section 8(6) of the Digital Personal Data Protection Act, 2023 requires a Data Fiduciary to inform the Data Protection Board and each affected Data Principal of a personal data breach. Rule 7 of the DPDP Rules, 2025 sets out how. Parliament passed the Act in August 2023, but under the staggered commencement notified by the Union Government, these provisions take effect only in May 2027. In January 2026, MeitY floated a proposal to shorten this window, but no amendment has been notified. Until then, the obligations in force run to regulators. The CERT-In Directions of 28 April 2022 require reporting of incidents to CERT-In within six hours. The RBI's cyber security framework for banks requires an initial report to the RBI within two to six hours. A bank can comply with every one of these and still leave its customers in the dark. # The RBI has already said what banks should do On 25 March 2026, the RBI's Department of Supervision issued Advisory No. 3/2026 on Best Practices relating to Customer Data Protection to the entities it supervises. Among the practices it records for incident response is notifying affected customers through SMS, email, app alerts, calls and website updates, with guidance on remedial steps and helpline support, built into the bank's cyber crisis management plan. The advisory is not binding. Even so, SBI's filing does not show that the bank has met the standard its own regulator has set out. A public sector bank is also bound by the right to informational privacy recognised by the Supreme Court in *Justice K.S. Puttaswamy (Retd.) v. Union of India* (2017). Telling people that their data has been exposed is the least that right requires. # Action We have sent a representation to the Chairman of SBI, marking copies to the Governor of the Reserve Bank of India and the Director General of CERT-In. We have asked SBI to: 1. Inform every affected customer directly, by SMS, email and letter, in English, Hindi and the language of their home branch, explaining what data was exposed and what they should do. 2. Set up a helpline and an online facility for customers to check whether their data is part of the exposed set. 3. State what the 3.75 lakh records and 2,722 documents contain, how many customers they concern, and whether they include Aadhaar, PAN or passport copies. 4. Disclose how the data left the bank once the investigation concludes, including whether a vendor or direct selling agent was involved, and publish a summary of the investigating agency's findings. 5. Confirm that customers who lose money because of this breach will be compensated under the RBI's rules on limiting customer liability. 6. Say whether it has followed the RBI's Advisory No. 3/2026, and if not, why. We have asked the RBI to make customer notification of data breaches a binding requirement for all regulated entities, pending the commencement of Section 8(6) of the DPDP Act. We have asked CERT-In to state what action it has taken and to issue a public advisory on the fraud that may follow. We will update this post when we receive a response. If you bank with SBI, treat any call, SMS, email or WhatsApp message that quotes your personal or loan details with care. SBI says it never asks for your OTP, user ID, password or PIN. Report any unauthorised transaction to SBI on 1800 1111 09 or unauthorisedtransaction@sbi.co.in, and to the national cyber crime helpline on 1930 or at cybercrime.gov.in. You can also write to SBI and ask whether your data is part of the exposed set. # Important documents 1. SBI's disclosure under Regulation 30 of the SEBI (LODR) Regulations, 2015, "Incident involving Data Loss", dated 21 October 2026 \[[link](https://www.bseindia.com/xml-data/corpfiling/AttachLive/e16e3a1a-ee15-4971-977c-5f9f6aef1fb9.pdf?ref=static.internetfreedom.in)\] 2. IFF's representation to the Chairman, SBI, with copies to the RBI and CERT-In, dated 21 October 2026 \[[link](https://drive.google.com/file/d/1VxJnEy_322w4sASeftO8dySnEngOnt30/view?usp=sharing&ref=static.internetfreedom.in)\] 3. RBI Advisory No. 3/2026 on Best Practices relating to Customer Data Protection, dated 25 March 2026 \[[link](https://www.medianama.com/wp-content/uploads/2026/04/1774846217712.pdf?ref=static.internetfreedom.in)\] 4. CERT-In Directions under Section 70B(6) of the Information Technology Act, 2000, dated 28 April 2022 \[[link](https://www.cert-in.org.in/PDF/CERT-In_Directions_70B_28.04.2022.pdf?ref=static.internetfreedom.in)\] 5. IBTimes India,[ "SBI data breach claim: Hacker group alleges access to 3.75 lakh records, 2,722 documents"](https://www.ibtimes.co.in/sbi-data-breach-claim-hacker-group-alleges-access-3-75-lakh-records-2722-documents-907722?ref=static.internetfreedom.in), 21 October 2026 6. Business Today,[ "SBI data breach? Hacker claims leak of 3.75 lakh records, over 2,700 documents"](https://www.businesstoday.in/amp/india/story/sbi-data-breach-hacker-claims-leak-of-3-75-lakh-records-over-2700-documents-562638-2026-10-20?ref=static.internetfreedom.in), 20 October 2026 7. Cyber Security News,[ "SBI Data Breach Claim: Hackers Allegedly Claim Access to 3.75 Lakh Users' Database"](https://cybersecuritynews.com/sbi-data-breach-claim/?ref=static.internetfreedom.in), 20 October 2026 8. The Asian Banker,[ "India's Bank of Baroda data breach exposes customer records after employee email compromise"](https://theasianbanker.com/updates-and-articles/india-s-bank-of-baroda-data-breach-exposes-customer-records-after-employee-email-compromise?ref=static.internetfreedom.in) [Donate Now](https://static.internetfreedom.in/donate)
document fetched 2026-10-22 00:28 · canonical https://reddit.com/r/india/comments/1xbh1l2/sbi_told_investors_its_data_breach_doesnt_matter