HackingRetail & ConsumerRetailStolen CredentialsData ExfiltratedCustomer Data InvolvedIdentity (basic)Financial accountFinancial credentialsMediumContained

ILKB, LLC

bd_8911a8f39765c0df · schema v1 · pii pii-v1

Severity

Medium

Discovered

Mar 24, 2017

Filed

Apr 12, 2017

To disclose

19 days

Affected

1,140state residents only

Linked

6 filings

Confidence

70%

Full breach record for ILKB, LLC →

ILKB, LLC, a fitness provider, notified the Washington AG of a cyberattack where unauthorized persons accessed customer data (names, addresses, credit card info) between Oct 2016 and Jan 2017. The breach was discovered on March 24, 2017. 1,140 Washington residents were affected. ILKB retained forensic experts and legal counsel.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 174 days

discovery → filing · 19 days

Oct 1, 2016

Begins

Mar 24, 2017

Discovered

Apr 12, 2017

Filed

vs. sector median

5 wks faster

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

Linked disclosures

Why this link?

Regulatory filings (5) · sorted by filing gap

New Hampshire State AGbd_876dd9be670197a02017-04-11 · +1dVerified
Montana State AGbd_bf45e3112af8752a2017-04-19 · +7dVerified by operator
California State AGbd_ddf52c1647e1b3b52017-04-24 · +12dVerified
Massachusetts State AGbd_3152dfb4c2bf19262017-03-08 · +35dVerified

Show 1 more filing ↓up to 37d gap

New Hampshire State AGbd_ff7512280fa21a122017-03-06 · +37dVerified

Name: ILKB, LLC
norm: ilkb

Name: ILKB, LLC
norm: ilkb
Industry: Retail & Consumerllm

Discovered: Mar 24, 2017
Breach occurred: Oct 1, 2016 – Jan 1, 2017
Undetected for: 174 daysoccurrence → discovery
Materiality determined: —
Notification sent: Apr 12, 2017
Affected individuals: 1,140state-resident count only
Data types: Identity (basic)Financial accountFinancial credentials
Data elements: Financial account numberName
WA-stated cause: Cyberattack
WA-stated duration: lifecycle 100-199dexposure 1-99d
WA-stated discovery: Found after the fact
Attack vector: Unauthorized Access
MITRE ATT&CK: T1190 Exploit Public-Facing ApplicationT1078 Valid Accounts
Threat actor: ExternalFinancial
Regulator citations: Notified Washington State Attorney General
Initial access: exploit_public_facing

During the incident: Retained a third-party team of forensic technical experts to assess and remediate any security concerns
Retained cyber-counsel to ensure notifications to consumers were performed in compliance with the law
Changes made: Considering moving onto a managed server system
Adding further protections to security systems
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 19 days(19 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 · 5 states

View merged incident ↗

New Hampshire State AGMar 6 · first

Massachusetts State AG+2d

New Hampshire State AG+36d

Washington State AG+37d · this page

Montana State AG+44d

California State AG+49d

Pattern: first filing Mar 6 (NH), last Apr 24 (CA) — a 49-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://agportal-s3bucket.s3.amazonaws.com/databreach/BreachM9692.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Apr 12, 2017
Raw hash: c3d75bfc11b4d68520ba26db7124e392960cc92ff942852da3d28a2401601329

Linked disclosures

Regulatory filings (5) · sorted by filing gap

Reporting entityILKB, LLC

Victim entityILKB, LLC

Incidentdiscovered Mar 24, 2017

Stated responseRetained a third-party team of forensic technical experts to assess and remediate any security concerns

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenanceagportal-s3bucket.s3.amazonaws.com