UnknownGovernment IDHigh

UBER TECHNOLOGIES, INC.

bd_103b55f80b2fd5c6 · schema v1 · pii pii-v2

Severity

High

Discovered

—

Filed

Nov 28, 2017

To disclose

—

Affected

24,149state residents only

Linked

6 filings

Confidence

95%

Full breach record for UBER TECHNOLOGIES, INC. →10 incidents on file

Uber Technologies, Inc. reported a data breach to the Massachusetts Office of Consumer Affairs and Business Regulation. The breach was reported on 2017-11-28. 24,149 Massachusetts residents were affected. The report records the breach type as electronic.

J jump to incidentP pin to compareR raw source

Incident timeline — partial

? — ?

Breach window unknown

Nov 28, 2017

Filed

—

Corroborated · see linked filings

Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.

This filing is one of 6 about the same incident.View merged incident

Linked disclosures

Why this link?

Regulatory filings (5) · sorted by filing gap

New Hampshire State AGbd_5aac63ae95779a492017-11-21 · +7dVerified
Montana State AGbd_74ccb250c0dca8c32017-11-21 · +7dVerified
Oregon State AGbd_8cb0530a7d7281d12017-11-21 · +7dCandidate
Washington State AGbd_cb676ca7c713e68b2017-11-21 · +7dVerified

Show 1 more filing ↓up to 7d gap

California State AGbd_dfe6822f4d0881262017-11-21 · +7dVerified

Name: UBER TECHNOLOGIES, INC.
norm: uber technologies

Name: UBER TECHNOLOGIES, INC.
norm: uber technologies

Discovered: —
Materiality determined: —
Notification sent: —
Affected individuals: 24,149state-resident count only
Data types: Government ID
Data elements: Driver's licence number
Stated not affected: Social Security numberFinancial account numberPayment card number
The filing states these were not involved. Categories absent from both lists were not addressed either way.
Attack vector: Unknown
Threat actor: External

Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 6 filings · 6 states

View merged incident ↗

New Hampshire State AGNov 21 · first

Montana State AGNov 21 · first

Oregon State AGNov 21 · first

Washington State AGNov 21 · first

California State AGNov 21 · first

Massachusetts State AG+7d · this page

Pattern: first filing Nov 21 (NH), last Nov 28 (MA) — a 7-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source URL: https://www.mass.gov/doc/data-breach-report-2017/download
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Nov 28, 2017
Raw hash: 3227b1bf86954c6aedf903ea5a00016b10f2d444392acad406ca2bd7bf33a1d8

Linked disclosures

Regulatory filings (5) · sorted by filing gap

Reporting entityUBER TECHNOLOGIES, INC.

Victim entityUBER TECHNOLOGIES, INC.

IncidentUnknown

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancewww.mass.gov