Clustered 2 filings across 2 jurisdictions · filing window Dec 10, 2024 → Dec 11, 2024. View entity profile → Other incidents for this victim →
incident inc_43cb77af7c6c4911 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
PCI · PII
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.
ME VT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Aug 3, 2024 → Aug 5, 2024
When the intrusion reportedly occurred, per the linked filings
Dec 5, 2024
Reported by VERMONT AG, MAINE AG filings
Hay House LLC notified consumers that malicious code on its website captured payment card data (names, card numbers, CVVs, expiration dates) entered between August 3-5, 2024. The incident was discovered on December 5, 2024. Forensic investigators were engaged. 13 Rhode Island residents were explicitly identified as impacted.
Hay House LLC (hayhouse.com) discovered on December 5, 2024 that malicious code was injected into their website checkout page, capturing payment card data (cardholder name, card number, CVV, expiration date) from customers who transacted between August 3–5, 2024. 6,011 individuals were affected in total; 19 were Maine residents. The incident was classified as an external system breach (hacking). No identity theft protection services were offered.
Affected (this filing): 19
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.