Clustered 4 filings across 4 jurisdictions · filed Jun 3, 2020. View entity profile → Other incidents for this victim →
incident inc_0c26adec18aa4181 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
CA MT OR WA
all State AG
per-filing reported counts
State AGs report only their own residents; bars show per-filing counts.
Earliest sighting first · deep chronology in Litigation Timeline
Nov 11, 2016
When the intrusion reportedly occurred, per the linked filings
Dec 26, 2018
Reported by WASHINGTON AG filing
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.
Bombas LLC reported a data breach to the Montana Attorney General. The breach was reported on 2020-06-03. The breach occurred from 11/11/2016 to 2/16/2017. 289 Montana residents were affected.
Affected (this filing): 289
Bombas LLC reported a data breach to the Oregon Attorney General. The breach was reported on 2020-06-03. The breach occurred during 11/11/2016 - 2/16/2017. 83,000 individuals were affected. Notice was sent on 6/3/2020.
Affected (this filing): 83,000
Bombas LLC discovered that malicious code designed to scrape payment card data and personal information may have been present on its e-commerce platform from November 11, 2016 to February 16, 2017. A security feature added in February 2017 stopped the code from functioning. An investigative report received May 20, 2020 could not rule out successful scraping of customer name, address, and payment card data. Customers were offered two years of identity monitoring services.
Bombas LLC, a business sector entity reported a malware incident to the Washington Attorney General. The organization became aware of the incident on 2018-12-26 and filed notice on 2020-06-03. 2,313 Washington residents were affected. 525 days elapsed between awareness and notification. 775 days to identify the breach. 0 days to contain the breach.
Affected (this filing): 2,313