Tokenpost SBI Investigates Dark Web Data Exposure of Customer Records
Article Content
- •SBI is investigating a data exposure incident involving 3,897 customer records on the dark web.
- •The bank's preliminary review indicates the data may originate from loan-sourcing or lead-management systems.
- •SBI has established a cybersecurity centre, CyRIS, to bolster its defenses against emerging threats.
The State Bank of India (SBI) is investigating the suspected exposure of customer data on the dark web, with 3,897 records containing personally identifiable information identified among approximately 375,000 records. The bank received alerts from its threat intelligence service provider, the Defence Cyber Agency, and CERT-In on October 16, 2026. Preliminary findings do not confirm that all records belong to SBI customers, and the investigation is ongoing to determine the authenticity and source of the data. SBI has activated its cyber incident response protocols and engaged an independent cybersecurity agency. The exposed data includes names, birth dates, and loan-related metadata, suggesting a potential link to loan-sourcing or lead-management systems rather than core banking systems. SBI has launched a cybersecurity centre, CyRIS, to enhance its digital security capabilities in response to this incident.
Ask AI about this cluster
Answers cite the sources they use
Timeline
More articles in this cluster (3)
Following this threat?
Track State Bank Of India in your own feed — you're alerted when they show up in new reporting, leak sites or exploitation.
Free account · no card needed
Common questions
What customer data was exposed?
Is there evidence of exploitation?
What actions is SBI taking in response?
Continue Reading
Brotli Decoder Vulnerability Patched Across Multiple Linux Distributions A vulnerability, CVE-2026-111497, affecting the Brotli decoder has been patched in various Linux distributions, including Fedora 44 and Oracle Linux 10. The flaw allows for an out-of-bounds write, which could potentially enable attackers to execute arbitrary code. The vulnerability was published on October 22, 2026…