Skip to content
cisonews.net

Incident · 8-K Item 1.05

Zoomcar data breach: personal data of about 8.4 million users accessed

Compiled from public records. Updated 2026-11-12. By the cisonews.net Desk.

Zoomcar Holdings, Inc. told the SEC in an Item 1.05 Form 8-K dated June 13, 2025 that an unauthorized third party accessed a limited dataset of personal information tied to a subset of approximately 8.4 million users. The company identified the incident on June 9, 2025, and the data involved was names, phone numbers, car registration numbers, personal addresses and email addresses.

Entries like this one, in Wednesday’s docket

Wednesdays

Unsubscribe any time.

The Zoomcar data breach is the second large one at the Bengaluru car-sharing company: a 2018 breach of about 3.6 million customer records was sold on a dark web market in 2020. Zoomcar has not said how many of the 8.4 million users were actually affected, and no notice to individual users is on record.

Who is Zoomcar?

Zoomcar runs a marketplace where people rent out their cars, by the month, week, day or hour. TechCrunch, citing the company's investor relations site, reported that it operates in 99 cities with more than 25,000 cars and over 10 million users, in India, Egypt, Indonesia and Vietnam. It is listed in the United States, which is why the first report of the breach was a Form 8-K filed with the SEC rather than a letter to a state regulator.

What happened and when

Zoomcar says it identified a cybersecurity incident on June 9, 2025. It became aware after some employees received messages from a threat actor who claimed to have reached company data. The company says it then put its incident response plan into action.

What information was involved

The findings described are preliminary. The filing says the dataset was limited and covered a subset of the roughly 8.4 million users, so the number of people actually affected is not given. The listed items are names, phone numbers, car registration numbers, personal addresses and email addresses. Zoomcar states that it has no evidence that financial information, plaintext passwords or other sensitive identifiers were compromised.

Response and effect on the business

The company describes added safeguards across its cloud and internal network, increased monitoring and a review of access controls. It is also working with third-party cybersecurity experts on the investigation. Regulators and law enforcement have been notified, according to the filing.

On operations, Zoomcar reports no material disruption so far. It adds that it is still assessing legal, financial and reputational effects, along with remediation costs.

What Zoomcar's annual reports say since

Zoomcar has not amended the 8-K, but its two annual reports since the incident show how its account moved. The 10-K filed on June 30, 2025, seventeen days after the 8-K, repeated the 8.4 million figure and said the review was still open. The 10-K filed on July 14, 2026 says that work is done: Zoomcar reports it has completed an external security assessment and strengthened its internal controls.

The 2026 report also says that, apart from anything noted elsewhere in it, Zoomcar does not believe any cybersecurity threat, including previous incidents, has materially affected the company or is reasonably likely to. It still gives no final count of affected users and no cost.

FilingDateWhat it adds
Form 8-K, Item 1.05June 13, 2025First report; a subset of about 8.4 million users
Form 10-K, fiscal 2025June 30, 2025Same facts; impacts still being evaluated
Form 10-K, fiscal 2026July 14, 2026External security assessment completed; internal controls enhanced

Did Zoomcar notify the affected users?

No notice to users is on record. When the breach was reported, TechCrunch wrote that Zoomcar had not said whether it had told the affected customers or whether it knew anything about the hacker, and that the company had not answered its questions. The Record also said the company did not respond to requests for comment. None of the three SEC filings listed above mentions letters or emails to users.

For a user, the practical risk comes from the data types named: a phone number, an address and a car registration number are enough for a convincing scam call or message that claims to be from Zoomcar about a booking. Zoomcar says no plaintext passwords were involved, so the filing gives no reason to change a password, though anyone who reused a password from the 2018 breach should change it.

Has Zoomcar had a data breach before?

Yes. The Record reported that Zoomcar had a large breach in July 2018 that exposed the names, IP addresses, passwords and phone numbers of 3.6 million customers, and that the data was sold on a dark web marketplace in 2020. Have I Been Pwned, which lets people check whether their email address is in a published breach, holds that 2018 data set and describes the passwords as stored as bcrypt hashes. The 2025 filing does not refer to the earlier breach.

BreachWhenWhat was takenHow manyRecord
First breachJuly 2018; data sold in 2020Names, email and IP addresses, phone numbers, hashed passwordsAbout 3.6 million customersThe Record; Have I Been Pwned
Second breachFound June 9, 2025Names, phone numbers, car registration numbers, addresses, email addressesA subset of about 8.4 million usersZoomcar Form 8-K, June 13, 2025

The Record placed the 2025 breach among attacks on car rental companies in the same year, including Hertz, whose notices traced back to the Cleo file transfer flaw.

What the filing leaves open

The filing does not say how the third party gained access or whether the threat actor's claims were accurate beyond the dataset described. It gives no dollar estimate of costs, no exact count of affected users, and no description of notices to individuals. It also does not say whether any amendment will follow, and none is on record here.

How this disclosure's timing compares

Zoomcar Holdings disclosed 4 days after the discovery date its filing gives. Across the 46 other filings under 8-K Item 1.05 on cisonews.net that date discovery to the day, the median gap is 6 days.

The rule behind an Item 1.05 filing

Form 8-K Item 1.05 is where a public company reports a cybersecurity incident it has determined to be material. Under the rule the SEC adopted on July 26, 2023, the filing is generally due four business days after the company determines that the incident is material. Source: U.S. Securities and Exchange Commission, press release 2023-139. The guide What is SEC Form 8-K Item 1.05, and what counts as a disclosed cyber incident? reads the rule in full, and the glossary defines Form 8-K Item 1.05.

Other transportation & logistics incidents on cisonews.net

  • Uber Technologies, Inc., Breach notice, first disclosed November 10, 2026
  • Caltrain, Breach notice, first disclosed November 3, 2026
  • STS Aviation Group, Breach notice, first disclosed October 19, 2026; 54,027 affected in total (Indiana Attorney General)
  • Preferred Parking Service, LLC, Breach notice, first disclosed August 14, 2026; affected: 72,912 people in total (Indiana AG record)
  • Yellow Corporation, Breach notice, first disclosed June 26, 2026; affected: 258,498 people (Oregon DOJ record)

All transportation & logistics incidents

Sources

  1. 2025-06-13 · AZoomcar Holdings, Inc., Form 8-K (SEC EDGAR), published June 13, 2025
  2. 2025-06-30 · AZoomcar Holdings, Inc., Form 10-K for the fiscal year ended March 31, 2025 (SEC EDGAR), published June 30, 2025
  3. 2026-07-14 · AZoomcar Holdings, Inc., Form 10-K for the fiscal year ended March 31, 2026 (SEC EDGAR), published July 14, 2026
  4. 2025-06-16 · BThe Record from Recorded Future News: 8.4 million people affected by data breach at Indian car share company Zoomcar, published June 16, 2025
  5. 2025-06-16 · BTechCrunch: Car-sharing giant Zoomcar says hacker accessed personal data of 8.4 million users, published June 16, 2025
  6. 2026-11-12 · BHave I Been Pwned, Zoomcar Data Breach (2018), published November 12, 2026
  7. 2023-07-26 · AU.S. Securities and Exchange Commission, press release 2023-139, published July 26, 2023

Tier A: the organization itself (including notices it filed with a state attorney general), a regulator or SEC EDGAR. Tier B: established press. Each fact on this page carries its supporting passage in the page source.

Entries like this one, in Wednesday’s docket

Wednesdays

Unsubscribe any time.