All incidents View linkage analytics →Get the evidence package — $7.99 what’s inside →

Confirmed11 filings · 9 statesUnverified claimConfirmedEnforcedakirahigh sensitivity

Merged incident · 11 filings

Green Diamond Resource Company — June 2023 breach

Clustered 11 filings across 10 jurisdictions · filing window Jul 10, 2023 → Apr 19, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

Affected · reported

27,896

First → last filing

Jul 10, 2023 → Apr 19, 2024

Merge confidence

100%

incident inc_f0d418ec0ad64478 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings and 1 unverified claim. Intrusion Jun 26, 2023–Jun 27, 2023, discovered Jun 27, 2023 — the first regulatory filing landed 297 days later (flagged late). 27,896 individuals reported across the linked filings. Data reported: Government ID, Financial account, Authentication, and 5 more. Notifications rolled out on a 284-day schedule across 10 filings beginning Jul 10, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay

297days

Discovered → first regulatory filing

Discovery variance

241days

Range of discovered_at dates across filings

Leak precedence

284days before filing

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span

284days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksLeak gap✗ Leak >180dVermont✗ VT AG >45 bdayCalifornia✗ CA 60-day late · 297dFull clock table in Litigation Timeline

Sensitive data

authenticationfinancial_credentialsidentity_government

Incident timeline

Jun 26, 2023breach begins

Jun 27, 2023discovered · members disagree

notification delay · 297 days

Apr 19, 2024first filing

—watching for filings

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

Member cascade — every filing about this breach

JUL 10Leak siteakira postfirst filing · attacker claim · unverifiedoperator-confirmedday 0
APR 19MA AGMA AG notice44 MA residentsoperator-confirmed+284d
APR 19OR AGOR AG noticestates nationwide total 27,896operator-confirmed+284d
APR 19WA AGWA AG notice9,532 WA residentsoperator-confirmed+284d
APR 19ME AGME AG noticestates nationwide total 27,896operator-confirmed+284d
APR 19VT AGVT AG noticeno count statedoperator-confirmed+284d
APR 19IN AGIN AG noticestates nationwide total 27,896operator-confirmed+284d
APR 19NH AGNH AG notice135 NH residentsoperator-confirmed+284d
APR 19CA AGCA AG noticeno count statedoperator-confirmed+284d
APR 19HHS OCRHHS OCR noticestates nationwide total 8,172operator-confirmed+284d
APR 19MT AGMT AG noticemost recent · 158 MT residentsoperator-confirmed+284d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Jun 26, 2023 – Jun 27, 2023
Discovered: Jun 27, 2023WA AG + VT AG + NH AG +2Feb 23, 2024ME AGfilings disagree on discovery
Data types: Authentication · Credentials · Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID · PHI
Attack vector: Ransomware

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)

27,896

Sum of filed state slices

9,948· 35.7% of stated

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

US27,896

WA9,532

MT158

NH135

IN50

MA44

ME29

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 claim1 member

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

Press / market report

No press coverage linked yet.

State AG / regulator filing10 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 Aug 22, 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

284 days

Cadence

~1 / 28.4d

vs. multi-state median

35.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.