Confirmed breach. Intrusion Oct 27, 2025–Nov 11, 2025, discovered Nov 11, 2025 — the first regulatory filing landed 79 days later (flagged late). 278 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 claimConfirmedEnforced
Affected (total reported)
278
Data types
—
Jurisdictions
2
IN VT
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Oct 27, 2025 → Nov 11, 2025
When the intrusion reportedly occurred, per the linked filings
Breach discovered
Nov 11, 2025
Reported by VERMONT AG filing
79 days
🍁Vermont State AGFirst filinglinked via multistate filing link · 100%
GS Engineering notified consumers of a data breach where unauthorized access occurred between Oct 27 and Nov 11, 2025. Suspicious activity was detected on Nov 11, 2025. Files containing names and other personal info were copied. The company engaged forensic specialists, notified federal law enforcement, and is offering credit monitoring services.
GS Engineering reported a data breach to the Indiana Attorney General. The breach occurred on 2025-10-27 and was reported on 2026-01-29. 1 Indiana residents were affected. 278 individuals affected in total.
Affected (this filing): 278
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.