HackingRetail & ConsumerRetailStolen CredentialsCapture Stored DataTargetedCustomer Data InvolvedPCIFinancial accountMediumContained

Loungefly LLC

bd_2e1a85e9716b9e06 · schema v1 · pii pii-v1

Severity

Medium

Discovered

—

Filed

Apr 26, 2019

To disclose

—

Affected · nationwide

3,6002 in this filing

Linked

6 filings

Confidence

66%

Full breach record for Loungefly LLC →

Loungefly, LLC notified Montana AG of a potential unauthorized access to its online store payment processing network. Unauthorized code was placed on the network between Sept 19 and Dec 17, 2018. Payment card data (names, account numbers, security codes) for up to 3,600 transactions may have been affected, though theft was not confirmed. Investigation concluded April 3, 2019. Law enforcement was notified.

J jump to incidentP pin to compareR raw source

Incident timeline

Sep 19, 2018

Begins

Apr 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

California State AGbd_04e9e0ad1ffc100c2019-04-26Candidate
New Hampshire State AGbd_9dcbaffa89ba0de62019-04-26Verified
Massachusetts State AGbd_d83648fc654a21992019-04-30 · +4dVerified
California State AGbd_0e2d70abafef91802019-06-26 · +61dVerified

Show 1 more filing ↓up to 61d gap

New Hampshire State AGbd_40a87a9dd04ffd682019-06-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 – Dec 17, 2018
Materiality determined: —
Notification sent: Apr 26, 2019
Affected individuals: 3,600state + nationwide
Data types: PCIFinancial account
Attack vector: Unauthorized Access
MITRE ATT&CK: T1190 Exploit Public-Facing ApplicationT1041 Exfiltration Over C2 Channel
Threat actor: ExternalFinancial
Regulator citations: reported the matter to law enforcement
Initial access: exploit_public_facing

During the incident: Took immediate steps to secure the affected part of our network, including removing the unauthorized code
Commenced an investigation to understand the nature and scope of the incident
Reported the matter to law enforcement
Taking steps to further strengthen and enhance our information security controls and procedures
Ongoing coordination with our development team to further harden our system
Changes made: Ongoing coordination with our development team to further harden our system
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

New Hampshire State AGApr 26 · first

Montana State AGApr 26 · first · this page

Massachusetts State AG+4d

California State AG+61d

New Hampshire State AG+61d

Pattern: first filing Apr 26 (CA), last Jun 26 (NH) — 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://dojmt.gov/wp-content/uploads/OCP/CON-LFLY-MT-AG-Regulator-Notice.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Apr 26, 2019
Raw hash: e71fb680de0408078a19b5eb7504d66fcc895baa6926e485c8ebb71b7115da9c

Linked disclosures

Regulatory filings (5) · sorted by filing gap

Reporting entityLoungefly LLC

Victim entityLoungefly LLC

IncidentUnauthorized Access

Stated responseTook immediate steps to secure the affected part of our network, including removing the unauthorized code

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov