Logo
Cybersecurity

Your Website Trusts the Script. Should Your Security Team?

A third-party JavaScript integration can become an attack route even when it loads from a legitimate domain. The recent incident involving 178 organisations shows why script permissions and browser security controls deserve closer scrutiny.

ITSEC AsiaITSEC Asia
|
Nov 18, 2026
Your Website Trusts the Script. Should Your Security Team?

On 16 November 2026, malicious JavaScript was delivered to visitors of websites belonging to 178 organisations through Optimizely Web Experimentation. Security researcher Scott Helme identified 188 infected snippets among 1,611 examined. The affected organisations included major names in finance, retail, technology, media and travel. [1]

The attacker inserted malicious code into customer projects within the experimentation platform. The original JavaScript snippet continued to load from Optimizely's legitimate content delivery domain. This meant that a website could receive compromised code through a source it had already approved.

The payload attempted to replace cryptocurrency wallet addresses, capture payment card details entered into website forms, steal certain browser cookies and take screenshots. It also attempted to deliver exploit code targeting Apple mobile devices. Reuters reported that the extent of successful data theft and the number of affected visitors could not be established. [1][2]

The technical issue goes beyond the compromised vendor. It exposes a weakness in how organisations define trust inside their browsers.

A trusted domain is not a guarantee of trusted code.

Many websites use Content Security Policy (CSP) to tell browsers which sources are permitted to load scripts and send data. A typical policy may allow a trusted vendor's domain because the website needs its functionality.

But a source allowlist answers only one question: where may the browser load code from? It does not establish whether the code coming from that source is safe.

In this incident, the malicious loader arrived through the approved Optimizely domain before attempting to load additional scripts and communicate with attacker-controlled destinations. The initial trusted source therefore became the entry point for the next stages of the attack. [1][3]

Report URI examined CSP configurations on affected websites and found a substantial control gap. Of the 159 organisations assessed, 68 had no CSP. Another 50 had policies that allowed both the malicious payload and data theft. Seventeen allowed the payload to run but blocked its outbound data transmission. Only 24 blocked the payload outright. [1]

This distinction matters. Blocking suspicious outbound connections can reduce data exfiltration, but it may not prevent malicious code from changing information displayed on a page. A cryptocurrency address replacement, for example, can happen entirely within the browser.

Organisations should review CSP as an active security control rather than a one-time configuration task. At a minimum, security teams should:

  • Restrict script-src to explicitly approved sources and assess whether nonce-based policies are appropriate.

  • Review connect-src to limit where browser scripts can transmit data.

  • Avoid allowing unsafe execution features such as unsafe-eval unless there is a documented technical requirement.

  • Monitor changes to third-party scripts and investigate unexpected external domains.

  • Test payment forms, authentication flows and other sensitive browser functions under realistic attack scenarios.

The review should also cover the full web application attack surface. Teams need to understand which pages expose sensitive functions, how scripts interact with those functions and whether weaknesses in application logic could increase the impact of a compromised integration.

Authorised penetration testing can help identify weaknesses in supported web applications, APIs and exposed access paths. Bronyx AI, ITSEC's AI-assisted autonomous penetration testing platform, can support security assessments within its confirmed technical scope. CSP configuration and browser policy reviews should remain part of the organisation's wider application security programme.

A website's security depends on every component that executes within it. If a third-party script can influence a payment form, user session or browser connection, it deserves the same scrutiny as other parts of the application.

Assess your supported digital assets through authorised testing with Bronyx AI: https://bronyx.ai/

References

  1. Report URI, “World's Largest Brands Infected With Malware Via Optimizely,” 16 November 2026. https://blog.report-uri.com/worlds-largest-brands-infected-with-malware-via-optimizely/

  2. Reuters, “Popular websites compromised in bid to steal crypto, target iPhone users,” 17 November 2026. https://www.reuters.com/legal/government/popular-websites-subverted-bid-steal-crypto-target-iphone-users-2026-11-17/

  3. Optimizely World, “Lessons From the Optimizely Web Experimentation Compromise,” 17 November 2026. https://world.optimizely.com/blogs/mark-stott/dates/2026/11/lessons-from-the-optimizely-web-experimentation-compromise

Share this post

You may also like

The Patch Is Installed. Is the Server Still Compromised?
Cybersecurity

The Patch Is Installed. Is the Server Still Compromised?

A VULNERABILITY THAT REACHED STORAGE DEVICES On 9 November 2026, SecurityWeek reported that attackers were exploiting Plex2Shell to compromise Plex Media Server applications running on QNAP network-attached storage (NAS) devices. QNAP had issued a security notice three days earlier, saying it had received reports from users whose Plex installations appeared to have been compromised. Its technical support team was assisting affected users and had confirmed no data loss in the cases it was handling. QNAP also clarified that the vulnerabilities were in Plex Media Server, not in its QTS or QuTS hero operating systems. [1][2] Plex disclosed four vulnerabilities affecting Plex Media Server versions 1.43.2 and earlier: CVE-2026-96652, CVE-2026-96654, CVE-2026-96655 and CVE-2026-96656. Each issue presents limited risk individually. Chained together, however, they allow an unauthenticated remote attacker to execute arbitrary code with the privileges of the Plex Media Server process. Plex published a proof of concept on 16 October and subsequently reported widespread attacks against internet-facing servers that had not been updated. Compromised servers were being used to run cryptocurrency miners and

ITSEC AsiaITSEC Asia
|
Nov 12, 2026 — 4 minutes read
What CISOs Should Ask Before Choosing a Penetration Testing Provider in 2026
Cybersecurity

What CISOs Should Ask Before Choosing a Penetration Testing Provider in 2026

INTRODUCTION What percentage of your last penetration test report was actually proven exploitable, and what percentage was a list of things a scanner flagged and nobody validated? Most CISOs cannot answer that question with confidence, and that is exactly the problem. Buyers guides published this year point to a pattern worth sitting with. If a quoted penetration test comes in at four to five thousand dollars or less, it is very likely an automated vulnerability scan wearing a pen test label, not manual work performed by a skilled tester. That gap between what is sold as a penetration test and what is actually delivered is why the selection conversation matters so much more than most procurement teams treat it. ITSEC Asia, Indonesia's leading cybersecurity company, works with organizations across Indonesia, Singapore, Australia, and the UAE that have gone through this exact evaluation, and the questions that separate a genuinely useful engagement from an expensive checkbox exercise are more specific than most RFPs ever ask. Source: Six Questions to Ask a

ITSEC AsiaITSEC Asia
|
Jul 17, 2026 — 5 minutes read
Cybersecurity Has a People Skills Gap Too
Cybersecurity

Cybersecurity Has a People Skills Gap Too

An analyst has spent two hours investigating suspicious activity. They understand the sequence, know which systems may be affected and have a reasonable hypothesis about what the attacker did. Then the incident manager asks a simple question: “What do we need to do now?” The answer suddenly requires more than technical knowledge. Cybersecurity work is full of moments like this. Findings need to be explained. Assumptions need to be challenged. Teams need to disagree without losing time. Technical specialists have to communicate with executives, engineers, auditors and people who would prefer never to hear the phrase “lateral movement” before their first coffee. NIST’s NICE program treats these capabilities as part of cybersecurity work itself. Its workplace skills resources include communication, collaboration, critical thinking, conflict management, resilience, strategic thinking and relationship building. That matters for how organizations train cybersecurity professionals. COMMUNICATION CHANGES THE VALUE OF TECHNICAL SKILL Consider a penetration tester who discovers a serious vulnerability. Finding it requires technical skill. Explaining why it matters requires another set of abilities. The tester needs to describe

ITSEC AsiaITSEC Asia
|
Sep 25, 2026 — 3 minutes read

Receive weekly
updates on new posts

Subscribe