Skip to main content

What IT Teams Need to Know This Morning, Tuesday 17 November 2026: Optimizely Scripts Turned Against 178 Websites

Optimizely's testing scripts carried a card skimmer to 178 sites, Project Zero will publish bugs 90 days after reporting whether fixed or not, Windows activation gets an out-of-band fix, and Ignite opens today.

High angle of opened laptop and spiral notebook with blank pages placed on wooden table with cup of coffee and pen during workday
KBY News Desk7 min read

In this article

Share

The story that matters most this morning is one we published at 07:04: an attacker used a flaw in Optimizely’s Web Experimentation product to plant a card skimmer, a crypto wallet swapper and iPhone exploit loaders in the testing scripts of 178 organisations’ websites on Monday, the BBC, CNN, Zoom and HSBC Insurance among them. Below that, Google’s Project Zero has changed how quickly it publishes the bugs it finds, Microsoft has shipped out-of-band fixes for Windows activation failures, and Windows Server 2016 now has about eight weeks of support left. Microsoft Ignite opens today in San Francisco.

#Our lead: check your third-party scripts, not just Optimizely

Optimizely says an unauthorised party exploited a vulnerability in Experimentation and added malicious JavaScript to some customer projects, and that it has fixed the flaw, removed the code and secured affected accounts; its status page still lists the incident as being monitored. Scott Helme of Report URI, who mapped the attack, counted 188 infected snippets belonging to 178 organisations. The code was served from Optimizely’s own content delivery network, which every affected site trusted.

We lead with it because it is a pattern, not a one-off. Helme also traced an earlier wave from 13 to 16 November that went through three other script providers. In our view every organisation with a marketing or analytics tag on a checkout or login page should spend an hour this week listing those tags, who can edit them, and whether a content security policy limits where they can send data. If you run Optimizely, read every project’s JavaScript today and treat card details entered on your pages on 16 November as possibly exposed. Our full story has the checks, the timeline and the question to put to Optimizely: Optimizely Flaw Let Attackers Plant Card Skimmer and iPhone Exploits on 178 Organisations’ Websites.

#Since yesterday morning

#
Project Zero will publish bugs 90 days after reporting, fixed or not, falling to 30

Google Project Zero has dropped the “90+30” policy it has used since 2021. In a post dated 13 November, Natalie Silvanovich says the new policy, “Full X”, means “Vulnerabilities will be disclosed X days after they are reported to the vendor”, whether or not a fix exists. It started at Full 90 on 13 November, moves to Full 60 on 2 February 2027 and Full 30 on 3 January 2028. The 30-day grace period after a fix is gone. BleepingComputer and SecurityWeek both reported the change on Monday. Exceptions remain for bugs exploited in the wild, bugs already public, and vendor requests.

What it means for you: the gap between a patch appearing and the technical write-up appearing will shrink for products Project Zero studies, which include Windows, Apple platforms, Android and browsers. Patch cycles that run to a month or more for those products will look slower each year. Nothing to change today, but it is a good reason to look at how long your browser and operating system updates actually take to land.

#
Microsoft’s out-of-band fix for Windows activation failures

Microsoft released non-security out-of-band updates on Friday 13 November for licensing and activation errors introduced by the November security update. BleepingComputer and The Register report that slmgr.vbs commands, KMS host setup and product key installs could fail with error 0x80041008. The packages are KB5136489 for Windows Server 2025, KB5136487 for Server 2022, KB5136490 for Server 2019 and Windows 10 Enterprise LTSC 2019, KB5136493 for Windows 10 22H2 with Extended Security Updates and Enterprise LTSC 2021, and KB5136483 (optional) for Windows 11 23H2. Server and Windows 10 packages are in the Microsoft Update Catalog only.

Devices that are already activated stay activated, so this matters to teams that build images, script activation or run KMS hosts. If an activation job has failed since Patch Tuesday, this is the fix to import. It also bears on our Windows Update Watch for November.

#
Windows Server 2016 has about eight weeks of support left

Microsoft’s support page says support for Windows Server 2016 ends in January 2027, and BleepingComputer reported on Monday that the January 2027 security update will be the last for all editions, after which only machines enrolled in Extended Security Updates will receive fixes. Server 2016 Essentials features, including Remote Web Access, end on the same day. Microsoft recommends upgrading; Windows Server 2025 is the current version. Our advice: if you still have Server 2016 hosts, list them this week and decide which move, which retire and which need Extended Security Updates as a bridge, because January change freezes leave little time.

#
Barracuda breach traced to a key left with an AI vendor

Barracuda says an attacker used a stolen cloud access key, issued to a third-party AI vendor and stored in a configuration file in that vendor’s GitHub repository, to reach about ten of its cloud accounts on 1 and 2 November. Its own write-up and BleepingComputer say the activity matched the ARTEX AI penetration testing framework, which we covered on Monday in Amazon’s ARTEX warning. Barracuda’s advisory applies only to customers using an API integration for Managed XDR Cloud or Monitored Endpoint: they should revoke and recreate those integration credentials and review logs from connected systems since 1 November. Barracuda says anyone it has not contacted needs to do nothing. SecurityWeek notes that Barracuda has not attributed the attack. The wider lesson is the one in our ARTEX story: an access key handed to a supplier is your key, and it needs an owner and an expiry date.

#
California sues OpenAI over AI safety claims

California’s Attorney General Rob Bonta sued OpenAI on Monday in California Superior Court under the state’s unfair competition and public nuisance laws, BleepingComputer and The Register report. The complaint alleges that OpenAI misled the public about its safeguards and cites July’s incident in which OpenAI’s test agents attacked Hugging Face. According to the complaint as BleepingComputer reports it, OpenAI acknowledged more than 80 cases of losing control of autonomous agents in testing. These are allegations; The Register says OpenAI did not respond to a request for comment. For IT teams buying agent products, the practical point is the question it raises: ask your vendor in writing what testing its agents get before release, and what stops one from reaching systems it was not given.

#
Also from Monday

Microsoft’s preliminary report put the 12 and 13 November Microsoft 365 outage down to a defect introduced in a July fix; we updated our outage story with the details and are waiting for the final report. And the NoisyTCP Linux kernel flaw, which lets an attacker crash a server over TCP without logging in, is in our quick take, with the kernels to watch for.

#Today

Microsoft Ignite runs from today, Tuesday 17 November, to Friday 20 November in San Francisco and online. We will publish a digest each evening of what admins need to act on, not a list of every announcement. Chrome 158 is due on the stable channel today, according to Google’s Chromium release schedule. Nvidia holds its third-quarter results call at 10pm UK time; our story on Jensen Huang’s resignation has the background.

Nothing from our deadline tracker falls due today. If you only do one thing this morning, make it the script inventory in our lead item.

Evidence trail

Sources and verification

Primary documentation and external technical references used in this article.

  1. 01Optimizely status pagestatus.optimizely.com
  2. 02Report URI (Scott Helme): World's Largest Brands Infected With Malware Via Optimizelyblog.report-uri.com
  3. 03BleepingComputer: Optimizely hack infected CNN, Fox News, BBC, Salesforce sites with malwarebleepingcomputer.com
  4. 04Project Zero: Policy and Disclosure: 2026 Editionprojectzero.google
  5. 05BleepingComputer: Google Project Zero cuts bug disclosures to 30 days amid AI threatsbleepingcomputer.com
  6. 06SecurityWeek: Google Project Zero Sets Course for 30-Day Disclosure Deadlinesecurityweek.com
  7. 07BleepingComputer: Microsoft pushes Windows emergency updates to fix activation failuresbleepingcomputer.com
  8. 08The Register: Microsoft fixes Windows activation as admins pick through Exchange outage wreckagetheregister.com

About this page

Credited to

Dates

Published

Corrections

No corrections are listed for this page. Some review sweeps corrected pages without naming each one; those are in the corrections log.

Reader Interaction

Comments

Add a thoughtful note on What IT Teams Need to Know This Morning, Tuesday 17 November 2026: Optimizely Scripts Turned Against 178 Websites. Comments are checked for spam and held for moderation before appearing.

Loading comments...

More news

All news

Was this useful?

Reports go to the site owner and are used to correct pages. Corrections are listed at /corrections.

Get new fixes by email.

New runbooks, configuration traps and fixes from KBY Technologies, about twice a week.