DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
State AGConfirmed9 filings · 9 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 9 filings

TaskRabbit, Inc. — April 2018 breach

Clustered 9 filings across 9 jurisdictions · filing window May 9, 2018 → May 18, 2018. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

9

Affected · reported

3,030,925

First → last filing

May 9, 2018 → May 18, 2018

Merge confidence

100%

incident inc_d0b784d574964ce6 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. The filings describe unauthorized access. Intrusion Apr 11, 2018–Apr 18, 2018, discovered Apr 12, 2018 — the first regulatory filing landed 27 days later. 3,030,925 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 2 more. Notifications rolled out on a 9-day schedule across 9 filings beginning May 9, 2018. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
27days

Discovered → first regulatory filing

Discovery variance
1days

Range of discovered_at dates across filings

Filing span
9days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksOregon✓ OR AG ≤45dHawaii✓ HI CRA notice dueSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

authenticationidentity_government

Incident timeline

Apr 11, 2018breach begins
Apr 12, 2018discovered · members disagree
notification delay · 27 days
May 9, 2018first filing
May 18, 2018most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. MAY 9MT AGMT AG noticefirst filing · 3,908 MT residentsday 0
  2. MAY 9WA AGWA AG notice77,618 WA residentsday 0
  3. MAY 14NH AGNH AG notice11,199 NH residents+5d
  4. MAY 14DE AGDE AG noticeno count stated+5d
  5. MAY 14CA AGCA AG noticeno count stated+5d
  6. MAY 16OR AGOR AG noticestates nationwide total 3,030,925+7d
  7. MAY 17MA AGMA AG notice120,391 MA residents+8d
  8. MAY 18HI AGHI AG notice4,062 HI residents+9d
  9. MAY 18SC AGSC AG noticemost recent · 19,019 SC residents+9d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 11, 2018
CA AG
Discovered
Apr 12, 2018MT AG + WA AG + NH AG +3Apr 13, 2018OR AGfilings disagree on discovery
Data types
Authentication · Credentials · Financial account · Identity (basic) · Government ID
MT AG + WA AG + NH AG +4
Attack vector
Unauthorized Access
MT AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

3,030,925

Sum of filed state slices

236,197· 7.8% of stated

92% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US3,030,925
MA120,391
WA77,618
SC19,019
NH11,199
HI4,062
MT3,908

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing9 members

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

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Jun 12, 2026 · at least one link edge was human-adjudicated
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

9 days

Cadence

~1 / 1.1d

vs. multi-state median

1.5× slower

About this clustering

DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.