Trusted Tool Turns Toxic – CNN, BBC, Zoom Exposed

skull silhouette in blue computer code
Photo: solarseven / Shutterstock

A trusted web tool was hijacked to slip card-stealing and crypto-thief code onto 178 major brand sites, putting everyday users at risk.

Story Snapshot

  • Optimizely confirmed an attacker injected malicious code through its Experimentation signup flow.
  • Researchers found 188 infected Optimizely scripts tied to 178 organizations, including CNN, BBC, Fox News, and Zoom.
  • The injected code could skim payment cards and swap crypto wallet addresses on victim pages.
  • Optimizely blocked the path, removed the code, revoked tokens, and reset access for affected accounts.

What Optimizely Says Happened

Optimizely said an unauthorized party abused a flaw in its Experimentation account signup flow. The intruder used that opening to add malicious JavaScript to some customer projects. The company said it fixed the flaw, removed injected code, and began monitoring. This was a supply chain hit delivered through a trusted script, not a break-in at each customer site. Optimizely detailed emergency actions and framed the impact as limited to some web experimentation customers.

The company reported it blocked the vulnerable path, ended active sessions, revoked tokens, and reset access for affected accounts. It also said it added protections to stop more unauthorized code delivery. Those steps match a response to unauthorized changes in customer project code. While the full loss tally is unknown, the provider-level fix removed the payloads from its content delivery network and project fields during the cleanup window.

What Independent Analysts Found

Security researchers scanned Optimizely-hosted scripts that many sites load. They found 188 infected files across 178 organizations. This supports a large, multi-brand reach in a short time. The bad code sat in a customer-controlled project JavaScript field that runs on every page. That makes this a classic client-side supply chain event. Big names on the affected list included CNN, BBC, Fox News, Zoom, Salesforce, and others, which drove attention to the case.

Analysts reported the payload could do two things users hate and criminals love. It could skim payment card data from forms and swap out cryptocurrency wallet addresses before a victim clicked send. This “clipper” trick diverts funds to the attacker’s address. The skimmer could read checkout fields and send captured data to a rogue server. Investigators labeled the campaign “Optimjack” or “OPTIMJACK,” referring to the Optimizely project layer used to spread the code.

What We Do Not Yet Know

Investigators have not released the full technical detail of the signup-flow flaw. We also do not have a count of confirmed stolen cards or the total of diverted crypto. The 178 figure comes from infected script findings, not a list of proven victim losses. Some sites may have blocked parts of the payload with security headers or other controls. The attacker’s identity is unknown, and the scope of any fraud is still being assessed by companies and researchers.

These gaps do not weaken the core facts. A provider confirmed unauthorized code changes. Independent teams measured widespread infected scripts tied to major brands. The code had real theft features. The open questions are the forensics details, the exact execution rate on each site, and the money trail. Those will take time to nail down. For now, the lesson is clear: if a trusted third-party script turns toxic, every site that pulls it is exposed.

Why This Matters for Families, Small Firms, and Liberty

Americans expect to read the news, pay a bill, or join a video call without a thief on the page. When a single vendor’s script gets poisoned, thousands or millions can be touched at once. That risk grows as more services move to cloud tools few people can audit. Strong private-sector security and real accountability beat heavy-handed mandates that miss the mark. Clear standards, swift disclosure, and tested rollback plans protect users without bloated bureaucracy.

Here is what you can do now. Check recent bank and card statements for odd charges. If you sent crypto during the incident window, confirm the destination address history on a reputable explorer. Turn on bank alerts and multi-factor logins. If you run a website, review all third-party scripts, lock down who can change them, and set strict content security policies to limit what runs and where data can go. Demand vendors prove they test these controls regularly.

Practical Next Steps for Companies

Companies should pull logs for pages that load Optimizely scripts during the incident window. Compare content security policy reports to see if the payload tried to call home. Rotate keys and tokens tied to the affected service. Require code review and approval for any project-level JavaScript field. Ask Optimizely for a customer-specific timeline of changes and token resets. Document all findings so you can answer banks, customers, and regulators with facts, not guesses.

Sources:

insiderpaper.com, thenextweb.com, cointelegraph.com, infostealers.com