Threat Atlas IndiaReporting rules

Story ·

AU Bank’s vehicle loan leak: three numbers that don’t mean what you think

On 2 November 2026, AU Small Finance Bank told the stock exchanges that a platform it uses to onboard vehicle loan customers may have leaked their data. Since then the numbers in circulation have grown from “some” to 28.5 lakh to a billion. Only one of those came from the bank.

By Threat Atlas India · Published 8 November 2026 · This story will be updated as the investigation reports.

The short version

  • Confirmed by the bank: it became aware on 29 October of a “potential data leakage incident” on a third-party Software-as-a-Service platform used to onboard vehicle loan customers.
  • How many: the bank says only that the incident “may have resulted in data leakage of some of the Bank’s vehicle loan customers”. That is the only quantity it has given.
  • The 28.5 lakh figure is from the same filing, but it counts customers onboarded through the platform. It is the size of the pool, not the number affected.
  • Also confirmed: the matter was reported to the Reserve Bank of India and CERT-In. Banks rarely say this out loud.
  • Claimed by a seller, not confirmed: 1.2 TB of data including 938 million core banking transaction records, offered for $8,500 on 6 November.
  • The risk to customers now: convincing scam calls, not direct theft from accounts.

Claimed versus confirmed

Two descriptions of the same incident are circulating. They do not describe the same thing, and they are not equally sourced.

Claimed by a seller 938 million core banking transaction records, part of a claimed 1.2 TB haul also said to hold 2.28 million customer accounts, 1.92 million account numbers and 3.85 million KYC records with PAN and Aadhaar numbers. Advertised on a forum for $8,500 and surfaced publicly on 6 November. Unverified.
Confirmed by the bank “some” vehicle loan customers may have had data leaked, from information collected at the time of loan onboarding, held on a platform run by an outside vendor. The bank says its own systems are unaffected and services are running normally.

A loan onboarding system holds application details. It does not hold a bank’s transaction ledger. If the seller’s 938 million core banking records are real, they did not come from the platform the bank has described. That would mean either the seller is inflating, or the bank has not yet found everything. Both are possible. Neither is established.

The number that isn’t what it looks like

Much of the coverage has reported that the leak “covers” or “affects” 28.5 lakh customers. That number does appear in the filing. Here is the sentence it appears in, in full:

What the filing says

“Based on the preliminary findings so far, the incident may have resulted in data leakage of some of the Bank’s vehicle loan customers. The Bank is undertaking a detailed internal and external forensic investigation… to ascertain the nature and extent of potential data leakage (there are ~28.5 lacs vehicle loan customers onboarded through this platform).”AU Small Finance Bank, Ref. AUSFB/SEC/2026-27/287, 2 November 2026

What that means
  • Affected: “some”, number unknown
  • 28.5 lakh: everyone ever onboarded through the platform
  • Relationship: the second is the ceiling, not the count

The bank put the figure in brackets to give the investigation’s scope a size. A denominator became a casualty figure somewhere between the filing and the headline.

This matters beyond pedantry. If you are one of the 28.5 lakh, you now know you are in the pool being investigated. You do not know, and neither does the bank yet, whether your record left the building.

How it unfolded

  1. The claim surfaces, and the bank learns of it. A group calling itself ScarlettGroup claims to hold the bank’s customer records. The filing gives the same date for when the bank “became aware” of a potential leak.
  2. A statement to the press. The bank tells reporters it is investigating a potential leak involving a third-party SaaS platform, and that its “own systems remain unaffected and all banking services are operating normally”.
  3. The exchanges ask; the bank answers. NSE and BSE seek a clarification on a media report titled “AU Bank probes potential data leak”. The bank replies the same day, filed at 11:53 pm, signed by its company secretary.
  4. The claim gets much bigger. A listing advertising 1.2 TB and more than a billion records for $8,500 is circulated by a threat-monitoring account. The bank has not commented on it.
  5. Forensic investigation under way, internal and external, with what the bank calls “leading cyber security firms”. No cause named, no count given, no further filing.

Read the filing like an analyst

It is a reply, not an announcement

The subject line is “Reply to clarification sought by Stock Exchanges”. The bank knew on 29 October and told investors on 2 November, after the exchanges asked, following a news report. Under SEBI’s listing rules a listed company must disclose a material event within 24 hours, but the company decides what is material, and this filing states the incident has no material impact on operations, financial performance or business continuity.

“Our systems are unaffected” is narrower than it sounds

It is a statement about the bank’s own infrastructure. The data in question was sitting with a vendor, which is precisely why the sentence can be true while customers’ details are still gone. Under the DPDP Act, when it is enforced, outsourcing the system will not outsource the responsibility: the bank remains the data fiduciary for data a processor handles on its behalf.

The regulator line is the unusual part

“The matter has been reported to regulatory authorities including the Reserve Bank of India and CERT-In.” Most Indian breach disclosures never confirm this. It is a bank saying on the record that the reporting clocks ran. It does not say when they ran, which is the part that would tell you whether the six-hour deadlines were met.

What the vendor is, and isn’t

The filing calls it “a reputed global third-party vendor” and does not name it. Press reports, citing the bank, have named the platform’s host. No evidence has been published that the vendor’s own platform was compromised, and this site does not name an organisation on an unconfirmed claim, vendors included.

What the rules required

One incident, several clocks, all of them starting when the organisation notices.

6 hoursto report to CERT-In, from noticing an incident or being told about it. The bank confirms it reported; it has not said when.CERT-In Directions, April 2022
6 hoursto report to the RBI, from detection. The bank confirms the RBI was told.RBI cybersecurity directions for commercial banks, 31 July 2026
24 hoursfor a listed company to disclose a material event to the exchanges. Materiality is the company’s own judgement; this filing came on day four, in reply to a query.SEBI Listing Regulations, Regulation 30
Not yetA duty to tell each affected person and the Data Protection Board exists in law, but only starts on 13 May 2027.DPDP Act 2023, s. 8(6), and DPDP Rules 2025, Rule 7

That last gap is why a vehicle loan customer reading this has no right, today, to be told whether their record is among the “some”. Every deadline is laid out on the four clocks.

If you have a vehicle loan with AU Bank: what to do now

  1. Expect the call to sound legitimate. Loan onboarding data is exactly what makes a fake call convincing: the caller can quote your loan, your vehicle and your address because the paperwork said so.
  2. Never share an OTP, PIN, CVV or password, and never approve a payment request you did not start. No genuine loan servicing, insurance renewal or “NOC release” needs any of them.
  3. Treat PAN and Aadhaar as exposed if the seller’s claims hold. You cannot change either, but you can lock your Aadhaar biometrics on the UIDAI site and check your credit report for loans you did not take.
  4. Do not click links in SMS or WhatsApp about your loan account, however specific they are. Open the bank’s app yourself.
  5. Lost money? Act within minutes. Call 1930 or report at cybercrime.gov.in. The faster it is reported, the better the chance of freezing the transfer.

What we don’t know yet

  • How many customers are actually affected, out of the 28.5 lakh in the pool.
  • Which fields left: the bank says “information obtained at the time of loan onboarding” without listing it.
  • Whether the seller’s 1.2 TB is genuine, partly genuine, or recycled from elsewhere.
  • How the data was taken, and from whose account or integration.
  • When CERT-In and the RBI were told, and whether that was inside six hours.
  • Whether affected customers will be contacted, which no law currently requires.

This story sticks to what the bank has filed and what named sources have reported. Claims by sellers are labelled as claims throughout.

Sources

Threat Atlas India names an organisation only when it has publicly confirmed an incident itself, as AU Small Finance Bank did in its stock exchange filing. Organisations that appear only in criminals’ claims are never named, and neither are vendors. Spotted an error? Write to [email protected].

More stories

All stories →