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

Greylock McKinnon Associates — May 2023 breach

Clustered 12 filings across 9 jurisdictions · filing window Jan 24, 2024 → Apr 16, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

12 filings

States

9

Affected · reported

352,965

First → last filing

Jan 24, 2024 → Apr 16, 2024

Merge confidence

100%

incident inc_59bb36e11af44532 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 12 regulatory filings. Intrusion May 17, 2023–May 30, 2023, discovered May 30, 2023 — the first regulatory filing landed 239 days later; 3 later filings were flagged late. 352,965 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 3 more. Notifications rolled out on a 83-day schedule across 12 filings beginning Jan 24, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
239days

Discovered → first regulatory filing

Discovery variance
253days

Range of discovered_at dates across filings

Filing span
83days

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 >45dCalifornia✗ CA 60-day late · 314dWashington✗ WA AG >90dMaine⏱ ME AG >30d · 58dMassachusetts✓ MA credit monitoring dueSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 17, 2023breach begins
May 30, 2023discovered · members disagree
notification delay · 239 days
Jan 24, 2024first filing
Apr 16, 2024most 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. JAN 24MA AGMA AG noticefirst filing · 787 MA residentsday 0
  2. FEB 23MT AGMT AG notice193 MT residents+30d
  3. FEB 23NH AGNH AG notice1 NH residents+30d
  4. FEB 23ME AGME AG noticestates nationwide total 5,465+30d
  5. FEB 23MA AGMA AG notice787 MA residents+30d
  6. FEB 23IN AGIN AG noticestates nationwide total 352,965+30d
  7. APR 4NH AGNH AG noticestates nationwide total 1,841+71d
  8. APR 5OR AGOR AG noticestates nationwide total 341,650+72d
  9. APR 5CA AGCA AG noticestates nationwide total 13,674+72d
  10. APR 5ME AGME AG noticestates nationwide total 341,650+72d
  11. APR 5SC AGSC AG noticestates nationwide total 15,244+72d
  12. APR 16WA AGWA AG noticemost recent · 1,323 WA residents+83d
  13. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 30, 2023
ME AG
Discovered
May 30, 2023MT AG + NH AG + CA AG +2Feb 5, 2024ME AGFeb 7, 2024OR AG + ME AGfilings disagree on discovery
Data types
Government ID
MA AG + MT AG + ME 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)

352,965

Sum of filed state slices

34,405· 9.7% of stated

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

US352,965
IN26,375
ME2,067
NH1,840
SC1,820
WA1,323
MA787
MT193

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 filing12 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
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

83 days

Cadence

~1 / 7.5d

vs. multi-state median

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