HackingGovernmentGovernmentStolen CredentialsData ExfiltratedCustomer Data InvolvedPIIIdentity (basic)Government IDMediumContained

Haverford Township

bd_17333fbcbcdb23ed · schema v1 · pii pii-v1

Severity

Medium

Discovered

Apr 17, 2023

Filed

Apr 2, 2024

To disclose

50 weeks

Affected

1state residents only

Linked

7 filings

Confidence

66%

Full breach record for Haverford Township →

Haverford Township, PA notified individuals of a cybersecurity incident detected on April 17, 2023, involving unauthorized network access and potential exposure of personal information including SSNs. Forensic investigators could not determine the volume of data accessed. The Township engaged external professionals, conducted a manual review, and is offering complimentary credit monitoring services to affected individuals.

J jump to incidentP pin to compareR raw source

Incident timeline

discovery → filing · 50 weeks / 351 days

Apr 17, 2023

Discovered

Apr 2, 2024

Filed

vs. sector median

+39 wks slower

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

Linked disclosures

Why this link?

Regulatory filings (6) · sorted by filing gap

Indiana State AGbd_237e2e21f6f1369d2024-04-02Verified
Delaware State AGbd_34b43e9d32eed3982024-04-02Verified
Maine State AGbd_7cb9640dac11f63e2024-04-02Verified
Vermont State AGbd_93934bd34326e86e2024-04-02Verified

Show 2 more filings ↓up to 6d gap

Massachusetts State AGbd_fc210c8679d3ed382024-04-02Verified
New Hampshire State AGbd_56c55cb90a30c29b2024-04-08 · +6dVerified

Name: Haverford Township
norm: haverford township
Domain: havtwp.org

Name: Haverford Township
norm: haverford township
Domain: havtwp.org
Industry: Governmentllm

Discovered: Apr 17, 2023
Materiality determined: —
Notification sent: Apr 2, 2024
Affected individuals: 1state-resident count only
Data types: PIIIdentity (basic)Government ID
Attack vector: Unauthorized Access
MITRE ATT&CK: T1078 Valid AccountsT1119 Automated Collection
Threat actor: External
Initial access: valid_credentials

During the incident: Immediately took steps to secure the network and mitigate against any additional harm
Engaged external cybersecurity professionals experienced in handling these type of incidents to conduct an investigation
Conducted a thorough and extensive manual review of the potentially impacted data
Providing you complimentary access to Identity Defense Complete
Changes made: Continually evaluate and modify our practices and internal controls to enhance the security and privacy of your information
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 50 weeks(351 days from discovery to filing)
Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 7 filings · 7 states

View merged incident ↗

Indiana State AGApr 2 · first

Delaware State AGApr 2 · first

Maine State AGApr 2 · first

Vermont State AGApr 2 · first

Massachusetts State AGApr 2 · first

Montana State AGApr 2 · first · this page

New Hampshire State AG+6d

Pattern: first filing Apr 2 (IN), last Apr 8 (NH) — a 6-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://dojmt.gov/wp-content/uploads/OCP/Consumer-notification-letter-1258.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Apr 2, 2024
Raw hash: 4df9ecefbed367495d9e32a5bb6e8da4b1ebbc8e812e49065127a0f52916bbf7

Linked disclosures

Regulatory filings (6) · sorted by filing gap

Reporting entityHaverford Township

Victim entityHaverford Township

Incidentdiscovered Apr 17, 2023

Stated responseImmediately took steps to secure the network and mitigate against any additional harm

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov