New Delhi: According to State Bank of India, there have been no losses of money. That may be little consolation to those who had their information stolen.
The breach is said to have occurred between 10th and 15th October at the Global IT Centre at SBI’s CBD-Belapur office in Navi Mumbai and 375,000 bank related records were leaked. Presumably, hackers stole application data, 4280 customer records and some confidential files. According to one local report, the information is from SBI’s YONO 2.0 and RAAS applications and the SBI identified the suspicious activity on October 16.
Safe balances, exposed people
A stolen account is the most obvious one when it comes to stolen assets, but it’s not the only one. Details reportedly contained included customer data, loan applications, account opening documents, contact information and addresses. That’s nearly the whole package of what it takes to pull off a scam. A con man who has your name, address and loan history can pretend to be a bank official and give the real information to establish trust. While the data has been deleted, cybersecurity lawyer Prashant Mali has urged customers to be on the lookout for phishing and other scams.
Customers should be skeptical of any calls, SMS or emails that they receive from any entity regarding loans, KYC documentation, or account issues and never provide an OTP to anyone.
Counting the records
There’s a number in the headline that requires some insight. The complaint says it includes approximately 32 CSV documents containing approximately 375,000 records, plus JSON documents and 2,721 PDFs with personal information like loan applications and account-opening forms. Raw records do not equal identifiable customers. The 4,280 customer records and the PDF set contain names and addresses, while a large portion (375,000) of the entries could be application data or logs that do not easily correspond with individual people. No one outside of the bank can say, how many people are actually being exposed, until SBI releases a break down.
The month-long gap
SBI identified the issue on October 16, but had a police complaint on November 12, almost a month later. There could be a simple cause. The banks typically conduct an internal forensic investigation before turning to the police and SBI said there was none in its investigation. Nevertheless, the delay caused any customers targeted during the period to not know about the risk. The CBD-Belapur police have registered a case under provisions of Bharatiya Nyaya Sanhita with regard to theft and criminal conspiracy, in addition to the IT Act.
The third-party question
According to public reports, little is known about how the attackers gained access. The police complaint identifies only unknown individuals associated with a group called Siriusim and it states that it was not enough to show it is the individuals. This raises the question of whether it was a vendor or a connected application or an internal credential. Dozens of outside vendors control large banks, and every connection is a potential weak point. SBI and investigators should indicate whether or not there is any third party involved.
Can data really be “removed”?
SBI said it had pulled the stolen data off the dark web, but not known if it had been accessed by other people or groups. That’s the issue at hand. After a file is uploaded, anyone can copy it in just a few minutes and a takedown merely prevents new copies from being made from that single source. The word “not misused” means “no misuse detected yet”.
Notification and what comes next
If the bank manages to work out whom to call, it’s our minimum that the customers will be notified individually. A general advisory is to exercise caution, whereas a direct message is to modify contact preferences, monitor their messages and be aware of potential fraud. The most at stake is for the customers who have loan files in the data-set.
But the greater concern is: what happens after this incident? Phishing messages can already be created at scale, in any Indian language, by feeding it with leaked information. Defenders will need a quicker detection of abnormal data transfers (data was said to have been pulled out of the bank’s server over approximately six days without being detected by the bank until a month later) and faster disclosure than a month.
Meanwhile, SBI consumers should take a few simple precautions: Regularly check statements for any irregularities, be wary of unsolicited calls that appear to be from SBI, and call the bank or cybercrime helpline, 1930, if anything appears suspicious.


