GLOBALClaimed by Hunters InternationalFirst sightinglinked via shared-victim match · 100%
Posted to leak site Jul 20, 2024bd_7067ebba28f13225
Country : United States of America - Exfiltraded data : yes - Encrypted data : no
Clustered 4 filings across 3 jurisdictions · filing window Jul 20, 2024 → Dec 10, 2024. View entity profile → Other incidents for this victim →
incident inc_177a5977b6bc4ecc · merge_method human · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Materiality delta · SEC filing delay — no SEC 8-K in this cluster.
ME VT
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jul 20, 2024
When the intrusion reportedly occurred, per the linked filings
Country : United States of America - Exfiltraded data : yes - Encrypted data : no
Country : United States of America - Exfiltraded data : yes - Encrypted data : no
Oct 11, 2024
Reported by VERMONT AG, MAINE AG filings
Rumpke Consolidated Companies, Inc. notified consumers of a data breach where attackers accessed systems via compromised credentials starting July 20, 2024. Data exposed included PII (SSN, DOB, driver's license), health insurance/billing data, and financial account info. Rumpke engaged forensic teams, notified law enforcement, and provided 24 months of credit monitoring.
Rumpke Consolidated Companies, Inc. reported a data breach affecting 2 Maine residents. The breach, described as an external system hack, occurred between July 20, 2024, and August 31, 2024, and was discovered on October 11, 2024. Affected individuals were notified on December 10, 2024, and offered 24 months of single-bureau credit monitoring services through Epiq.
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.
Affected (this filing): 2