Jamaica Bearings Group Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2024-10-04 and was reported on 2025-01-29. 1 Indiana residents were affected. 275 individuals affected in total.
Affected (this filing): 275
Clustered 2 filings across 2 jurisdictions · filing window Jan 29, 2025 → Jan 30, 2025. View entity profile → Other incidents for this victim →
incident inc_f71e843b61ab4e02 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
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.
IN NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Oct 4, 2024
When the intrusion reportedly occurred, per the linked filings
Oct 9, 2024
Reported by NEW HAMPSHIRE AG filing
Jamaica Bearings Group Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2024-10-04 and was reported on 2025-01-29. 1 Indiana residents were affected. 275 individuals affected in total.
Affected (this filing): 275
Jamaica Bearings Group, Inc. notified individuals of a data breach where an unauthorized third party gained limited access to IT systems on or about October 9, 2024. The incident may have exposed personal information including names, addresses, and Social Security numbers. The company engaged incident response professionals, stopped unauthorized access, and is offering credit monitoring and identity protection services.
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.