Confirmed breach. Intrusion Apr 5, 2024–Aug 29, 2024, discovered Jun 6, 2024 — the first regulatory filing landed 196 days later (flagged late). 17 individuals reported across the linked filings.
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Regulatory clocksLeak gap✗ Leak >180dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedlow sensitivity
Affected (total reported)
17
Data types
1
Identity (basic)
Jurisdictions
2
CA NH
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Apr 5, 2024 → Aug 29, 2024
When the intrusion reportedly occurred, per the linked filings
62 days
Breach discoveredletter-grounded
Jun 6, 2024
Reported by NEW HAMPSHIRE AG filing
196 days
⛰️New Hampshire State AGFirst filinglinked via multistate filing link · 100%
The Coffee Bean & Tea Leaf experienced unauthorized access to systems and email accounts between April and August 2024. The breach affected 17 New Hampshire residents, potentially exposing PII. The company notified law enforcement, offered credit monitoring, and implemented employee training.
International Coffee & Tea, LLC (The Coffee Bean & Tea Leaf) reported unauthorized access to certain systems and limited email accounts between April 5 and August 29, 2024. An external actor gained access, potentially viewing names and other personal information. The company engaged third-party cybersecurity specialists, strengthened system security, and offered credit monitoring to affected individuals.
Leak >180d
About this clustering
DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.