Confirmed breach. Intrusion Jul 25, 2024, discovered Oct 18, 2024 — the first regulatory filing landed 25 days later. 18,264 individuals reported across the linked filings.
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.
Regulatory clocksMaine✓ ME AG ≤30d · 25dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
18,264
Data types
2
PII · Government ID
Jurisdictions
2
IN ME
Linked filings
2
all State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Jul 25, 2024
When the intrusion reportedly occurred, per the linked filings
85 days
Breach discovered
Oct 18, 2024
Reported by MAINE AG filing
🏎️Indiana State AGFirst filinglinked via multistate filing link · 100%
Pallet Logistics of America dba PLA reported a data breach to the Indiana Attorney General. The breach occurred on 2024-07-25 and was reported on 2024-11-12. 75 Indiana residents were affected. 18,264 individuals affected in total.
Pallet Logistics of America d/b/a PLA, a Dallas TX-based company, experienced an external system breach in which an unauthorized actor acquired files stored within legacy systems. Unusual activity was discovered on September 6, 2024; a comprehensive review confirmed on October 18, 2024, that personal information (names, Social Security numbers, and/or driver's license numbers) of 18,264 individuals—including 3 Maine residents—may have been compromised. Notifications were sent November 12, 2024.
Affected (this filing): 3
ME AG ≤30d · 25d
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.