Uber Alerts About Potential Exposure of Almost 150,000 Users Following Third‑Party Credential Theft
In a set of breach‑notification letters, Uber announced that nearly 150,000 people could be impacted by a security incident that stemmed from a third‑party service provider. According to the firm, the breach came to light when the provider warned Uber on October 9 that internal credentials had been taken and then employed to infiltrate Uber’s systems.
The notice explained that the stolen credentials were part of Uber’s internal infrastructure and were used by unidentified parties to sign into the rideshare platform. Although Uber has not specified which data were viewed, it stressed that the incident concerned authentication information, not the direct disclosure of customers’ payment details.
In response, Uber launched an immediate probe together with outside cybersecurity specialists and law‑enforcement bodies. It is resetting passwords for the impacted accounts, tightening multi‑factor authentication standards, and watching for any suspicious behavior. Uber further committed to updating regulators and the affected users as the inquiry moves forward.
The event highlights the escalating danger that third‑party vendors present within the technology landscape. Analysts observe that numerous high‑profile breaches lately have originated from compromised supplier credentials, urging companies to revisit supply‑chain security measures. Uber, which has earlier disclosed data‑security problems concerning driver and rider data, is now under intensified scrutiny regarding its data‑protection practices.
U.S. and foreign regulators could demand formal breach notices under privacy laws like the California Consumer Privacy Act and the EU’s GDPR, based on where the impacted users reside. Uber’s forthcoming actions are expected to involve comprehensive reports to authorities, provision of credit‑monitoring services where needed, and the deployment of further safeguards to lessen dependence on external authentication routes.
Comments (0)
Be the first to comment.
Join the discussion