In short
Several publishers report attackers injecting malicious code into customer websites through compromised third-party platforms and tools. The Record reported Optimizely confirmed malicious code in customer sites, and iTnews reported a hijacked testing tool planted a card skimmer on Australian brands. These are reported breaches, not outages.
What the headlines say
Four publishers reported a cluster of incidents over the past 48 hours, all involving malicious code reaching websites through third parties rather than through the site owners' own systems.
According to The Record's headline, website management platform Optimizely confirmed that hackers put malicious code into customer sites. iTnews reported that a hijacked website testing tool planted a card skimmer on Australian brands' sites. The Register reported that Transport for London took its Oyster photocard website offline after attackers compromised customer accounts. Dark Reading reported that Cursor traced a malicious Claude Code extension back to a third-party breach.
We have only the headlines, so specifics such as the number of affected sites, the data taken and the full timeline are not yet clear. Treat the details below as attributed reporting, not confirmed fact.
Is this a cyber attack?
In these cases, the headlines describe attacks. The words used by the publishers, compromised accounts, malicious code, card skimmer and hijacked tool, all point to deliberate intrusion rather than an outage or configuration error.
That distinction matters because not every website problem is an attack. A site can go down due to a failed deployment, an expired certificate or a provider outage. The way organisations tell the difference is by looking for evidence of unauthorised change: unexpected scripts, altered checkout pages, new outbound connections to unfamiliar domains, and logins or code pushes that no one on the team recognises. Where those appear, as the publishers describe here, you are likely dealing with an incident rather than a fault.
Why the supply chain angle matters
The common thread across all four reports is trust in something external. A management platform, a testing tool and a code editor extension were each reportedly used to deliver malicious content to downstream sites.
This is a classic supply chain problem. Your own code can pass every review while the attacker rides in through a dependency you load automatically. The Australian brands referenced by iTnews may have had no flaw in their own applications at all; the risk came from a tool they trusted. We cover this pattern in our supply chain attack Field Manual entry.
The Cursor and Claude Code reporting from Dark Reading also touches on a related risk: tools with broad permissions acting on your behalf. When an AI coding assistant or extension can read and change code, a compromised version inherits that reach. Our excessive agency entry explains why over-permissioned tools widen the blast radius.
What organisations should check now
Start with visibility. Build or refresh an inventory of every third-party script, extension, plugin and tool that touches your public websites and development pipeline. If you cannot list them, you cannot defend them.
Then prioritise the following:
- Review recent changes to front-end and checkout code, and compare against a known good baseline.
- Verify the versions of any management platforms, testing tools and editor extensions against the vendor's expected releases.
- Inspect payment and login pages for injected scripts or unexpected outbound requests.
- Restrict and monitor the permissions granted to automated tools and extensions.
- If you use any of the named platforms, follow the vendor's advisories and assume customer accounts and sessions may be exposed until proven otherwise.
Our Threat Radar tracks exploited issues, and there are no related CVEs listed for this cluster at present. Keep an eye on the briefing and research pages as more detail emerges.
If you suspect you are affected
Move quickly to contain. Isolate the affected tool or platform, rotate credentials and tokens, and preserve logs before cleaning up. Our incident response guidance covers the early steps, and the broader Field Manual sets out the patterns behind these breaches.
StrikeCyber helps organisations test how far a compromised dependency could reach through penetration testing before an attacker finds out for you.
Sources
- TfL takes Oyster photocard website offline after attackers compromise customer accounts, The Register, 2026-11-19
- Hijacked website testing tool plants card skimmer on Australian brands' sites, iTnews, 2026-11-18
- Website management platform Optimizely confirms hackers put malicious code into customer sites, The Record, 2026-11-17
- Cursor Traces Malicious Claude Code Extension to Third-Party Breach, Dark Reading, 2026-11-17
Frequently asked questions
Were these confirmed cyber attacks?
Yes, based on the headlines these are reported as breaches rather than technical faults. The Record reported Optimizely confirmed hackers put malicious code into customer sites, and iTnews reported a hijacked testing tool was used to plant a card skimmer. The Register reported TfL took its Oyster photocard site offline after customer accounts were compromised.
How does a supply chain breach affect my website?
When a shared platform, extension or testing tool is compromised, attackers can push malicious code to every site that trusts it. iTnews reported a hijacked testing tool delivered a card skimmer, which means your own code can be clean while the injected content steals data from customers. This is why monitoring third-party scripts matters.
What should Australian organisations do first?
Inventory every third-party script, tool and extension loaded on your public sites, then verify each one against the vendor's expected version. Review any recent unexplained changes to front-end code and check payment and login pages closely. If you use any of the named platforms, follow the vendor's guidance and treat customer accounts as potentially exposed.
