Threat Analysis: Optimizely Supply Chain Attack, ScreenConnect MSP Flaw, and ConnectWise Credential Abuse

Threats & Attacks

Threat Analysis: Optimizely Supply Chain Attack, ScreenConnect MSP Flaw, and ConnectWise Credential Abuse

This is your Daily Threat Analysis for the 18th of November 2026.

Three separate incidents, all confirmed active, all with direct relevance to UK businesses that use managed IT providers or third-party web platforms. I am leading with the Optimizely supply chain compromise because the scale of it warrants your immediate attention, but the ScreenConnect and ConnectWise stories are arguably more structurally important for SMBs over the medium term. All three tell the same story: your attack surface now includes your suppliers’ code, your suppliers’ tools, and your suppliers’ credentials.


1. The Optimizely Supply Chain Compromise: What Actually Happened

On the 16th of November 2026, attackers exploited a vulnerability in Optimizely’s Experimentation signup workflow to inject malicious JavaScript into customer projects. According to researchers at report-uri.com who published detailed analysis, the malicious code was distributed to 178 organisations and affected 188 snippets. The list of compromised sites reads like a register of household names: BBC, Zoom, CNN, Fox News, Salesforce, GitLab, IKEA, HSBC UAE, and Equifax.

The payload was not a single-purpose tool. It was a multi-function kit:

  • Card skimming: payment card data entered on affected sites was silently exfiltrated.
  • Cryptocurrency address swapping: if a visitor copied a crypto wallet address, the clipboard content was replaced with an attacker-controlled address.
  • Cookie theft and screenshot capture: session data harvested without any interaction.
  • iOS exploit delivery: Mobile Safari users were silently routed to infrastructure hosting the Coruna and DarkSword exploit kits. No user interaction required. Just visiting the site on an iPhone was sufficient to trigger the exploit chain.

The iOS component is the detail that should concern you most. CVE-2022-48503, a WebKit vulnerability, features in the indicators associated with this campaign. The DarkSword and Coruna kits are designed for zero-click or minimal-interaction exploitation of Mobile Safari. Zimperium’s analysis confirms that at least 21 major websites were routing iPhone users to this infrastructure.

The compromise lasted for approximately 19 hours before Optimizely contained it. Nineteen hours is a long time when BBC News has tens of millions of monthly visitors and an unknown proportion of them are on iPhones.

What the coverage is not saying

The public statements have focused, reasonably, on the named brands. What is receiving less attention is the downstream exposure. HSBC UAE is listed. Equifax is listed. These are financial services organisations. If a visitor authenticated to an HSBC service during the compromise window and had session cookies harvested, the downstream risk to that individual extends well beyond the 19-hour window.

The investigation by infostealers.com also documents that the compromise was not confined to Optimizely. Three other JavaScript providers, Kissmetrics, StorifyMe, and minute-ly, were also affected. This is not one vulnerability in one product. This is a coordinated operation targeting the third-party JavaScript supply chain at multiple points simultaneously.

If your business or any third party you work with uses tag managers, A/B testing platforms, analytics scripts, or any externally hosted JavaScript, and virtually every modern website does, your exposure to this category of attack is non-trivial.

What to do

  • If you operate a website that uses Optimizely, Kissmetrics, StorifyMe, or minute-ly, review whether your site was affected and check your Content Security Policy logs for unexpected external requests during the 16th of November 2026.
  • If you are an e-commerce operator, treat any transactions processed on the 16th of November as potentially compromised and consider notifying affected customers in line with your ICO obligations under UK GDPR.
  • Implement or review your Content Security Policy. A properly configured CSP will not prevent every supply chain attack, but it significantly limits the damage a malicious script can do by restricting where data can be sent.
  • Consider subresource integrity (SRI) checks for externally hosted scripts. If the script changes, the browser refuses to execute it.

2. CVE-2026-84869 in ScreenConnect: The MSP Attack That Becomes Your Attack

CVE-2026-84869 is a critical vulnerability in ConnectWise ScreenConnect with a CVSS score of 9.9. The flaw allows a malicious guest in a remote support session to push files to the MSP technician’s workstation and trigger their execution with elevated privileges, without any authorisation prompt.

Huntress has published detailed analysis of active exploitation. Between October and November 2026, attackers conducted what Huntress describes as a massive spray campaign across 42 MSP ScreenConnect servers, issuing 688,000 malicious file-transfer requests. In a documented incident on the 12th of November 2026, attackers successfully installed a commercial remote monitoring and management agent on a compromised technician workstation using this method.

Read that again. An attacker joined a support session, the kind an MSP technician opens to help you with a problem, and used that session to push malware onto the technician’s machine. The technician did not click anything. They did not approve the file transfer. The flaw bypassed the authorisation entirely.

Why this matters more than it appears

If your IT provider uses ScreenConnect to manage your systems, their technician workstations have privileged access to your network. Administrative credentials, remote access tokens, documentation about your infrastructure, all of it sits on or flows through those machines. A compromised MSP technician workstation is not an MSP problem. It is a direct path into every business that MSP supports.

The advisory attributes the exploitation to a tool tracked as SCKIT. The campaign has been running since at least October 2026, which means unpatched MSPs have had exposed attack surface for the better part of six weeks.

If your IT provider tells you this does not affect you because you are too small, ask them how many of the 42 affected MSP servers thought they were too small to be targeted. The attackers issued 688,000 requests. That is not targeted. That is automated, indiscriminate, and ongoing.

What to do

  • Contact your MSP today and ask, in writing, whether they use ConnectWise ScreenConnect and whether CVE-2026-84869 has been patched.
  • Request confirmation of the patched version number. Do not accept “we are aware of it” as an answer.
  • Ask your MSP what compensating controls are in place for technician workstations that hold privileged access to your environment, endpoint detection, privileged access workstations, session logging.
  • If you cannot get a straight answer, treat it as a material risk and escalate accordingly.

3. ConnectWise SkyKick Credential Abuse: Vendor Access at Scale

This is the quieter story of the three, and in some ways the one with the longest tail.

On the 15th of October 2026, a Microsoft 365 API credential belonging to ConnectWise Cloud Backup, formerly known as SkyKick, was compromised. The attacker used this single credential to authenticate and obtain Microsoft Graph access tokens across hundreds of M365 tenants. Huntress researchers observed the attacker moving through tenants in sorted GUID order, which indicates automated tooling and systematic enumeration rather than opportunistic browsing.

The CVE listed in the associated indicators is CVE-2025-11371, though the primary mechanism here is credential compromise rather than a software vulnerability per se. The compromised credential held permissions across customer tenants because that is how cloud backup products are architecturally required to work: they need broad access to back up your data.

What the advisory does not say

The public reporting focuses on what was observed: authentication events, Graph token issuance, tenant enumeration. What it does not enumerate is what the attacker did inside those tenants during the access window. M365 Graph access can include email, calendar data, SharePoint documents, Teams conversations, and Azure AD identity information depending on the permissions granted. Enumerating hundreds of tenants in GUID order suggests the goal was reconnaissance or data harvesting at scale, not targeted extraction from a single known victim.

For UK SMBs using any MSP that offers M365 backup through a ConnectWise or SkyKick product, this is worth raising directly with your provider. The question is not whether ConnectWise has revoked the compromised credential, they have. The question is what access occurred in your tenant during the period from the 15th of October onwards, and whether your M365 audit logs were reviewed.

What to do

  • Ask your MSP whether they use ConnectWise Cloud Backup (SkyKick) for your M365 environment.
  • Request a review of your M365 audit logs for unusual access events from external service principals between the 15th of October and the date ConnectWise confirmed remediation.
  • Review the third-party application permissions granted in your Azure AD tenant. Any service principal with broad Graph permissions is a potential pivot point if the credential is compromised upstream.
  • Consider implementing Conditional Access policies that restrict where service principal authentication can originate, even if your MSP pushes back on the operational overhead.

The Pattern Connecting All Three

Optimizely, ScreenConnect, SkyKick. Three different products. Three different attack vectors. One consistent theme: the attacker did not need to compromise your systems directly. They compromised something your suppliers trust, and your exposure followed automatically.

The NCSC has published guidance on supply chain security. The fact that three separate supply chain incidents are active in the same week, all with direct UK exposure, tells you everything about how seriously the guidance is being operationalised.

This is not a reason for paralysis. It is a reason to have a direct conversation with your IT provider this week. Not an email. A call. What products do you use? What was affected? What did you patch, and when?

If they cannot answer those questions, that is information too.


If this briefing is useful to you, follow the show wherever you listen so tomorrow’s analysis lands automatically, and pass it to whoever in your business or network needs the heads-up. The people who most need this information are rarely the ones looking for it.


Sources

SourceTitleURL
report-uri.comWorld’s Largest Brands Infected With Malware Via Optimizelyhttps://blog.report-uri.com/worlds-largest-brands-infected-with-malware-via-optimizely/
SOCRadarOptimizely Attack Hits Zoom, BBC, CNN With Skimmer, iOS Kitshttps://socradar.io/blog/optimizely-attack-hits-zoom-bbc-cnn-with-skimmer-ios-kits/
ZimperiumURGENT: iOS Exploits Are Being Actively Deployed via Poisoned JavaScript on BBC, Zoom, CNNhttps://zimperium.com/blog/urgent-ios-exploits-are-being-actively-deployed-via-poisoned-javascript-on-bbc-zoom-cnn-and-other-major-websites?hs_amp=true
CensysMCH and Caishen: supply chain poisoning pushes iOS exploitshttps://censys.com/blog/mch-and-caishen-supply-chain-poisoning-pushes-ios-exploits
Infostealers.comBeyond Optimizely: Malicious Scripts Traced Across Four Web Serviceshttps://www.infostealers.com/article/beyond-optimizely-malicious-scripts-traced-across-four-web-services/
HuntressCVE-2026-84869 in ScreenConnect Exploited to Run Malicious Files on MSP Technician Accountshttps://www.huntress.com/blog/cve-2026-84869-screenconnect-technician-exploitation
HuntressConnectWise (SkyKick) Vendor Credentials Abused in M365 Attackshttps://www.huntress.com/blog/vendor-credential-enables-unauthorized-access

Filed under

  • supply-chain-risk
  • msp-security
  • smb-security
  • credential-theft
  • vendor-risk
  • cloud-security
  • incident-response