DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteState AGConfirmed11 filings · 7 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedbianlianhigh sensitivity
Merged incident · 11 filings

Bunkhouse Group — April 2022 breach

Clustered 11 filings across 8 jurisdictions · filing window Nov 2, 2022 → Apr 15, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

7

Affected · reported

3,659

First → last filing

Nov 2, 2022 → Apr 15, 2025

Merge confidence

100%

incident inc_d0c5f9a0da4c497b · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings and 2 unverified claims. Intrusion Apr 28, 2022–Jun 30, 2024, discovered May 12, 2022 — the first regulatory filing landed 174 days later (flagged late). 3,659 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 4 more. Notifications rolled out on a 895-day schedule across 9 filings beginning Nov 2, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
174days

Discovered → first regulatory filing

Discovery variance
797days

Range of discovered_at dates across filings

Leak precedence
Noneclaim trailed by 577d

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
895days

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 >180dMaine✗ ME AG >90d · 272dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Apr 28, 2022breach begins
May 12, 2022discovered · members disagree
notification delay · 174 days
Nov 2, 2022first filing
Apr 15, 2025most 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 2IN AGIN AG noticefirst filing · states nationwide total 1,340day 0
  2. NOV 2MT AGMT AG notice1 MT residentsday 0
  3. NOV 2MA AGMA AG notice2 MA residentsday 0
  4. JUN 1Leak sitebianlian postattacker claim · unverified+577d
  5. JUL 24Leak sitebianlian postattacker claim · unverified+631d
  6. AUG 28MA AGMA AG notice8 MA residents+665d
  7. APR 14NH AGNH AG noticeno count stated+894d
  8. APR 15NE AGNE AG notice2 NE residents+895d
  9. APR 15IN AGIN AG noticestates nationwide total 3,659+895d
  10. APR 15VT AGVT AG noticeno count stated+895d
  11. APR 15ME AGME AG noticemost recent · 5 ME residents+895d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 28, 2022
IN AG
Discovered
May 12, 2022MT AGJul 17, 2024NE AG + ME AGfilings disagree on discovery
Data types
Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID · PCI · PII
MT AG + NH AG + NE AG +3
Attack vector
Phishing
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,659

Sum of filed state slices

38· 1.0% of stated

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

US3,659
IN22
MA8
ME5
NE2
MT1

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 claim2 members

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

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

895 days

Cadence

~1 / 89.5d

vs. multi-state median

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