SBI Data Leak: Why Your Staff Should Expect Smarter Scam Calls

SBI data leak October 2026: steps for Indian firms

On 21 October 2026, State Bank of India told the stock exchanges about an incident involving the loss of certain data. The bank had received alerts on 16 October from a threat intelligence provider, CERT-In and the Defence Cyber Agency. Even if your company does not bank with SBI, your team and your customers may be the next target of very convincing scam calls.

What we know so far

  • About 3.75 lakh records were examined on the dark web, and 3,897 of them held customer personal information. SBI calls this count preliminary.
  • The data includes names, mobile numbers, dates of birth, email and home addresses, branch and customer identifiers, lead IDs and loan details.
  • SBI has not reported account numbers, balances, passwords, OTPs, card details, PAN or Aadhaar as exposed.
  • The cause is still unknown. SBI has started incident response and brought in a CERT-In-empanelled security firm.

Why this matters for any business

A caller who already knows a person's name, address and loan details sounds real. That trust is then used to ask for an OTP, a remote access app or a payment. A few simple habits close most of this gap:

  • Warn staff this week and share a clear reporting route, such as the 1930 helpline or cybercrime.gov.in.
  • Require a call-back on a known number before any payment or bank detail change.
  • Map where your own customer and lead data sits, and review partner access to it.
  • Test your incident response, including CERT-In's 6-hour reporting window.

Read the full guide with all the steps here: SBI Data Leak: What Indian Firms Should Do This Week

Published by Affix Center, a Mumbai-based IT services company that helps organisations with cyber security services and incident readiness.

Comments

Post a Comment

Popular posts from this blog

Self-Hosted GitLab? CVE-2026-97229 Is Being Exploited, Check Your Version

Image
If your team runs its own GitLab server, this one needs attention this week. CVE-2026-97229 is a CVSS 10.0 integer overflow in the regular expression compiler used by GitLab CI/CD. A crafted regex in a CI/CD configuration can let an attacker run code on the server. GitLab shipped fixes on 12 October 2026, and CISA added the flaw to its Known Exploited Vulnerabilities catalogue on 29 October 2026. Which versions are affected 19.2 branch: fixed in 19.2.8 19.3 branch: fixed in 19.3.5 19.4 branch: fixed in 19.4.2 GitLab.com and GitLab Dedicated are already patched The root cause sits in Onigmo, the regex engine inside Ruby, so source or custom builds with their own Ruby may need a separate Ruby update. A short action list List every self-managed GitLab instance, including test and forgotten ones Upgrade each one to the fixed version for its branch Turn off open sign-up and limit who can push to public projects until patched Review recent .gitlab-ci.yml changes, unknown users and o...
Read more

Hiring a Website Developer? Six Warning Signs to Spot Before You Sign

Image
Many business websites get built twice. The first vendor wins on price, and a few months later the site is slow on mobile, the contact form stops working, and nobody can reach the developer. Most of this can be avoided with the right questions before signing. Warning signs in a website quote A fixed price given before anyone asks about content, integrations or users No live examples, or examples that no longer load Reluctance to register the domain and hosting in your company's name No mention of testing, backups or updates Pressure to sign fast with a "this month only" discount A launch plan with no redirects for old URLs, which can wipe out search traffic What to ask for instead An itemised proposal: pages, templates, features, integrations, revisions, testing, hosting and support A meeting with the project manager and lead developer, not only sales Written ownership of domain, hosting, source code, design files and content A short paid discovery phase that p...
Read more

Laravel Projects That Need a Rebuild After 18 Months: Five Causes and How to Avoid Them

Image
A common story: a business picks a Laravel vendor for a low quote, and about eighteen months later the app is slow, small changes break other features, and the next vendor says it must be rebuilt. Laravel is rarely the problem. The way the vendor was chosen usually is. Five causes behind costly rebuilds Business rules stuffed into controllers, so a new GST field touches many files No automated tests, even though Laravel supports PHPUnit and Pest The N+1 query problem: a list of 100 orders running 101 queries Security left to chance: debug mode on in production, or secrets stored in the code repository The vendor, not the client, holding the repository, servers and domain Version support matters too Per the official Laravel documentation, each major release gets bug fixes for 18 months and security fixes for 2 years. Laravel 13 came out in March 2026, and security support for Laravel 12 runs until February 2027. Plan upgrades in your maintenance contract. Before you sign Have an ...
Read more