HackingRetail & ConsumerRetailVulnerability ExploitCapture Stored DataTargetedPIIFinancial accountFinancial credentialsLowContained

LuckyPet, Inc.

bd_12ee22f3d57b58de · schema v1 · pii pii-v1

Severity

Low

Discovered

Mar 16, 2016

Filed

Apr 22, 2016

To disclose

5 weeks

Affected

67state residents only

Linked

3 filings

Confidence

65%

Full breach record for LuckyPet, Inc. →

LuckyPet, Inc. notified Montana customers that on October 12, 2015, an unauthorized party exploited a vulnerability in third-party shopping cart software to intercept customer data. The company discovered the incident on March 16, 2016. Affected data included names, addresses, and credit card details. LuckyPet updated the software and removed malicious files.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 156 days

discovery → filing · 5 weeks / 37 days

Oct 12, 2015

Begins

Mar 16, 2016

Discovered

Apr 22, 2016

Filed

vs. sector median

2 wks faster

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

Linked disclosures

Why this link?

Regulatory filings (2) · sorted by filing gap

California State AGbd_26c71464ca8203ce2016-04-26 · +4dVerified
Massachusetts State AGbd_13f877eb0f55a4ab2016-04-28 · +6dVerified

Name: LuckyPet, Inc.
norm: luckypet

Name: LuckyPet, Inc.
norm: luckypet
Industry: Retail & Consumerllm

Discovered: Mar 16, 2016
Breach occurred: Oct 12, 2015
Undetected for: 156 daysoccurrence → discovery
Materiality determined: —
Notification sent: Apr 1, 2016
Affected individuals: 67state-resident count only
Data types: PIIFinancial accountFinancial credentials
Attack vector: Unauthorized Access
MITRE ATT&CK: T1190 Exploit Public-Facing ApplicationT1056 Input Capture
Threat actor: ExternalFinancial
Initial access: exploit_public_facing

During the incident: Communicating with the third-party software vendor
The affected files have been removed
The underlying third-party software has been updated
Reviewing all of our security practices
Informed the credit reporting agencies and payment card networks
Changes made: The underlying third-party software has been updated to prevent similar issues in the future
Reviewing all of our security practices to identify additional steps we might take to further protect customer information
Source: Quoted from the filing itself, not independently verified.

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

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 3 filings · 3 states

View merged incident ↗

Montana State AGApr 22 · first · this page

California State AG+4d

Massachusetts State AG+6d

Pattern: first filing Apr 22 (MT), last Apr 28 (MA) — a 6-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/LuckyPet.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Apr 22, 2016
Raw hash: 20bf2f93f26dc79d4e55cd60330a64f68e30b75f9fb122ee89af93fb4f47fc9b

Linked disclosures

Regulatory filings (2) · sorted by filing gap

Reporting entityLuckyPet, Inc.

Victim entityLuckyPet, Inc.

Incidentdiscovered Mar 16, 2016

Stated responseCommunicating with the third-party software vendor

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov