HackingRetail & ConsumerRetailTargetedIdentity (basic)Government IDMediumContained

Zullas LC

bd_80d667b75c28fe3e · schema v1 · pii pii-v1

Severity

Medium

Discovered

—

Filed

Feb 25, 2025

To disclose

—

Affected

9state residents only

Linked

8 filings

Confidence

66%

Full breach record for Zullas LC →

Zullas LC dba Café Zupas LC notified Montana residents of a security incident where an unauthorized actor accessed the network between Oct 21-23, 2024. The actor viewed or copied names and Social Security numbers. The company engaged third-party specialists and implemented additional cybersecurity measures.

J jump to incidentP pin to compareR raw source

Incident timeline

Oct 21, 2024

Begins

Feb 25, 2025

Filed

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

Linked disclosures

Why this link?

Regulatory filings (7) · sorted by filing gap

Indiana State AGbd_1a73b16986b021ca2025-02-25Verified
Maryland State AGbd_2f7626a151348af82025-02-25Verified
Nebraska State AGbd_3184a7101bbb4d7f2025-02-25Verified
Vermont State AGbd_371ba1d20a7127e62025-02-25Verified

Show 3 more filings ↓up to 24d gap

New Hampshire State AGbd_aa357fe5d7efd0652025-02-25Verified
Massachusetts State AGbd_d969ebf35dfc9b2a2025-02-25Verified
Illinois State AGbd_3de3e3391bb506f02025-02-01 · +24dVerified

Name: Zullas LC
norm: zullas lc

Name: Zullas LC
norm: zullas lc
Also named: Zullas LCdba oflegal entity
Café Zupas LCdba oftrade name
Industry: Retail & Consumerllm

Discovered: —
Breach occurred: Oct 21, 2024 – Oct 23, 2024
Materiality determined: —
Notification sent: Feb 25, 2025
Affected individuals: 9state-resident count only
Data types: Identity (basic)Government ID
Attack vector: Unauthorized Access
MITRE ATT&CK: T1078 Valid AccountsT1119 Automated Collection
Threat actor: External

During the incident: Took steps to secure our systems
Launched an investigation into the nature and scope of the activity with the assistance of third-party cybersecurity and data privacy specialists
Undertook a comprehensive and time-intensive review of the data at risk
Notifying potentially impacted individuals
Changes made: Reviewing existing security policies
Implemented additional cybersecurity measures
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 · 8 filings · 8 states

View merged incident ↗

Illinois State AGFeb 1 · first

Indiana State AG+24d

Maryland State AG+24d

Nebraska State AG+24d

Vermont State AG+24d

New Hampshire State AG+24d

Massachusetts State AG+24d

Montana State AG+24d · this page

Pattern: first filing Feb 1 (IL), last Feb 25 (MT) — a 24-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/2025/03/Consumer-notification-letter-139.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Feb 25, 2025
Raw hash: 2b2368d41d1e810050e29e5bb8a64e7dd1e411279e5175e3e3c0aa5a73c94e63

Linked disclosures

Regulatory filings (7) · sorted by filing gap

Reporting entityZullas LC

Victim entityZullas LC

IncidentUnauthorized Access

Stated responseTook steps to secure our systems

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov