Confirmed breach. Intrusion Aug 1, 2025–Aug 31, 2025, discovered Aug 1, 2025 — the first regulatory filing landed 80 days later (flagged late). 34 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 clocksVermont✗ VT AG >45 bdayFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmoderate sensitivity
Affected (total reported)
34
Data types
2
Identity (basic) · Financial account
Jurisdictions
2
IN VT
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach discovered
Aug 1, 2025
Reported by VERMONT AG filing
Breach window
Aug 6, 2025
When the intrusion reportedly occurred, per the linked filings
75 days
🏎️Indiana State AGFirst filinglinked via multistate filing link · 100%
Galco Industrial Electronics Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2025-08-06 and was reported on 2025-10-20. 1 Indiana residents were affected. 34 individuals affected in total.
Galco Industrial Electronics, Inc. notified consumers on October 20, 2025, that a malicious cyberattack on its third-party payment processor in August 2025 may have exposed customer names, addresses, and payment card details. Galco engaged security professionals, removed malicious code, and updated credentials.
VT AG >45 bday
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.