Hackers Poison Adform Script to Swap Crypto Wallet Addresses Across Customer Sites

Summary: Attackers modified a JavaScript file served by advertising technology company Adform, turning it into a browser-side tool that rewrites cryptocurrency wallet addresses. Adform detected the incident on July 27, 2026, removed the malicious code, notified affected clients, and reported it to authorities. Anyone who visited a site carrying the affected script on July 27 and copied a Bitcoin,

Third-party JavaScript has become one of the internet’s most trusted—and least scrutinized—components. Millions of websites rely on externally hosted scripts for advertising, analytics, customer engagement, and marketing, often granting them broad access to the browser without questioning their integrity. That trust has once again been exploited after attackers compromised a script distributed by advertising technology company Adform, transforming a legitimate service into a cryptocurrency theft mechanism that silently targeted visitors across multiple customer websites.

The incident represents a classic software supply chain attack, but instead of compromising applications or operating systems, the attackers targeted the browser itself. By injecting malicious JavaScript into Adform’s legitimate script distribution infrastructure, they were able to deliver unauthorized code to every website loading the affected resource during the attack window. Because the script originated from a trusted provider already embedded in customers’ websites, browsers executed it without raising security warnings, allowing the malicious payload to operate transparently in users’ sessions.

The objective was both simple and highly effective: steal cryptocurrency by manipulating clipboard operations.

Rather than deploying malware or attempting to compromise cryptocurrency wallets directly, the injected JavaScript monitored users for cryptocurrency wallet addresses copied to the clipboard. Whenever it detected one, the script silently replaced the legitimate destination address with another controlled by the attackers. Victims who pasted the altered address into their wallet software would unknowingly transfer digital assets to the criminals instead of the intended recipient.

This technique, commonly known as a clipboard hijacking or crypto clipper attack, has existed for years in desktop malware. What makes the Adform incident particularly significant is that the manipulation occurred entirely inside the browser through a trusted third-party JavaScript dependency. Users did not need to install malicious extensions, download infected software, or click suspicious attachments. Simply visiting a website that loaded the compromised script could expose them to the attack if they performed cryptocurrency transactions during that session.

According to available information, the malicious code was active for a limited period before Adform detected the unauthorized modification, removed the injected script, and notified affected customers. The company also initiated an investigation into the compromise while working to restore the integrity of its distribution infrastructure.

Although the immediate payload focused on cryptocurrency theft, the broader implications extend far beyond digital assets.

Third-party JavaScript often executes with the same privileges as a website’s own code. Depending on browser permissions and page functionality, such scripts may read form fields, monitor user interactions, modify displayed content, intercept clipboard operations, manipulate payment workflows, or collect behavioral information. If attackers gain control over one widely distributed script, they effectively inherit access to every website that depends upon it.

This supply chain model has become increasingly attractive to cybercriminals because it offers extraordinary scale.

Instead of compromising hundreds of individual websites, attackers only need to infiltrate a single upstream provider whose code is embedded across thousands of customer sites. Previous campaigns targeting analytics providers, software development kits, content delivery networks, and JavaScript libraries have demonstrated how a single compromise can rapidly propagate malicious code throughout large portions of the web.

The Adform incident follows that same pattern.

Advertising technology platforms occupy a particularly sensitive position because their scripts are intentionally designed to execute across large numbers of unrelated websites. Once those delivery mechanisms are compromised, attackers gain immediate distribution channels capable of reaching substantial numbers of users without directly attacking the websites themselves.

The campaign also illustrates the continued evolution of cryptocurrency-focused cybercrime.

Early crypto theft campaigns relied heavily on phishing emails, malicious wallet applications, fake exchanges, and credential theft. Modern attackers increasingly target the transaction process itself. Rather than attempting to steal private keys, they manipulate destination addresses immediately before funds are transferred, exploiting the fact that cryptocurrency wallet addresses are long, complex strings that users rarely verify character by character.

This behavioral weakness makes clipboard substitution remarkably effective.

Most users copy wallet addresses directly from websites or applications, assuming the value remains unchanged until pasted into their wallet. Even experienced cryptocurrency users often verify only the first and last few characters of an address, allowing carefully executed substitutions to pass unnoticed.

For organizations, the incident reinforces the security risks associated with third-party dependencies.

Modern websites frequently load dozens of external JavaScript resources originating from advertising platforms, analytics providers, marketing services, customer support widgets, social media integrations, payment processors, and performance monitoring tools. Every additional dependency effectively extends the organization’s attack surface beyond its own infrastructure.

Reducing that exposure requires stronger controls around third-party content.

Security specialists recommend implementing Content Security Policy (CSP) to restrict script execution, applying Subresource Integrity (SRI) where possible to verify that externally hosted scripts have not been modified, continuously monitoring client-side JavaScript behavior, and minimizing unnecessary third-party integrations. Organizations should also maintain inventories of externally loaded resources and establish procedures for rapidly disabling compromised providers if suspicious activity is detected.

For cryptocurrency users, the attack serves as another reminder that transaction security depends not only on protecting wallets but also on verifying every destination address before confirming a transfer. Hardware wallets, address whitelisting, QR code validation, and manual verification of complete wallet strings remain effective safeguards against clipboard manipulation attacks.

The Adform compromise ultimately demonstrates how software supply chain attacks continue expanding into every layer of the modern web. As organizations become increasingly dependent on externally hosted services, attackers are shifting their focus toward the trusted components that connect them. In an ecosystem where a single JavaScript file can be distributed to thousands of websites within minutes, protecting the integrity of third-party code has become just as important as securing the applications that rely upon it.

Key facts

  • Attackers modified a JavaScript file served by Adform
  • The malicious script rewrote cryptocurrency wallet addresses
  • Adform detected and removed the malicious code on July 27, 2026
  • The company notified affected clients and reported the incident to authorities

Why it matters

This incident highlights a significant supply chain vulnerability in digital advertising technology, demonstrating how compromised third-party scripts can directly impact financial transactions and customer trust for websites relying on ad tech platforms. The browser-side nature of the attack means even sites that implemented security best practices for server-side code could be affected, underscoring the need for continuous monitoring of script integrity and user transaction validation.