The websites kept working. Behind the scenes, our team was dealing with a compromised software update.
On the evening of September 15, 2026, several clients across our managed website portfolio needed attention after a premium software developer reported a security compromise. Our team responded almost immediately, investigated the installations, addressed the affected website, and checked the other sites using the same software.
The sites experienced no downtime during the response. Our checks identified no evidence of client data exposure or compromise of the underlying server infrastructure. The clients did not have to diagnose the problem, chase a software developer, or coordinate the cleanup themselves. [2]
This is exactly why we offer actively managed website security. The work matters most when clients never see the problem in the first place.
Even Carefully Selected Software Can Be Compromised
The software involved was Admin Menu Editor Pro, a paid WordPress application we use on some websites to help organize and manage the administrative back end. It helps make the behind-the-scenes tools easier to navigate and manage.
According to the developer, an attacker compromised its distribution system and introduced malicious code into an update labeled version 2.35. A subsequent version, 2.36, was also compromised. The developer identified earlier releases as outside the affected versions. [1]
This was a software supply chain attack: the threat arrived through a source normally trusted to deliver legitimate software updates. It was not simply a case of someone neglecting an old website.
We are extremely selective about the software used on the TownNexus platform. But careful selection is the first layer of protection, not the last. A paid license, an established developer, and useful features do not make any application immune to compromise.
Premium software is not a security guarantee. Neither is a new version number.
An After-Hours Response, Not a Next-Day Ticket
By 6:28 p.m. Eastern on September 15, our team was responding to the issue. Information from the developer, security reporting, and our own security systems informed the review. We did not wait for a client to report a problem or for the next business day to begin.
On the affected website, our team took immediate containment and corrective measures, isolated and removed the affected software and related malicious files, and began deeper security checks. We performed multiple scans at both the server and website level rather than relying on one system or a quick look at the homepage.
At 9:33 p.m., our server team completed the final follow-up scan, reported that no malicious code was detected, and closed the malware case. Website operation continued without interruption throughout the response. [2]
The visible result was an ordinary evening for the client. Behind that result were investigation, containment, remediation, and repeated verification. An unchanged homepage was not our definition of a completed security review.
We Checked the Unaffected Sites, Too
Our review did not stop with the website that required corrective action. Several other managed clients used the same application, so their installations were checked as well.
Those reviews confirmed that the other sites were not running the affected software versions. They did not require the same cleanup, but confirming that distinction was part of the security work. We also prepared client updates explaining the findings and the precautions being taken. [2]
There is a meaningful difference between a site that has been checked and found outside the affected versions and a site whose owner simply has not noticed anything unusual. The first is a finding. The second is an assumption.
Automatic Updates Are Not a Complete Security Plan
Keeping software updated is important. WordPress itself recommends maintaining current plugins, reviewing available updates, and keeping a backup before making changes. [4]
But enabling automatic updates and assuming security has been handled skips a critical part of the job: understanding what is being installed and what the security community is reporting about it.
This incident illustrates the problem. The compromised code was distributed as an update. An installation could appear current while containing a malicious release. [1]
An automatic update can install software. It cannot, by itself, provide an accountable response to a compromised software supplier.
That is not an argument for disabling every automatic update or leaving known vulnerabilities unpatched. Automation has a useful role. It needs informed oversight, monitoring, backups, and a process for responding when an update itself becomes the concern.
A monthly report saying that everything was updated is not the same as knowing someone reviewed the relevant security notices, checked which sites were affected, and acted on the findings.
We Monitor the Industry, Not Just the Server
Every day, malicious actors and automated systems attempt to gain access to websites and other online systems. Login attacks and attempts to exploit vulnerable software are recurring activity, not rare events reserved for large organizations. Wordfence’s threat reporting documents this sustained activity across the websites it protects. [3]
Our team invests substantial time in following developer notices, independent security research, vulnerability reports, and industry developments. We connect that information to the applications actually running on the sites we manage.
That work helps answer practical questions: Does this notice apply to our software? Which versions are involved? Which clients need intervention? Is a proposed replacement release trustworthy?
Monitoring is not just receiving an email or watching a dashboard. Its value comes from interpreting the information and taking the appropriate action.
A Replacement Release Still Needs Verification
The compromise of a second release reinforced why we would not treat a replacement download as sufficient reassurance on its own. [1]
For this application, further updates are on hold pending independent third-party verification that the replacement software is clean and the developer’s distribution system has been secured. Monitoring continues while that review remains open.
This is a targeted precaution for the affected application, not a suspension of routine security maintenance. If the issue cannot be satisfactorily resolved, we will replace the application rather than keep clients dependent on an unresolved risk.
The decision is about more than installing the next version. It is about whether the source delivering that version can be trusted again.
Why This Matters for a Small Town
For a municipality, website availability is not just a technical statistic. It is a resident finding a meeting agenda after work, checking a public notice, or looking for the right department without waiting for the office to reopen.
A smaller town should not have to turn its clerk or administrator into a software security analyst to keep those services available. Nor should someone on staff have to watch industry advisories all evening and decide whether a newly released application is safe to install.
That technical oversight is part of the value of a managed service. The municipality can focus on serving residents while the team responsible for its website handles the investigation and response.
This Is What Ultimate Defense and NexusGuard Are For
Our Ultimate Defense website security services bring together layered protection, threat monitoring, malware scanning, managed software updates, and backups. The goal is not simply to install security software. It is to maintain an active process for identifying and responding to threats.
Qualifying Ultimate Defense plans also cover investigation, remediation, and emergency response services of this type at no additional charge. That coverage has practical value when an unexpected security issue requires attention after normal business hours.
Within TownNexus, these protections are part of the broader NexusGuard managed hosting, security, and support system. Hosting, security, backups, monitoring, and ongoing technical support work together instead of becoming separate problems for municipal staff to coordinate. The specific protections and response coverage depend on the selected service level.
This incident required two kinds of work: containing and removing malicious software where it was found, and verifying that other clients were not running affected versions. Both mattered. So did the decision to keep monitoring and withhold further updates until they could be independently verified.
The result was no website downtime and no evidence of client data exposure in our review. That did not make the security work unnecessary. It made the work worth doing. [2]
A municipal website needs more than someone who can click Update. It needs a team paying attention to what happens next.
Sources and Technical Background
[1] Admin Menu Editor Pro: Developer security advisory for the September 14, 2026 incident, reviewed September 17, 2026. This article describes our managed response; it is not a substitute for the developer’s incident-specific recovery guidance.
[2] MACH4’s response narrative and client security communications for September 15-16, 2026. Client identities and site-specific details have been withheld.
[3] Wordfence: Quarterly WordPress Threat Intelligence Report, Q4 2025, published February 3, 2026. Referenced for background on recurring website attacks, detection, and layered protection.
[4] WordPress.org: Managing plugins and software updates. Referenced for update review and backup guidance.
