Loading prices…
STKR NewsSTKR News0 of 3 free this month
Markets

Hackers inject credit card, crypto-stealing malware into 178 major websites

A massive supply chain attack has turned 178 major websites into malware distribution hubs, targeting crypto wallets and credit card data through compromised optimization scripts.

Originally on Cointelegraph →
AB

Adrian Boysel

Contributor

Nov 17, 2026

4 min read

Photo illustration / STKR News

Security is often a game of trust, but in the current web architecture, that trust is being weaponized. We recently learned that 178 major websites were compromised not through their own servers, but through a third-party script delivery system. This is a classic supply chain attack, and for anyone building in the crypto or AI space, it is a loud wake-up call about the fragility of the tools we use to 'optimize' our user experience.

The Anatomy of the Script Injection

The breach centers on Optimizely, a widely used platform for A/B testing and conversion rate optimization. Hackers managed to inject malicious code into the JavaScript files that these 178 sites load to track user behavior. Because these scripts are trusted by the browser and the site owner, they bypass traditional firewalls. Once the script is live on the site, it acts as a silent parasite.

This isn't a simple defacement where a hacker puts a logo on a homepage. This is functional, high-intent malware. The researchers who discovered the breach noted two primary functions: stealing credit card information from checkout pages and, more importantly for us, replacing cryptocurrency wallet addresses in real-time.

The Crypto Clipboard Threat

For builders, the crypto-stealing component is the most dangerous part of this story. The malware monitors the user's clipboard and the webpage's input fields. When a user goes to send funds and copies a wallet address, the malware swaps that address with one owned by the attacker. If the user doesn't double-check every single character of that long alphanumeric string, their funds are gone forever.

This targets the 'autopilot' mode many users fall into. We talk about mass adoption, but mass adoption implies a level of safety that simply doesn't exist yet if a simple script injection on a reputable site can divert thousands of dollars in a single click.

Why Builders Should Be Skeptical of Third-Party Bloat

As a founder, the pressure to optimize is constant. You want to know which button color converts better or where users are dropping off in your funnel. To get that data, you install 'one simple line of code.' That one line of code is a backdoor. You are essentially giving a third-party provider permission to execute whatever code they want on your site, in front of your users, without your direct oversight.

The 178 websites affected here weren't small blogs. These were major players with presumably large security budgets. Yet, they were vulnerable because they relied on the security of a vendor's delivery pipeline. If you are building a dApp or a platform that handles sensitive financial data, you need to ask yourself if that A/B testing script is worth the risk of a total brand wipeout.

  • Audit your dependencies: Every script you load from an external CDN is a liability.
  • Subresource Integrity (SRI): Use SRI tags to ensure that if a script is modified by a hacker, the browser refuses to load it.
  • Minimalism as Security: If you don't absolutely need a tracking script, don't use it. Each one increases your attack surface.

The Human Cost of Automated Attacks

We often look at these hacks as numbers—178 sites, thousands of users. But from a founder's perspective, this is a trust crisis. When a user loses their life savings because they copied an address on a site they trusted, they don't blame the script provider. They blame the site they were on. They blame 'crypto' as a whole. This is why our industry struggles to move past the 'Wild West' phase.

The attackers are getting more sophisticated. They aren't just looking for server vulnerabilities; they are looking for the weakest link in the chain of trust. In this case, it was the delivery mechanism for optimization tools. It’s a reminder that 'convenience' for the developer often leads to 'catastrophe' for the user.

Is Decentralization the Answer?

There is an argument to be made that decentralized hosting or content delivery could mitigate some of these risks, but that’s a long way off from being the standard for enterprise web apps. For now, the solution is much more boring: rigorous security hygiene and a healthy dose of skepticism regarding third-party integrations.

If you are building a product right now, go look at your header tags. Look at every script being called from an external domain. Do you know who owns those domains? Do you know their security protocols? If the answer is no, you are essentially leaving your front door unlocked and hoping the neighbors are watching.

The Clear Takeaway

The 178-site hack proves that no site is an island. We are all connected through a web of shared scripts and services. For the builder, the lesson is clear: your security is only as strong as the least secure script you've imported. Stop treating third-party integrations as 'set it and forget it' tools. They are active participants in your ecosystem, and right now, they are being used to drain wallets and steal data. Keep your tech stack lean, use integrity checks, and never prioritize a conversion metric over the safety of your user's assets.


Read the original at Cointelegraph →

The Brief

Stay Updated on Cutting-Edge Tech

A six-minute morning dispatch on the markets and the technology shaping them.

Free. No spam. Unsubscribe anytime.

Write for STKR

Become a Contributor

Earn $STKR for published stories on markets, protocols, and culture.

  • Earn $STKR for every published piece
  • Editorial support from the STKR desk
  • Byline visibility across the network
  • First look at the upcoming creator program
Apply to Write

Keep reading

All stories

Comments

24 reader responses