A hacked website tool planted a card skimmer on Australian sites
Attackers slipped malicious code into Optimizely, a website testing tool used by sites including Vodafone and HSBC Australia. What it did and what to check.

If you used a big brand’s website on Monday afternoon or overnight, it may have been running someone else’s code. That code tried to copy card numbers, swap crypto wallet addresses and break into older iPhones.
The attackers didn’t hack those websites directly. They got into Optimizely, a tool many large companies use to test different versions of their web pages.
One tool, 178 organisations
Optimizely confirmed the breach on its status page on 17 November. It says an “unauthorized party exploited a vulnerability” in its Web Experimentation product and “used it to add malicious JavaScript to some customer projects”.
Because companies load Optimizely’s code straight into their pages, anything added to it ran on their sites too.
Security researcher Scott Helme of Report URI spotted it. His report found the malicious code on 188 of the 1,611 Optimizely snippets he checked, belonging to 178 organisations. He thinks the real number is higher. Optimizely hasn’t said how many customers were affected.
The Australian sites on the list
Report URI’s list includes hsbc.com.au, rest.com.au, vodafone.com.au and tpg.com.au. It also names betashares.com.au, compareclub.com.au, energyscout.com.au, obrien.com.au and levis.com.au.
TPG Telecom, which owns Vodafone in Australia, told iTnews it has paused Optimizely on the Vodafone site. It found no evidence Vodafone’s systems or customer data were compromised, and said the affected Vodafone pages had no payment or login functions.
iTnews understands HSBC switched off Optimizely worldwide. HSBC told Reuters, in a report carried by SmartCompany, that the scripts were not active on its websites. Rest did not respond to iTnews.
Being on the list means the code was delivered to a site. It doesn’t mean anyone’s details were taken from it.
Four tricks in one script
Report URI found the code did four things:
- Copied card details. It grabbed the card number, expiry date and security code typed into a site’s own payment form. Cards typed into a payment provider’s hosted payment field, such as Stripe’s or Adyen’s, were out of its reach.
- Swapped crypto addresses. It replaced wallet addresses on the page and in your clipboard with the attacker’s, so a payment would go to the wrong place.
- Took cookies and screenshots. When it swapped a crypto address, it also sent some site cookies and a screenshot of the page to the attacker.
- Attacked older iPhones. It loaded two known exploit kits aimed at iPhones and iPads running iOS 13 to iOS 18. Report URI says iOS 18.7.3 or later, and iOS 26.3 or later, are patched.
The attacker’s crypto wallets had received at least US$7,040 by 3:25am Perth time on 17 November. Helme says he can’t see how many cards or cookies reached the attacker.
About 17 hours, from Monday lunchtime in Perth
The timeline puts the first injection at 4:21am UTC on Monday 16 November. That’s 3:21pm in Sydney and 12:21pm in Perth. The card-copying part was added later that evening, at 9:43pm Perth time.
Most sites were cleaned up between about 4:40am and 5:10am Perth time on Tuesday 17 November. Every infected file Helme tracked was clean by 7:11am.
Optimizely says it has “fixed the vulnerability and removed the injected code”, secured affected user accounts and added protections. Its status page still lists the incident as being monitored.
We found no advice on the breach from the Australian Cyber Security Centre when we checked on 18 November.
If your business uses Optimizely
The attack hit companies through a supplier they trusted. Any third-party script on your site, from analytics to chat widgets, can do the same if its maker is breached. Taking card details in your payment provider’s hosted payment fields keeps them out of reach of code like this.
For iPhone users, the fix is the same as ever: keep iOS up to date. Our guide to iOS 27.2 covers the latest version.
Checklist
- Update your iPhone and iPad. Go to Settings, General, Software Update; iOS 18.7.3 or later, or iOS 26.3 or later, is patched against the exploits Report URI found.
- Check your card statements. If you typed card details into a large brand’s website on 16 or 17 November, look for charges you don’t recognise and report them to your bank.
- Double-check crypto addresses. Compare the full wallet address before you send any cryptocurrency, rather than trusting a pasted one.
- Ask your web team about Optimizely. If your business uses Optimizely Web Experimentation, ask Optimizely whether your project was affected and what code ran on your site on 16 and 17 November.
- List the third-party scripts on your site. Remove any you no longer use, so fewer outside suppliers can change what your customers’ browsers run.
- Use your payment provider’s hosted payment fields. Taking card details in the provider’s own hosted fields keeps them away from scripts on your pages.
Tick items as you go. Your ticks stay in this browser.




