Clustered 2 filings across 2 jurisdictions · filing window Dec 30, 2021 → Jan 24, 2022. View entity profile → Other incidents for this victim →
incident inc_804d6045cb664ef5 · merge_method human · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
ME WA
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Nov 1, 2019 → Aug 31, 2021
When the intrusion reportedly occurred, per the linked filings
Oct 10, 2021
Reported by WASHINGTON AG filing
Dec 2, 2021
Reported by MAINE AG filing
Penn LLC d/b/a PulseTV, a business sector entity reported a malware incident to the Washington Attorney General. The organization became aware of the incident on 2021-10-10 and filed notice on 2021-12-30. 4,302 Washington residents were affected. 81 days elapsed between awareness and notification. 709 days to identify the breach. 0 days to contain the breach.
Affected (this filing): 4,302
Penn LLC, doing business as Pulse TV, reported a data breach that appears to be an external system breach, though it could not be confirmed. The breach occurred between November 1, 2019, and August 31, 2021, and was discovered on December 2, 2021. The compromised information includes financial account numbers or credit/debit card numbers in combination with security codes, access codes, passwords, or PINs. This notice is a supplement to a previous notification, with the total number of affected Maine residents updated to 753.
Affected (this filing): 753
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.