HackingEducationEducationStolen CredentialsCapture Stored DataData ExfiltratedCustomer Data InvolvedTargetedPIIIdentity (basic)LowContained

Greater Lawerence Technical School District

bd_960cb2f32a07d669 · schema v1 · pii pii-v1

Severity

Low

Discovered

Nov 8, 2024

Filed

Mar 5, 2025

To disclose

17 weeks

Affected

221state residents only

Linked

6 filings

Confidence

65%

Full breach record for Greater Lawerence Technical School District →2 incidents on file

Greater Lawrence Technical School District (GLTSD) notified New Hampshire residents of a data breach involving unauthorized network access between Nov 4-9, 2024. GLTSD discovered unusual activity on Nov 8, 2024. Personal information of 221 NH residents was potentially accessed. GLTSD secured systems, updated training, and offered credit monitoring via Experian.

J jump to incidentP pin to compareR raw source

Leak gap clock⏱ Leak >90d17 weeks discovery → filing

Incident timeline

undetected · 4 days

discovery → filing · 17 weeks / 117 days

Nov 4, 2024

Begins

Nov 8, 2024

Discovered

Dec 10, 2024

Scope determined

Mar 5, 2025

Filed

vs. sector median

+8 wks slower

This filing is one of 6 about the same incident.View merged incident

A leak claim by abyss about this victim predates this filing by 99 days.View originating leak claim

Linked disclosures

Why this link?

Ransomware claims (1)

Leak Siteabyssbd_820bac83e8c0bc172024-11-25 · +99dVerified by operator

Regulatory filings (4) · sorted by filing gap

Maine State AGbd_9dc3f488ba551ea02025-03-05Verified by operator
Massachusetts State AGbd_7d3eaa9a44f2a5f42025-01-17 · +47dVerified by operator
Maine State AGbd_aeafeb564cc205902025-01-17 · +47dVerified
New Hampshire State AGbd_d413e3b453f15bd02025-01-17 · +47dVerified

Name: Greater Lawerence Technical School District
norm: greater lawerence technical school district
Domain: glts.net

Name: Greater Lawerence Technical School District
norm: greater lawerence technical school district
Domain: glts.net
Industry: Educationllm

Discovered: Nov 8, 2024
Breach occurred: Nov 4, 2024 – Nov 9, 2024
Undetected for: 4 daysoccurrence → discovery
Materiality determined: Dec 10, 2024
Notification sent: Mar 5, 2025
Affected individuals: 221state-resident count only
Data types: PIIIdentity (basic)
Attack vector: Unauthorized Access
MITRE ATT&CK: T1078 Valid AccountsT1041 Exfiltration Over C2 Channel
Threat actor: ExternalFinancial
Regulator citations: Providing written notice of this incident to relevant state regulators
Initial access: valid_credentials

During the incident: Initiated an investigation into the nature and scope of the impact
Moved quickly to respond, secure the systems involved, assess the security of our network, and investigate the event
Providing access to credit monitoring services for individuals whose personal information was potentially affected by this incident, at no cost to these individuals
Providing impacted individuals with guidance on how to better protect against identity theft and fraud
Providing written notice of this incident to relevant state regulators
Changes made: Working to implement additional safeguards and training to its employees
Reviewed our policies, procedures, and security tools, and updated our employee training program
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 17 weeks(117 days from discovery to filing)
Compliance flags: Leak >90d
Discovery-date grounding: letter-groundedThe discovery date is the detection date narrated in the notification letter — the defensible tier.

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 5 filings · 3 states

View merged incident ↗

Massachusetts State AGJan 17 · first

Maine State AGJan 17 · first

New Hampshire State AGJan 17 · first

Maine State AG+47d

New Hampshire State AG+47d · this page

Pattern: first filing Jan 17 (MA), last Mar 5 (NH) — a 47-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source URL: https://mm.nh.gov/files/uploads/doj/remote-docs/greater-lawrence-technical-school-district-20250305.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Mar 5, 2025
Raw hash: a00b7ac4cb25f388008818b7600dfa3f33591c8b2c15e514fb3d08a3ebd64b91

Linked disclosures

Ransomware claims (1)

Regulatory filings (4) · sorted by filing gap

Reporting entityGreater Lawerence Technical School District

Victim entityGreater Lawerence Technical School District

Incidentdiscovered Nov 8, 2024

Stated responseInitiated an investigation into the nature and scope of the impact

ComplianceLeak >90d

Extraction provenanceno artifact recorded

Source provenancemm.nh.gov