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

Perkins & Co. — November 2020 breach

Clustered 24 filings across 6 jurisdictions · filing window Mar 11, 2021 → Oct 7, 2022. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

24 filings

States

6

Affected · reported

478,278

First → last filing

Mar 11, 2021 → Oct 7, 2022

Merge confidence

100%

incident inc_f30bade1d8a64bde · merged by human · confidence 100%

Part of the Netgain Networks supply-chain incident (2021) — at least 15 organizations filed notifications naming this third party.
Confirmed breach. Merged as one breach: 24 regulatory filings. Intrusion Nov 8, 2020–Dec 3, 2020, discovered Dec 3, 2020 — the first regulatory filing landed 98 days later (flagged late). 478,278 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 4 more. Notifications rolled out on a 575-day schedule across 24 filings beginning Mar 11, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
98days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
575days

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 clocksWashington✗ WA AG >90dOregon✗ OR AG >45dMaine✗ ME AG >90d · 113dFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Nov 8, 2020breach begins
Dec 3, 2020discovered
notification delay · 98 days
Mar 11, 2021first filing
Oct 7, 2022most 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. MAR 11WA AGWA AG noticefirst filing · 41,871 WA residentsday 0
  2. MAR 11OR AGOR AG noticestates nationwide total 8,440day 0
  3. MAR 23NH AGNH AG notice5 NH residents+12d
  4. MAR 26OR AGOR AG noticestates nationwide total 2,642+15d
  5. MAR 26ME AGME AG noticestates nationwide total 2,642+15d
  6. APR 4OR AGOR AG noticestates nationwide total 1,240+24d
  7. APR 10ME AGME AG noticestates nationwide total 23,018+30d
  8. APR 10OR AGOR AG noticestates nationwide total 23,018+30d
  9. APR 23MT AGMT AG notice1,459 MT residents+43d
  10. APR 23OR AGOR AG noticestates nationwide total 53,768+43d
  11. APR 23ME AGME AG noticestates nationwide total 53,768+43d
  12. MAY 3NH AGNH AG notice176 NH residents+53d
  13. MAY 4ME AGME AG noticestates nationwide total 12,379+54d
  14. MAY 4OR AGOR AG noticestates nationwide total 12,379+54d
  15. MAY 26DE AGDE AG noticeno count stated+441d
  16. MAY 27OR AGOR AG noticestates nationwide total 2,985+442d
  17. MAY 27ME AGME AG noticestates nationwide total 354,647+442d
  18. MAY 27ME AGME AG noticestates nationwide total 2,985+442d
  19. MAY 27DE AGDE AG noticeno count stated+442d
  20. JUN 3NH AGNH AG notice177 NH residents+449d
  21. AUG 12ME AGME AG noticestates nationwide total 473,705+519d
  22. AUG 15NH AGNH AG notice379 NH residents+522d
  23. OCT 3ME AGME AG noticestates nationwide total 478,278+571d
  24. OCT 7NH AGNH AG noticemost recent · 386 NH residents+575d
  25. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 8, 2020 – Dec 3, 2020
WA AG
Discovered
Dec 3, 2020· 25d undetected
WA AG + OR AG + NH AG +3
Data types
Credentials · Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID · PII
WA AG + NH AG + ME AG +2
Attack vector
Third-Party / Supply Chain
WA 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)

478,278

Sum of filed state slices

44,174· 9.2% of stated

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

US478,278
WA41,871
MT1,459
ME458
NH386

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 filing24 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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 10, 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

575 days

Cadence

~1 / 25d

vs. multi-state median

71.9× 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.