Town of Waxhaw Impacted by Cybersecurity Incident
Post Date:09/14/2025 8:42 p.m.
The Town of Waxhaw has unfortunately become the victim of a cybercriminal attack. Early Friday morning, September 12, 2025, we discovered irregularities in our systems and our IT department took immediate actions to protect our organization. Then IT staff immediately retained the services of the North Carolina Joint Cybersecurity Task Force, a team of outside experts from the NC National Guard, the NCLGISA Cybersecurity Strike Team, NC Emergency Management, and the NC Department of IT, to launch a forensic investigation and help secure our servers.
It is important to share that our Town has emergency preparedness plans specifically for situations like these, and at no time did any life safety services cease to operate. All emergency services have been fully operational throughout the incident.
Our dedicated IT professionals are working diligently with some of the country’s leading experts in cybersecurity to return the Town of Waxhaw government systems back to normal as quickly as possible, and they are making incredible progress. Based on the preliminary investigation, the malicious activity performed by cybercriminals on our Town network was designed to access our systems to create system disruptions.
We can confirm the criminals were able to access some of the Town servers, but we do not have any confirmation that data containing personal information was taken.
We are operating the Town of Waxhaw Government under normal hours, but some services may be impacted. Thankfully, many of our critical functions are operational due to the progress our IT department has made to modernize and secure our technical infrastructure. Town staff have contingency plans for using alternative methods to transact public business in those limited instances.
Please understand that our priority is the safety and security of the Waxhaw community. We are committed to addressing the situation quickly and responsibly. We appreciate your patience as we work to resolve this issue.
Return to full list >>