GLOBALClaimed by NitrogenFirst sighting
Posted to leak site Jul 15, 2025bd_6be3144308dc6396
Sale of new cars of famous brands: Chevrolet, Chrysler, Dodge, Jeep, Ram. Sale of used cars, budget cars. Service and repair. Registration of loans, leasing.
Clustered 3 filings across 3 jurisdictions · filing window Jul 15, 2025 → Jan 27, 2026. View entity profile → Other incidents for this victim →
incident inc_920676d6b44a4ec1 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
IN NH
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jun 20, 2025
When the intrusion reportedly occurred, per the linked filings
Jun 20, 2025
Reported by NEW HAMPSHIRE AG filing
Sale of new cars of famous brands: Chevrolet, Chrysler, Dodge, Jeep, Ram. Sale of used cars, budget cars. Service and repair. Registration of loans, leasing.
Progressive Auto Group reported a data breach to the Indiana Attorney General. The breach occurred on 2025-06-20 and was reported on 2025-12-29. 3 Indiana residents were affected. 1,680 individuals affected in total.
Affected (this filing):
Progressive Auto Group notified the New Hampshire Attorney General of a security incident involving unauthorized network access. The breach affected one New Hampshire resident, exposing name, driver's license/state ID, and potentially financial account numbers. The incident occurred on June 20, 2025, was discovered on that date, and notification was mailed on January 27, 2026. The company engaged a cybersecurity firm, secured the network, and provided one year of credit monitoring to the affected individual.
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): 1