MalwareGovernmentGovernmentRansomwareData ExfiltratedData EncryptedRansom DemandedCustomer Data InvolvedPIIEmploymentLowContained

Town of Apex

bd_ac38b669739d9be2 · schema v1 · pii pii-v1

Severity

Low

Discovered

Jul 2, 2024

Filed

Mar 30, 2026

To disclose

—

Affected

Not disclosed

Linked

5 filings

Confidence

65%

Full breach record for Town of Apex →

Town of Apex experienced a ransomware incident in June 2024, discovered on July 2, 2024. Unauthorized actors accessed systems from June 23 to July 2, 2024, encrypting data and exfiltrating it to a cloud provider. The Town engaged the FBI, obtained a court order to retrieve data, and notified affected individuals. Impacted data included names and employment status.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 9 days

Jun 23, 2024

Begins

Jul 2, 2024

Discovered

Mar 30, 2026

Filed

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

Linked disclosures

Why this link?

Regulatory filings (4) · sorted by filing gap

Massachusetts State AGbd_399263c65fe910fc2026-03-30Verified
Indiana State AGbd_4a934c48207f171d2026-03-30Candidate
Indiana State AGbd_5cce7f628cd5a86a2026-03-30Candidate
New Hampshire State AGbd_26c16ad80a169c992026-04-06 · +7dVerified

Name: Town of Apex
norm: town of apex

Name: Town of Apex
norm: town of apex
Industry: Governmentllm

Discovered: Jul 2, 2024
Breach occurred: Jun 23, 2024 – Jul 2, 2024
Undetected for: 9 daysoccurrence → discovery
Materiality determined: —
Notification sent: Mar 30, 2026
Affected individuals: Not disclosed
Data types: PIIEmployment
Attack vector: Ransomware
MITRE ATT&CK: T1486 Data Encrypted for ImpactT1041 Exfiltration Over C2 Channel
Threat actor: ExternalFinancial
Regulator citations: reported this Incident to relevant government agencies

During the incident: Took systems offline
Engaged data security and privacy professionals
Notifying federal law enforcement
Worked with the FBI
Petitioned the Wake County Superior Court and was granted a Temporary Restraining Order
Worked with a trusted third-party data analytics team
Conducted an in-depth review of the impacted data
Changes made: Changing passwords
Strengthening authentication controls
Enhancing endpoint detection and monitoring capabilities
Regularly monitoring for potential security threats
Managing access to our systems
Source: Quoted from the filing itself, not independently verified.

Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 5 filings · 4 states

View merged incident ↗

Massachusetts State AGMar 30 · first

Indiana State AGMar 30 · first

Nebraska State AGMar 30 · first · this page

New Hampshire State AG+7d

Pattern: first filing Mar 30 (MA), last Apr 6 (NH) — a 7-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://nebraska.gov/ago/data-breach/documents/a744c555-fe6c-40e1-873d-67cc748cc2e5.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Mar 30, 2026
Raw hash: 6e2e8d65e517b10beee006880270fb3758a7f9f7543c92f2cdc885fae6b31801

Linked disclosures

Regulatory filings (4) · sorted by filing gap

Reporting entityTown of Apex

Victim entityTown of Apex

Incidentdiscovered Jul 2, 2024

Stated responseTook systems offline

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancenebraska.gov