Threat Analysis: Optimizely Supply Chain Attack and ScreenConnect MSP Campaign, What UK SMBs Need to Know
This is your Daily Threat Analysis for the 17th of November 2026.
Two significant campaigns landed simultaneously this week, and the official coverage of each is treating them as separate events. They are not, in any meaningful sense, separate. Both exploit the same structural vulnerability in how smaller businesses receive IT services and run their web presence: third-party trust. You trusted the platform. The platform was the weapon.
Let us deal with each in turn, then explain why they belong in the same conversation.
The Optimizely Supply Chain Attack
On the 16th of November 2026, malicious JavaScript was distributed through the Optimizely Web experimentation platform to 178 organisations. The list of confirmed affected sites includes BBC, CNN, Fox News, Zoom, Salesforce, GitLab, IKEA, HSBC UAE, and Equifax. This is not a minor incident with a marginal victim list. These are organisations with dedicated security teams and substantial security budgets.
The malware was multi-purpose. According to research published by report-uri.com, it performed the following on affected sites: swapped cryptocurrency wallet addresses to redirect transactions to attacker-controlled addresses, skimmed payment card data from users transacting on affected pages, stole browser cookies and session screenshots, and deployed two iOS exploit kits, Coruna and DarkSword, targeting iPhone users visiting the compromised sites.
Optimizely subsequently confirmed that attackers had exploited a vulnerability in its Experimentation signup workflow to inject malicious code into customer projects. A follow-on investigation by infostealers.com identified the same malicious JavaScript appearing across three additional web services: Kissmetrics, StorifyMe, and minute-ly. The scope of the compromise extended to 188 affected snippets across the confirmed 178 organisations.
The advisory coverage of this incident focuses, understandably, on the large named organisations. What it does not say is this: the businesses most at risk from a supply chain injection of this type are not the large brands. The large brands have security operations centres. They have the budget to detect anomalous script behaviour, to implement Content Security Policies, to review third-party tag changes. The small business running Optimizely for A/B testing, or running any of the other four affected platforms for analytics, has none of that. And their customers, paying by card, visiting on an iPhone, are exposed just the same.
If you or your web developer uses Optimizely, Kissmetrics, StorifyMe, or minute-ly and you have not received direct communication from your vendor confirming the incident is resolved and your project is clean, treat your site as potentially compromised until you have verified the scripts currently loaded on your pages. If you have an e-commerce function, consider whether customers who transacted during the 16th of November should be notified as a precaution. The ICO’s breach notification obligation does not wait for your forensics provider to finish their report.
The ScreenConnect MSP Campaign: CVE-2026-84869
Running in parallel with the Optimizely incident, and with considerably less press coverage, is an active exploitation campaign targeting managed service providers through a critical vulnerability in ConnectWise ScreenConnect.
CVE-2026-84869 carries a CVSS score of 9.9. The vulnerability allows malicious guests in a remote support session to push files to the technician’s workstation and execute them with elevated privileges, without any authorisation requirement. That is a significant distinction: the attacker does not need to compromise the MSP’s credentials. They need only to establish a guest session on the ScreenConnect server and use the file transfer function that the tool provides legitimately.
According to Huntress research, between October and November 2026, attackers conducted a large-scale spray campaign across 42 MSP ScreenConnect servers, issuing 688,000 malicious file-transfer requests. That is not a targeted campaign. That is automation searching for unpatched instances at scale.
The second phase of the campaign, documented separately by both Huntress and Microsoft’s security team, involved fake guest sessions masquerading as legitimate computers. Between the 3rd and the 13th of November, attackers enrolled over 2,200 fake sessions across 118 ScreenConnect servers belonging to 109 MSPs and organisations. The fake sessions used cryptocurrency exchange-themed names, KUCOIN-SRV, BACKUP-PROBIT, and similar, and displayed screenshots of trading desktops to avoid casual detection. The majority of the connections originated from a single IONOS infrastructure provider.
The payload deployed through these sessions is SCKit, a worm documented by Microsoft. SCKit establishes persistence through scheduled tasks, deploys unauthorised remote-access clients, and propagates to customer-managed endpoints, the businesses whose IT is managed by the compromised MSP. This is the downstream effect that never makes the headline. The MSP is the victim in the trade press. Their customers are the actual victims in practice.
Microsoft’s security blog confirmed active SCKit deployment from the 11th of November onwards.
If your business uses a managed IT provider and that provider uses ConnectWise ScreenConnect for remote support sessions, you have two questions to ask them today. First: has CVE-2026-84869 been patched on your instance? Second: were there any unrecognised guest sessions on your ScreenConnect server between the 3rd and the 13th of November? If they cannot answer both questions with confidence, that is information you need before you assume your endpoints are clean.
If your IT provider tells you this does not affect you because you are too small, ask them how many of the 109 MSPs affected by this campaign thought the same thing.
The Microsoft 365 Phishing Campaign: Context
A third item worth noting, though lower priority than the two above: on the 13th of November, a high-volume phishing campaign used spoofed Microsoft 365 service-health notifications as lures. The emails claimed that messages had been held during a service disruption and would be deleted within 24 hours unless recipients acted. The sender domains used in the campaign were not Microsoft’s legitimate domains.
Microsoft’s security blog documented the campaign on the 16th of November. The credential-harvesting mechanism is straightforward and not technically sophisticated. The social engineering is. A notification that your email is about to be deleted creates time pressure and plausible authority simultaneously. Both are reliable mechanisms for bypassing rational evaluation.
The action here is straightforward: your staff need to know that Microsoft will not send unsolicited emails demanding urgent action to prevent message deletion, and that any email claiming to be a service-health notification should be verified through the Microsoft 365 admin portal directly, not through any link in the email itself.
Why These Incidents Belong Together
Supply chain attacks through trusted third-party tools, and attacks that weaponise MSP remote access infrastructure, share the same logic: they exploit the trust relationship that makes legitimate services useful. Optimizely is on your site because it provides value. ScreenConnect is on your MSP’s server because it makes remote support work. Both are now demonstrated attack surfaces.
The NCSC published guidance on third-party and supply chain risk years ago. The fact that 178 organisations running enterprise-grade web platforms were simultaneously compromised through a single vendor’s signup workflow tells you that guidance is not being operationalised. Not at the enterprise level, and certainly not at the SMB level where vendor due diligence conversations rarely happen at all.
The practical posture for UK SMBs coming out of today’s briefing is this:
- Review which third-party scripts currently load on your website. Your web developer can audit this in under an hour using browser developer tools or a service like report-uri.com’s CSP tooling. If you do not know what scripts are running on your site, that is the first problem to solve.
- Ask your MSP directly whether they use ConnectWise ScreenConnect, whether CVE-2026-84869 has been patched, and whether they observed any anomalous sessions in the first two weeks of November. Put the question in writing so the response is on record.
- Brief your staff on the Microsoft 365 lure campaign. Five minutes in a team meeting is sufficient. The lure is effective precisely because it sounds plausible; familiarity with the format is the best counter to it.
None of this requires specialist expertise or significant budget. It requires asking the right questions of the providers you already pay.
If the Threat Analysis is useful to you, follow the show wherever you listen so tomorrow’s briefing lands automatically, and pass it to someone who needs the heads-up. The people who most need this information are usually the ones who have not heard of it yet.