HackingRetail & ConsumerRetailCustomer Data InvolvedFinancial accountFinancial credentialsCredentialsMediumContained

Loungefly LLC

bd_0e2d70abafef9180 · schema v1 · pii pii-v1

Severity

Medium

Discovered

—

Filed

Jun 26, 2019

To disclose

—

Affected

4,600

Linked

6 filings

Confidence

66%

Full breach record for Loungefly LLC →

Loungefly, LLC notified customers of a potential data breach involving unauthorized code placed on its online store system between September 19, 2018, and February 13, 2019. Up to 4,600 customers may have had payment card data (account numbers, expiration dates, security codes) and account credentials (usernames, passwords) exposed. The company secured the network, removed the code, and is enhancing password requirements and security controls.

J jump to incidentP pin to compareR raw source

Incident timeline

Sep 19, 2018

Begins

Jun 26, 2019

Filed

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_40a87a9dd04ffd682019-06-26Verified
Massachusetts State AGbd_d83648fc654a21992019-04-30 · +57dVerified
California State AGbd_04e9e0ad1ffc100c2019-04-26 · +61dCandidate
Montana State AGbd_2e1a85e9716b9e062019-04-26 · +61dVerified

Show 1 more filing ↓up to 61d gap

New Hampshire State AGbd_9dcbaffa89ba0de62019-04-26 · +61dVerified

Name: Loungefly LLC
norm: loungefly
Domain: loungefly.com

Name: Loungefly LLC
norm: loungefly
Domain: loungefly.com
Industry: Retail & Consumerllm

Discovered: —
Breach occurred: Sep 19, 2018 – Feb 13, 2019
Materiality determined: —
Notification sent: Jun 27, 2019
Affected individuals: 4,600nationwide
Data types: Financial accountFinancial credentialsCredentials
Attack vector: Unknown
MITRE ATT&CK: T1505.003 Web Shell

During the incident: Took steps to secure the affected part of our network
Confirmed that the unauthorized code was not present on the system that now operates our online store
Commenced an investigation to understand the nature and scope of the incident
Reported the matter to law enforcement
Changes made: Taking steps to further strengthen and enhance our information security controls and procedures
Ongoing coordination with our development team to further harden our system
Enhancing the complexity requirements for customer passwords
Requiring all Loungefly customers to select a new password that complies with the new requirements the next time they log in to their Loungefly account
Source: Quoted from the filing itself, not independently verified.

Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 6 filings · 4 states

View merged incident ↗

California State AGApr 26 · first

Montana State AGApr 26 · first

New Hampshire State AGApr 26 · first

Massachusetts State AG+4d

New Hampshire State AG+61d

California State AG+61d · this page

Pattern: first filing Apr 26 (CA), last Jun 26 (CA) — a 61-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://oag.ca.gov/ecrime/databreach/reports/sb24-148443
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Jun 26, 2019
Raw hash: 29ea4693ada8f52bf4d33aede57efde4830efec55703429ac34c75610718133b

Linked disclosures

Regulatory filings (5) · sorted by filing gap

Reporting entityLoungefly LLC

Victim entityLoungefly LLC

IncidentUnknown

Stated responseTook steps to secure the affected part of our network

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenanceoag.ca.gov