HackingRetail & ConsumerRetailStolen CredentialsTargetedCustomer Data InvolvedIdentity (basic)Financial accountLowContained

ILKB, LLC

bd_bf45e3112af8752a · schema v1 · pii pii-v1

Severity

Low

Discovered

Dec 23, 2016

Filed

Apr 19, 2017

To disclose

17 weeks

Affected

159state residents only

Linked

6 filings

Confidence

64%

Full breach record for ILKB, LLC →

ILKB, LLC notified customers of a cyber-attack targeting its systems. Unauthorized access occurred in early October 2016, exposing names, addresses, emails, and credit/debit card info. The breach was detected on December 23, 2016. Notices were sent March 9, 2017.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 83 days

discovery → filing · 17 weeks / 117 days

Oct 1, 2016

Begins

Dec 23, 2016

Discovered

Apr 19, 2017

Filed

vs. sector median

+9 wks slower

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

California State AGbd_ddf52c1647e1b3b52017-04-24 · +5dVerified
Washington State AGbd_8911a8f39765c0df2017-04-12 · +7dCandidate
New Hampshire State AGbd_876dd9be670197a02017-04-11 · +8dVerified
Massachusetts State AGbd_3152dfb4c2bf19262017-03-08 · +42dVerified

Show 1 more filing ↓up to 44d gap

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

Name: ILKB, LLC
norm: ilkb

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

Discovered: Dec 23, 2016
Breach occurred: Oct 1, 2016 – Oct 7, 2016
Undetected for: 83 daysoccurrence → discovery
Materiality determined: —
Notification sent: Mar 9, 2017
Affected individuals: 159state-resident count only
Data types: Identity (basic)Financial account
Attack vector: Unauthorized Access
MITRE ATT&CK: T1078 Valid AccountsT1119 Automated Collection
Threat actor: ExternalFinancial
Initial access: valid_credentials

During the incident: Engaged third-party cybersecurity team to investigate
Recommended customers place a fraud alert on their credit file
Recommended customers request free credit reports
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 17 weeks(117 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

Montana State AG+44d · this page

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://dojmt.gov/wp-content/uploads/ILKB-Inc..pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Apr 19, 2017
Raw hash: 33043efa84c5889ce36d72ee267bc40e267722fb40d173024b26249542c93637

Linked disclosures

Regulatory filings (5) · sorted by filing gap

Reporting entityILKB, LLC

Victim entityILKB, LLC

Incidentdiscovered Dec 23, 2016

Stated responseEngaged third-party cybersecurity team to investigate

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov