Bimba LLC — August 2020 breach
One linked filing — more sources may join as they report · filed Dec 28, 2020. View entity profile → Other incidents for this victim →
incident inc_db1599eb6f3741d3 · merged by deterministic
Litigation Timing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Incident timeline
No discovery date is recorded on any filing in this cluster, so the notification delay is not computable. Dashed segments fill in as filings merge.
Member cascade — every filing about this breach
- DEC 28NH AGNH AG noticeonly filing · states nationwide total 844day 0
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- Aug 21, 2020 – Nov 13, 2020 NH AG
- Discovered
- —
- Data types
- Identity (basic) · Financial account NH AG
- Attack vector
- Misconfiguration NH AG
- Response
- Began an investigation to determine how the security incident occurred and the scope of such incident · Offering a complimentary 24-month membership with Experian · Sending consumer notice to affected individuals NH 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)
844
Sum of filed state slices
11· 1.3% of stated
99% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.
Evidence ladder — rungs this incident occupies
No leak-site claim on record for this incident.
No press coverage linked yet.
Unlocks: discovery date, data types, affected count, compliance clock.
No SEC filing or victim statement yet.
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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.