DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteState AGConfirmed6 filings · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcontihigh sensitivity
Merged incident · 6 filings

ORGILL, INC. — October 2021 breach

Clustered 6 filings across 6 jurisdictions · filing window Nov 11, 2021 → Dec 13, 2021. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

6 filings

States

5

Affected · reported

2,459

First → last filing

Nov 11, 2021 → Dec 13, 2021

Merge confidence

100%

incident inc_7414559cfbb9419c · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings and 1 unverified claim. The filings describe hacking. Intrusion Oct 28, 2021–Oct 31, 2021, discovered Oct 31, 2021 — the first regulatory filing landed 38 days later. 2,459 individuals reported across the linked filings. Data reported: Government ID and Identity (basic). Notifications rolled out on a 32-day schedule across 5 filings beginning Nov 11, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
38days

Discovered → first regulatory filing

Discovery variance
2days

Range of discovered_at dates across filings

Leak precedence
27days 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
32days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksMaine⏱ ME AG >30d · 38dLeak gap⏱ Leak >30dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Oct 28, 2021breach begins
Oct 31, 2021discovered · members disagree
notification delay · 38 days
Dec 8, 2021first filing
Dec 13, 2021most 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. NOV 11Leak siteconti postfirst filing · attacker claim · unverifiedday 0
  2. DEC 8MA AGMA AG notice9 MA residents+27d
  3. DEC 8MT AGMT AG notice2 MT residents+27d
  4. DEC 8ME AGME AG noticestates nationwide total 2,459+27d
  5. DEC 8IN AGIN AG noticestates nationwide total 2,459+27d
  6. DEC 13NH AGNH AG noticemost recent · 13 NH residents+32d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 28, 2021 – Oct 31, 2021
MT AG
Discovered
Oct 31, 2021ME AGNov 2, 2021MT AG + NH AGfilings disagree on discovery
Data types
Identity (basic) · Government ID
MA AG + MT AG + ME AG +1
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)

2,459

Sum of filed state slices

40· 1.6% of stated

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

US2,459
NH13
IN12
MA9
ME4
MT2

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 filing5 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 23, 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

32 days

Cadence

~1 / 6.4d

vs. multi-state median

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