HackingRetail & ConsumerRetailStolen CredentialsCapture Stored DataDelayed DiscoveryCustomer Data InvolvedPIIIdentity (basic)Financial accountLowContained

Bombas

bd_032c860efe4a2ff3 · schema v1 · pii pii-v1

Severity

Low

Discovered

Nov 11, 2016

Filed

Jun 3, 2020

To disclose

43 months

Affected

289state residents only

Linked

7 filings

Confidence

66%

Full breach record for Bombas →4 incidents on file

Bombas LLC notified Montana residents of a data breach involving malicious code on its e-commerce platform. The code, present from Nov 11, 2016 to Feb 16, 2017, potentially scraped customer names, addresses, and payment card data. Bombas added a security feature in Feb 2017 to stop the code and offered two years of free identity monitoring to affected individuals.

J jump to incidentP pin to compareR raw source

Incident timeline

discovery → filing · 43 months / 1300 days

Nov 11, 2016

Begins

Nov 11, 2016

Discovered

Jun 3, 2020

Filed

vs. sector median

+178 wks slower

This filing is one of 7 about the same incident.View merged incident

Linked disclosures

Why this link?

Regulatory filings (6) · sorted by filing gap

New Hampshire State AGbd_2e0f55b86f1170a32020-06-03Verified
Oregon State AGbd_2f92b42d2848b3ab2020-06-03Verified
California State AGbd_9101cc153fd11ef12020-06-03Verified
Indiana State AGbd_9b29684e29b93fe12020-06-03Verified

Show 2 more filings ↓up to 1d gap

Washington State AGbd_f50804e00f8304562020-06-03Verified
Massachusetts State AGbd_43c63091f0426d8f2020-06-04 · +1dVerified

Name: Bombas
norm: bombas

Name: Bombas
norm: bombas
Industry: Retail & Consumerllm

Discovered: Nov 11, 2016
Breach occurred: Nov 11, 2016 – Feb 16, 2017
Undetected for: 0 daysoccurrence → discovery
Materiality determined: —
Notification sent: —
Affected individuals: 289state-resident count only
Data types: PIIIdentity (basic)Financial account
Attack vector: Unauthorized Access
MITRE ATT&CK: T1190 Exploit Public-Facing ApplicationT1056 Input Capture
Threat actor: ExternalFinancial
Initial access: exploit_public_facing

During the incident: Added a new security feature to the e-commerce platform on February 16, 2017
Launched a thorough investigation to determine whether personal information was exposed
Received an investigative report on May 20, 2020
Provided identity monitoring services at no cost for two years
Changes made: Added a new security feature to the e-commerce platform on February 16, 2017
Taken other steps in recent years to further improve security and prevent similar incidents from happening in the future
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 43 months(1300 days from discovery to filing)
Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 7 filings · 7 states

View merged incident ↗

New Hampshire State AGJun 3 · first

Oregon State AGJun 3 · first

California State AGJun 3 · first

Indiana State AGJun 3 · first

Washington State AGJun 3 · first

Montana State AGJun 3 · first · this page

Massachusetts State AG+1d

Evidence ladder

Leak-site claim

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

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source URL: https://dojmt.gov/wp-content/uploads/OCP/General-Notice-103.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Jun 3, 2020
Raw hash: a6e79f025e42fc05d16a30c992339a120348a552c5ba173fe9abbe1c034d9183

Linked disclosures

Regulatory filings (6) · sorted by filing gap

Reporting entityBombas

Victim entityBombas

Incidentdiscovered Nov 11, 2016

Stated responseAdded a new security feature to the e-commerce platform on February 16, 2017

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov