HackingRetail & ConsumerRetailStolen CredentialsSupply Chain (3P Vendor)Data ExfiltratedCustomer Data InvolvedIdentity (basic)Financial accountMediumContained

Kayser-Roth, Inc.

bd_08f13f5794e8a6ea · schema v1 · pii pii-v1

Severity

Medium

Discovered

Feb 6, 2017

Filed

Jul 5, 2017

To disclose

21 weeks

Affected · nationwide

90,5481,325 in this filing

Linked

6 filings

Confidence

65%

Full breach record for Kayser-Roth, Inc. →3 incidents on file

Kayser-Roth Corporation notified customers of a data breach involving its third-party payment processor, Aptos Inc. The intrusion, occurring from February to December 2016, compromised names, addresses, emails, and payment card data for approximately 90,548 customers across Nononsense.com and Hue.com. Kayser-Roth engaged Mandiant for forensics and cooperated with the FBI and DOJ.

J jump to incidentP pin to compareR raw source

South Carolina clock✓ SC CRA notice due21 weeks discovery → filing

⚠ unattributedNo provenance was recorded for this discovery date and it matches no other date on the record. It may be correct, but it is not independently grounded.

Incident timeline

undetected · 371 days

discovery → filing · 21 weeks / 149 days

Feb 1, 2016

Begins

Feb 6, 2017

Discovered

Jul 5, 2017

Filed

vs. sector median

+12 wks slower

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

Part of Aptos supply-chain incident (2017) — a supply-chain cascade affecting multiple organizations.View cascade →

Linked disclosures

Why this link?

Regulatory filings (5) · sorted by filing gap

California State AGbd_a84a721cdf83e5642017-07-05Verified
New Hampshire State AGbd_cff9302ab13ddd092017-07-05Verified
Montana State AGbd_b53bf980330e0a422017-07-03 · +2dVerified
Oregon State AGbd_c8f623bb36a6f0112017-06-20 · +15dCandidate

Show 1 more filing ↓up to 16d gap

Washington State AGbd_656a73d558860e4e2017-06-19 · +16dVerified

Name: Kayser-Roth, Inc.
norm: kayser roth

Name: Kayser-Roth, Inc.
norm: kayser roth
Industry: Retail & Consumerllm

Discovered: Feb 6, 2017
Breach occurred: Feb 1, 2016 – Dec 6, 2016
Undetected for: 371 daysoccurrence → discovery
Materiality determined: —
Notification sent: Jun 1, 2017
Affected individuals: 90,548state + nationwide
Data types: Identity (basic)Financial account
Attack vector: Third-Party / Supply Chain
MITRE ATT&CK: T1195 Supply Chain CompromiseT1041 Exfiltration Over C2 ChannelT1078 Valid Accounts
Threat actor: ExternalFinancial
Regulator citations: Worked with the FBI Cyber division and the U.S. Department of Justice to investigate this incidentReceived an official request from the FBI to defer disclosure for a minimum of 60 days given the FBI’s active investigation
Third party: via Aptos Inc.
Initial access: supply_chain

During the incident: Engaged Mandiant, a forensic cybersecurity firm, to assist with stopping and remedying the data security breach
Removed the malicious software used to access the system
Deploying additional integrity monitoring software
Implemented changes to its systems for best-in-class security with the assistance of external security consultants
Worked with the FBI Cyber division and the U.S. Department of Justice to investigate this incident
Supplied the numbers of the affected payment cards to their issuers for monitoring
Changes made: Deploying additional integrity monitoring software to alert it to any similar attack
Implemented changes to its systems for best-in-class security
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 21 weeks(149 days from discovery to filing)
Compliance flags: SC CRA notice due
Discovery-date grounding: unattributedNo provenance was recorded for this discovery date and it matches no other date on the record. It may be correct, but it is not independently grounded.

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 6 filings · 6 states

View merged incident ↗

Washington State AGJun 19 · first

Oregon State AG+1d

Montana State AG+14d

California State AG+16d

New Hampshire State AG+16d

South Carolina State AG+16d · this page

Pattern: first filing Jun 19 (WA), last Jul 5 (SC) — a 16-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

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://consumer.sc.gov/sites/consumer/files/Documents/Business%20Resources%20Laws/Related%20Laws/Breaches/2017/KayserRothCorporation.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Jul 5, 2017
Raw hash: 11ed5ff4b8111f3d615a457d66ab64eebcf1742ee50e6e5f6626e111f0544ccb

Linked disclosures

Regulatory filings (5) · sorted by filing gap

Reporting entityKayser-Roth, Inc.

Victim entityKayser-Roth, Inc.

Incidentdiscovered Feb 6, 2017

Stated responseEngaged Mandiant, a forensic cybersecurity firm, to assist with stopping and remedying the data security breach

ComplianceSC CRA notice due

Extraction provenanceno artifact recorded

Source provenanceconsumer.sc.gov