GLOBALClaimed by RedransomwareFirst sighting
Posted to leak site Apr 19, 2024bd_8ec65ab6de02f2c7
Computer Equipment & Peripherals
Clustered 4 filings across 4 jurisdictions · filing window Apr 19, 2024 → Nov 21, 2024. View entity profile → Other incidents for this victim →
incident inc_a54d10c12cee4fa4 · 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
CA FEDERAL IN
Leak Site · SEC 10-K Item 1C · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Apr 5, 2024
Reported by SEC 10-K Item 1C filing
Apr 6, 2024
When the intrusion reportedly occurred, per the linked filings
Apr 6, 2024
Reported by CALIFORNIA AG filing
Computer Equipment & Peripherals
On April 5, 2024, Targus discovered unauthorized access by a threat actor to certain of its file systems. Targus activated incident response and business continuity protocols with external cybersecurity counsel and consultants. Containment measures temporarily disrupted Targus' business operations. The incident has been contained and systems recovery is ongoing. Regulatory authorities have been notified and law enforcement engagement is planned. The parent company does not currently expect material financial impact.
Targus notified consumers of a data security incident discovered on April 6, 2024. The incident involved unauthorized access to personal information, including names and Social Security numbers. Targus engaged cybersecurity experts for a forensic investigation and implemented additional security measures. Affected individuals are offered complimentary credit monitoring and identity protection services.
Targus reported a data breach to the Indiana Attorney General. The breach occurred on 2024-04-06 and was reported on 2024-11-21. 3 Indiana residents were affected. 750 individuals affected in total.
Affected (this filing):
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.