GLOBALClaimed by AbyssFirst sighting
Posted to leak site Feb 7, 2024bd_75e24914fa404bc5
transaxle.com 795Gb uncompressed data
Clustered 2 filings across 2 jurisdictions · filing window Feb 7, 2024 → Apr 10, 2024. View entity profile → Other incidents for this victim →
incident inc_a74140dc2703481f · merge_method human · 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.
ME
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jan 19, 2024
When the intrusion reportedly occurred, per the linked filings
transaxle.com 795Gb uncompressed data
Mar 28, 2024
Reported by MAINE AG filing
TransAxle, a technology company based in New Jersey, reported a ransomware incident on January 19, 2024, discovered on March 28, 2024. The breach affected 401 individuals, including 17 Maine residents. Personal information, including Social Security Numbers, was compromised. TransAxle provided 12 months of credit monitoring and identity protection services through Epiq to affected individuals.
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): 401