For most of Monday afternoon and overnight into Tuesday, Australian time, visitors to some of the world’s biggest websites were served malware that could swap cryptocurrency wallet addresses, skim card numbers and, on older iPhones and iPads, try to hack the device. According to security firm Report URI, the code was slipped into scripts from Optimizely, a website testing service, and turned up on the sites of 178 organisations, including Zoom, the BBC, CNN and several Australian brands: Vodafone, TPG Telecom, Rest Super and HSBC Australia.
Optimizely says it has fixed the flaw that let the attacker in, and most of the malicious code was removed by Tuesday morning. Here is what happened, which Australian sites were on the list, and what to check if you visited one of them.
What happened
Optimizely Web Experimentation lets companies run A/B tests and personalise their websites. To do that, each customer’s pages load a small JavaScript file, called a snippet, from Optimizely’s servers. That snippet can include custom code that the customer writes in its Optimizely dashboard and that runs on every page.
Report URI, the company run by security researcher Scott Helme, says an attacker wrote their own code into that custom-code field in many customer projects. The rest of each file was untouched and was still delivered from Optimizely’s own servers, so the affected websites had no obvious reason to distrust it. As Report URI put it, “A website can be compromised through a third-party dependency without its own code or infrastructure ever being breached.”
Report URI says it checked 1,611 Optimizely snippets and found malicious code in 188 of them, belonging to 178 organisations. It says the real number is likely higher, because it could only check the snippets it was able to find. BleepingComputer independently analysed copies of the modified files and confirmed they had been altered to load an extra script from an attacker-controlled domain, and used urlscan.io records to confirm the script loaded, or tried to load, on sites including Zoom, GitLab, BBC, CNN and Salesforce.
When it happened, in Australian time
Report URI’s timeline is in UTC. Converted to Australian Eastern Daylight Time (UTC+11), which covers Sydney, Melbourne, Canberra and Hobart:
- About 3:20pm Monday 16 November: first Optimizely injection seen, on the BBC’s snippet (04:21 UTC).
- 12:43am Tuesday 17 November: a card skimmer is added to the attacker’s script (13:43 UTC).
- About 4:15am to 5am Tuesday: a second iOS attack server is added and an exploit kit is pushed to visits from iOS 18.6 or earlier (17:13 to 17:57 UTC).
- About 7:40am to 8:10am Tuesday: mass clean-up across affected snippets (about 20:40 to 21:10 UTC).
- 8:52am Tuesday: Report URI finds the code in just one of the 188 snippets, belonging to UK broadband provider TalkTalk (21:52 UTC).
If you are in Queensland, subtract an hour; in Adelaide, subtract half an hour; in Perth, subtract three hours. Report URI also notes that the attacker’s script was rebuilt 26 times during the day, so not every visitor received every feature at every point in that window.
What the malicious code did
Report URI, BleepingComputer and Cointelegraph, citing separate analysis by security firm StepSecurity, describe the same main functions:
- Crypto address swapping. The script looked for wallet addresses on the page and in the clipboard and replaced them with the attacker’s. If you copied an address from an affected page, or from anywhere else while that tab was open, you may have pasted the attacker’s.
- Card skimming. It watched for a card number, expiry date and security code typed into a website’s own form fields and sent them to the attacker. Report URI and StepSecurity say card fields shown inside a payment provider’s own embedded frame, such as Stripe or Adyen, were out of its reach.
- Cookie and screenshot theft. In some situations it sent the page address, cookies that were readable by scripts, and a screenshot of the page to the attacker.
- iPhone and iPad exploits. On iOS it loaded known exploit kits, Coruna for iOS 13 to 17 and DarkSword for iOS 18, in a hidden frame. Report URI says the kits’ own comments indicate iOS 18.7.3 and later, and iOS 26.3 and later, are patched. For iOS 26 it says a separate chain only fingerprinted the device.
Report URI says the attacker’s wallets received about US$7,040 within roughly nine hours on 16 November (UTC). Cointelegraph, checking blockchain records itself, put the figure at about US$7,100. Neither Report URI nor anyone else has said how many card numbers or cookies reached the attacker’s server, and Report URI says it cannot see that.
Which Australian sites were on the list
Report URI’s published list of affected organisations includes these Australian websites:
- Telecommunications: Vodafone Australia (vodafone.com.au) and TPG Telecom (tpg.com.au)
- Banking, finance and comparison: HSBC Australia (hsbc.com.au), Rest Super (rest.com.au), Compare Club (compareclub.com.au) and Energy Scout (energyscout.com.au)
- Investing: Betashares (betashares.com.au)
- Retail and services: Levi’s Australia (levis.com.au) and O’Brien Glass (obrien.com.au)
Global sites widely used here were also on the list, including Zoom, IKEA, ASOS, Salesforce, GitLab, Bitly, Typeform and the trading platform IG. Being on the list means the malicious code was found in that organisation’s Optimizely snippet. It does not mean the company’s own systems, customer databases or accounts were breached, and it does not show whether any of their visitors were actually harmed. We have not seen public statements from the Australian organisations named at the time of writing.
Separately, Report URI says an earlier, related wave between 13 and 16 November injected the same actor’s code through other third-party scripts, on sites including smh.com.au. That wave came through different providers and is not included in the list of 178.
What Optimizely says
An Optimizely spokesperson told Gizmodo the company “identified a security incident in which an unauthorized party exploited a vulnerability in the Experimentation account signup flow,” and that all affected customers had been notified. In a statement to Cointelegraph, the company said: “We have blocked access to the vulnerable path and deployed a fix.” It also said it had removed the injected code, ended active sessions, revoked tokens and reset access for affected user accounts, and was continuing to investigate.
Optimizely has not publicly explained how a flaw in its signup process gave the attacker access to so many separate customer projects. Report URI says it does not know whether this involved a compromised Optimizely system, stolen credentials or something else.
What to do if you visited an affected site
If you visited any of the sites above between Monday afternoon and Tuesday morning, Australian time, these are sensible checks. Most people will have nothing to do beyond the first one.
- Update your iPhone or iPad. Report URI says the exploit kits target older versions and recommends at least iOS 18.7.3 or iOS 26.3. The current public release is iOS 27.2.1, according to Apple’s security releases page. Check in Settings > General > Software Update, or follow Apple’s update guide. Report URI says a page that reloads itself every 60 seconds on iOS 18.6 or earlier was a visible symptom.
- Double-check any crypto transfer. If you copied and pasted a wallet address on Monday or early Tuesday, compare the address the transfer went to with the one you meant to use. Crypto transfers are usually irreversible.
- Watch your card statements. If you typed card details into a form on an affected site in that window, keep an eye on your statement and contact your bank or card provider if you see anything you don’t recognise. If you are worried, ask them to replace the card.
- Sign out and back in. Because the script could grab some cookies, signing out of affected sites and signing back in is a cheap precaution, especially for financial accounts.
- Get help if something goes wrong. You can report a cybercrime on the government’s cyber.gov.au reporting page or call the Australian Cyber Security Hotline on 1300 CYBER1 (1300 292 371), report scams to Scamwatch, and get free support from IDCARE, Australia’s national identity and cyber support service.
What businesses using Optimizely should do
Report URI’s advice for Optimizely Web customers is to review every project’s custom JavaScript and every experiment’s code for anything they didn’t write, check who and what has write access to the account, rotate credentials, and treat card details entered into their own forms, and session tokens in cookies readable by scripts, on 16 November (UTC) as potentially exposed. It also recommends a restrictive Content Security Policy, a browser setting that limits where a page can load scripts from and send data to.
Report URI found that only a minority of the affected organisations it tested had a policy strict enough to block the attack, and said that simply trusting Optimizely’s domain did not help, because the malicious code arrived from that trusted domain. Gizmodo noted that Report URI sells tools for detecting malicious scripts, which is worth keeping in mind when reading those recommendations. Australian organisations that may have had customer data taken should also consider their obligations under the Notifiable Data Breaches scheme. This is the same pattern we saw with Expedia’s third-party vendor breach and the Cursor and Fireworks supply-chain incident: the weak point was a supplier, not the brand customers dealt with.
Our read
This is a good example of why the security of a website isn’t just about the company whose name is in the address bar. Many large sites load code from a dozen or more outside services for analytics, advertising and testing, and each one is a door. The good news is that the attack was spotted and largely cleaned up within hours, the cash taken so far is small, and, based on Report URI’s analysis, anyone on a current version of iOS does not appear to have been a target of the iPhone exploits. The worrying part is the reach: if Optimizely’s account is right, a single weakness in one supplier’s signup process put malware on banks, telcos and a super fund in a day. We would like to see Optimizely explain exactly how its signup flaw led to access across customer accounts, and the Australian companies named tell their customers plainly whether any card or account data was captured on their sites.
Featured image: HTML and JavaScript code on a computer screen, including script tags that load outside files. Photo: Martin Vorel, via Wikimedia Commons, licensed CC BY-SA 4.0; cropped to 3:2, resized and converted to PNG. The adapted image is licensed CC BY-SA 4.0. Illustrative only; it does not show the malicious Optimizely code.




