HackingRetail & ConsumerTechnologyRetailStolen CredentialsCapture Stored DataData ExfiltratedCustomer Data InvolvedSupply Chain (3P Vendor)PIIIdentity (basic)Financial accountPCIMediumContained

Kayser-Roth, Inc.

bd_b53bf980330e0a42 · schema v1 · pii pii-v1

Severity

Medium

Discovered

Feb 6, 2017

Filed

Jul 3, 2017

To disclose

21 weeks

Affected · nationwide

90,548209 in this filing

Linked

6 filings

Confidence

66%

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

Kayser-Roth Corporation (via HUE) notified customers of a third-party vendor breach involving Aptos Inc. Intrusion occurred Feb-Dec 2016; discovered Feb 6, 2017. Compromised data included names, addresses, emails, and payment card info for ~90,548 customers. Aptos engaged Mandiant and FBI/DOJ. Incident contained.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 371 days

discovery → filing · 21 weeks / 147 days

Feb 1, 2016

Begins

Feb 6, 2017

Discovered

Jul 3, 2017

Filed

vs. sector median

+11 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

South Carolina State AGbd_08f13f5794e8a6ea2017-07-05 · +2dVerified
California State AGbd_a84a721cdf83e5642017-07-05 · +2dVerified
New Hampshire State AGbd_cff9302ab13ddd092017-07-05 · +2dVerified
Oregon State AGbd_c8f623bb36a6f0112017-06-20 · +13dCandidate

Show 1 more filing ↓up to 14d gap

Washington State AGbd_656a73d558860e4e2017-06-19 · +14dVerified

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

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

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: PIIIdentity (basic)Financial accountPCI
Attack vector: Third-Party / Supply Chain
MITRE ATT&CK: T1190 Exploit Public-Facing ApplicationT1041 Exfiltration Over C2 Channel
Threat actor: ExternalFinancial
Regulator citations: Worked with FBI Cyber divisionWorked with U.S. Department of Justice
Third party: via Aptos Inc.
Initial access: exploit_public_facing

During the incident: Engaged Mandiant to assist with stopping and remedying the data security breach
Malicious software used to access the system has been completely removed
Deploying additional integrity monitoring software
Implemented changes to systems for best-in-class security
Worked with FBI Cyber division and the U.S. Department of Justice to investigate
Supplied numbers of affected payment cards to issuers for monitoring
Changes made: Deploying additional integrity monitoring software to alert to similar attacks
Implemented changes to systems for best-in-class security
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 21 weeks(147 days from discovery to filing)
Compliance flags: — (clock not assessable for this source)

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 · this page

South Carolina State AG+16d

California State AG+16d

New Hampshire State AG+16d

Pattern: first filing Jun 19 (WA), last Jul 5 (NH) — 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://dojmt.gov/wp-content/uploads/Kayser-Roth-Inc..pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Jul 3, 2017
Raw hash: 649b388d659288b3edd271eed9caaa2f94b69d46987a9845e22b8ffc855f52aa

Linked disclosures

Regulatory filings (5) · sorted by filing gap

Reporting entityKayser-Roth, Inc.

Victim entityKayser-Roth, Inc.

Incidentdiscovered Feb 6, 2017

Stated responseEngaged Mandiant to assist with stopping and remedying the data security breach

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov