MalwareRetail & ConsumerRetailCapture App DataInfostealerCustomer Data InvolvedDelayed DiscoveryIdentity (basic)Financial accountPIIPCILowResolved

Bombas

bd_9101cc153fd11ef1 · schema v1 · pii pii-v1

Severity

Low

Discovered

—

Filed

Jun 3, 2020

To disclose

—

Affected

Not disclosed

Linked

7 filings

Confidence

70%

Full breach record for Bombas →4 incidents on file

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.

J jump to incidentP pin to compareR raw source

Incident timeline

Nov 11, 2016

Begins

Jun 3, 2020

Filed

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

Montana State AGbd_032c860efe4a2ff32020-06-03Candidate
New Hampshire State AGbd_2e0f55b86f1170a32020-06-03Verified
Oregon State AGbd_2f92b42d2848b3ab2020-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: —
Breach occurred: Nov 11, 2016 – Feb 16, 2017
Materiality determined: —
Notification sent: —
Affected individuals: Not disclosed
Data types: Identity (basic)Financial accountPIIPCI
Attack vector: Unauthorized Access
MITRE ATT&CK: T1056 Input CaptureT1185 Browser Session Hijacking
Threat actor: ExternalFinancial

During the incident: Launched a thorough investigation to determine whether personal information of our customers was potentially exposed
Received an investigative report on May 20, 2020
Changes made: In February 2017, a feature was added to our e-commerce platform that would prevent malicious code attacks like this one
Taken other steps in recent years to further improve security and prevent similar incidents from happening in the future
Made arrangements to provide identity monitoring services at no cost to affected customers for two years
Source: Quoted from the filing itself, not independently verified.

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 ↗

Montana State AGJun 3 · first

New Hampshire State AGJun 3 · first

Oregon State AGJun 3 · first

Indiana State AGJun 3 · first

Washington State AGJun 3 · first

California 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://oag.ca.gov/ecrime/databreach/reports/sb24-190612
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: 563a229c17b6848932c1dc4e2814be595ebc871e92625811da7d91bd1ab9a741

Linked disclosures

Regulatory filings (6) · sorted by filing gap

Reporting entityBombas

Victim entityBombas

IncidentUnauthorized Access

Stated responseLaunched a thorough investigation to determine whether personal information of our customers was potentially exposed

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenanceoag.ca.gov