SBI Data Leak: 3,897 Confirmed Records, a 375,000-Row Claim and an FIR Filed a Month Later
Security / news
SBI Data Leak: 3,897 Confirmed Records, a 375,000-Row Claim and an FIR Filed a Month Later
State Bank of India confirmed personal data in 3,897 records out of roughly 375,000 circulating. Police registered a complaint on November 12.

State Bank of India has confirmed personal data in 3,897 customer records from a set of roughly 375,000 (3.75 lakh) rows that a group called Siriusim posted to a dark web forum. Police registered a First Information Report on November 12, 2026, about a month after the alleged access, against unidentified persons. The number SBI has confirmed is about one percent of the number the group claimed, and the two are not the same measure.
The account below comes from Inc42, which updated its report on November 16 and cites the police complaint and SBI's exchange filing, and from the Free Press Journal. The Terminal did not obtain the filing or the complaint itself.
Timeline
| Date | Event |
|---|---|
| Oct. 10 to 15 | Alleged access to a server at SBI's Global IT Centre in CBD-Belapur, per the complaint as reported by Inc42 |
| Oct. 16 | SBI says it received alerts from its threat intelligence provider, the Defence Cyber Agency and CERT-In; the X account CyberPulse56 flags the claim |
| Oct. 21 | SBI's exchange filing reported |
| Nov. 12 | FIR registered, as reported by The Times of India |
The FIR cites Bharatiya Nyaya Sanhita provisions on theft and criminal conspiracy, plus sections of the Information Technology Act. SBI says it removed the data from the dark web and that it has not been misused. Neither claim has been independently checked.

Three numbers that do not match
The group says it holds more than 375,000 CSV rows and 2,722 PDF files, per the Free Press Journal. The police complaint cites about 375,000 records, 2,721 PDFs and about 32 CSV files, per Inc42. SBI's preliminary review found personal information in 3,897 records.
- Rows claimed by Siriusim375K records
- SBI-confirmed records with personal data3897 records
Source: Inc42 and Free Press Journal reporting of the police complaint and SBI filing, accessed 2026-11-16
Inc42 states that the number of records examined does not establish that 375,000 customers were affected. A single customer can appear in several rows, and the rows include lead and loan metadata that is not personal data. The 3,897 figure is also a count of records, not people.
What data classes are involved
SBI's filing lists mobile numbers, dates of birth, email addresses, residential addresses, branch details, customer information file (CIF) identifiers, lead IDs and metadata tied to loan and lead records. The complaint adds loan application records and account-opening forms.
The group's own claim goes further. The Free Press Journal reports it says the material includes KYC records and Aadhaar numbers, and that it shared four sample records. SBI's filing, as reported, does not list Aadhaar numbers. That gap is unresolved. The Free Press Journal found the phone numbers in the public samples were valid, which shows the samples are real. It does not show how the data was obtained or when.
What is not known
Neither report says how the data left SBI, whether the records are recent, or whether they come from an earlier incident. The Free Press Journal says Siriusim has no known prior history. SBI has not attributed the exposure to the group, and Inc42 could not independently verify the claims first publicised by CyberPulse56.
SBI has engaged an independent cybersecurity agency empanelled by CERT-In to verify the authenticity and completeness of the data and to find the source of the exposure. It says core banking and business functions are operating normally.
Anyone with an SBI loan application or account-opening form from the affected period should expect phishing calls that quote real personal details. Treat any call citing a CIF number or loan lead as unverified until it is checked through the branch. Related reading on personal data: the Penlink location-data report, and the ThisBash desktop-agent analysis.
Sources
More in Security
- 01Ruby2Shell (CVE-2026-132825): Ruby Is Fixed, but GitLab, GitHub Enterprise and Chatwoot Are Listed Without a PatchA one-byte heap overflow in Ruby's case conversion carries a 7.4 local score, while the researchers say stock Rails is remotely reachable and will publish a proof of concept Nov. 25.
- 02NPCI Wants Overlay Permissions Restricted on Sideloaded Apps; Google's 2024 India Block List Omits ThemThe reported ask covers accessibility, device admin and display-over-apps. The pilot Google announced on Oct. 3, 2024 named four other permissions.
- 03CVE-2026-99312: A KVM Nested-AMD Bug Scores 8.8, With Fixes Listed for Three Kernel BranchesThe Linux CNA's scoring notes describe a freed page-table root that a guest can aim at; the commit message describes only a stale MMU context.
- 04CISA's Nov. 18 KEV Additions Include Apache Axis 1.x, Which Has No Fix, With a Nov. 21 DeadlineThree of four new entries carry a three-day federal deadline; LiteLLM's advisory names two different patched versions.