GLOBALClaimed by LockBit 3.xFirst sighting
Posted to leak site Nov 3, 2022bd_9a67e1924b63f901
Clustered 3 filings across 3 jurisdictions · filing window Nov 3, 2022 → Aug 23, 2023. View entity profile → Other incidents for this victim →
incident inc_a2ee717830ee4a02 · 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 4, 2022 → Aug 5, 2022
When the intrusion reportedly occurred, per the linked filings
Aug 1, 2022
Reported by VERMONT AG filing
Aug 4, 2022
Reported by MAINE AG filing
Continental Automotive Systems, Inc. notified consumers of a cyberattack occurring July 4–August 5, 2022. Hackers gained access to IT systems, stole data including employee identity, financial, and health information, and threatened to publish it on the darknet. Continental engaged forensic experts, coordinated with the FBI, and provided 24 months of credit monitoring to affected individuals.
Continental AG, a German commercial entity, reported an external system breach (hacking) occurring between July 1, 2022, and August 5, 2022. The incident compromised the names and Social Security Numbers of 5,365 individuals, including 2 Maine residents. The breach was discovered on August 4, 2022. Continental AG provided written notification to affected consumers on August 15, 2023, and offered 24 months of credit monitoring through Cyberscout.
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): 5,365