A flaw in Optimizely’s signup flow exposed visitors to malicious scripts, while active attacks against N-able N-central and continued ScreenConnect activity put remote-management systems on alert.
A vulnerability in Optimizely’s Web Experimentation account-signup flow let an attacker inject malicious JavaScript into customer projects, exposing visitors to harmful code on otherwise legitimate websites. Optimizely says it blocked access to the vulnerable path, fixed the flaw and removed the injected code. Monitoring continues. Report URI researchers found 188 infected files among 1,611 scripts examined, affecting 178 organizations.
The incident, reported November 16 and updated November 17, illustrates how a weakness in a third-party web platform can reach customers across many unrelated sites. Businesses use external scripts for functions such as testing and personalization; compromise of the platform supplying them can place malicious code on websites without a direct breach of each site’s systems.
BleepingComputer confirmed delivery or attempted delivery on sites including Zoom, CNN, Fox News, the BBC, Salesforce, GitLab, KLM, Smartsheet, Stamps.com and IKEA. The payload could replace cryptocurrency wallet addresses, capture payment-card data, collect cookies and screenshots, and attempt to load iOS exploit kits. Reporting does not establish that every listed site’s visitors were compromised or that every payload succeeded.
Organizations using Optimizely should check customer projects for unauthorized scripts and confirm the injected code is gone. Review website and payment activity dating to November 16, including changes to wallet addresses, and examine relevant account logs. Rotate credentials if exposure is plausible, especially accounts that can alter site code or access payment systems. Retain logs for investigation rather than relying only on a clean page view.
N-able’s N-central remote-monitoring platform is also under attack. Exploited flaws have been used to download scripts that install XMRig Monero miners. Because remote-management tools can administer customer systems, a compromised N-central server can create risks beyond the server itself. N-able released N-central 2026.4 Hotfix 3 to address additional critical flaws, but reporting does not establish that it eliminates the exploited attack chain.
N-central operators should install the hotfix but also investigate their systems. Disable Legacy APIs if they are not needed, restrict access to management interfaces and review logs for suspicious requests to `/dms/services/ServerUI`. Look for unexpected scripts or processes and unusual sustained resource use that could indicate mining. If activity appears suspicious, preserve logs and examine both the N-central server and systems it manages.
ConnectWise says its investigation into unauthorized access to partner ScreenConnect environments is complete. However, it reports continued activity against on-premises environments where identified third-party extensions remained enabled and ScreenConnect was not updated. The company recommends technician clients run version 26.6.5 or later. Administrators should verify installed versions, disable the identified extensions and review access logs and system changes. The end of the vendor’s investigation does not confirm that every customer installation is secure.
Small IT teams should inventory internet-facing Optimizely, N-central and ScreenConnect deployments, including those managed by outside providers. Apply available fixes, remove unnecessary integrations and check for signs of misuse. Remote-management systems warrant priority because their administrative reach can turn one exposed service into a route to many machines. Record which systems have been checked and escalate suspicious findings rather than assuming a patch alone resolves an intrusion.
The supplied reporting also mentions an urgent Chrome zero-day but gives no vulnerability identifier, affected versions, patch status or source details. Administrators should check Google’s official Chrome security updates and apply updates according to the vendor’s guidance. The available information does not support more specific remediation advice.

