Attackers used Optimizely Web to deliver cryptocurrency theft code, payment-card skimmers and iOS exploit kits to visitors of 178 organizations on November 16, 2026, security researcher Scott Helme reported in a Report URI investigation. His team found malicious code in 188 JavaScript snippets associated with sites including Zoom, BBC, CNN, Salesforce and GitLab, turning a trusted website dependency into a delivery route for malware.
Optimizely told BleepingComputer that an unauthorized party exploited a vulnerability in its Experimentation account signup flow to add JavaScript to customer projects. The company said it blocked the vulnerable path, deployed a fix, removed injected code, ended active sessions, revoked tokens and reset access for affected accounts. It also said it blocked code delivery in Cloudflare and notified all affected customers.
The exposure crossed industries. Report URI identified 32 banking and finance organizations, 23 technology and SaaS companies and 20 retail and fashion businesses, alongside organizations in media, healthcare, travel, telecoms and other sectors. Its examples included HSBC, Equifax, IKEA, Ledger, Peacock and Air France-KLM. BleepingComputer independently confirmed through urlscan.io records that malicious scripts loaded, or attempted to load, on numerous affected sites, including Fox News, KLM, Scheels, American Girl, Smartsheet, Stamps.com and Salesforce.
Salesforce told the publication it was investigating the modifications and confirming that Optimizely scripts were disabled across preview and production instances. It said it would notify affected customers without undue delay if it identified unauthorized access to their data.
How trusted snippets became the delivery route
Optimizely Web customers load JavaScript snippets containing the platform’s code, their experiments and an optional Project JavaScript field, known as projectJS. That field holds customer-written code that runs on every page using the snippet.
The attacker inserted code into projectJS, leaving the rest of each snippet untouched. The altered files continued to arrive from cdn.optimizely.com with Optimizely’s certificate. Customers serving snippets through their own domains, including Scheels and Vodafone Australia, were also affected because the content came from the same Optimizely projects. Optimizely’s main website and login site carried infected snippets too.
Report URI distinguished this from CDN cache poisoning: the CDN delivered the project content it received. Optimizely told BleepingComputer that attackers gained access through a vulnerability in its Experimentation account signup flow. Report URI said it had not determined how the attacker gained write access to customer projects.
Most injected loaders fetched https://1688360.cc/track.js directly. Another variant concealed the URL with Base64 encoding and decoded it using atob(), defeating a simple search for the domain. A third embedded the payload and executed it through eval if the remote host was blocked. Smartsheet’s snippet was cleaned and then reinfected with the encoded variant, which the researchers said showed the attacker still had access at that point.
The earliest observed Optimizely injection was in a BBC snippet at 04:21 UTC on November 16, loading webshell.lol; its last clean urlscan capture was at 02:21. Certificates for 1688360.cc were issued between 04:28 and 05:23, and the domain was registered at 05:23. The first recorded track.js build appeared at 08:10, with the script observed on BBC’s site at 08:28. Zoom’s snippet carried a Last-Modified time of 11:20.
Report URI linked the activity to an earlier wave using webshell.lol/get.js through Kissmetrics, StorifyMe and Minute Media scripts on November 13–16, and traced what it described as the same actor’s injector to Turkish sites using an SEO backlink-panel script on September 17.
One payload, several routes to theft
The attacker rebuilt the payload 26 times during November 16, adding capabilities and wallet addresses without removing existing wallets. Visitors received the same script, with its functions active together; the effect depended on their device and activity.
The cryptocurrency component validated wallet checksums and replaced legitimate addresses with attacker-controlled destinations. It covered Bitcoin, Ethereum and EVM chains, TRON, Solana, TON, Litecoin, Bitcoin Cash and Dogecoin. Beyond page text, forms, links and images, it intercepted copying, navigator.clipboard, outgoing fetch/XHR requests, navigation, window.open and the iOS share sheet. It rescanned changing pages, allowing address substitution to persist as visitors interacted with a site.
A card skimmer added at 13:43 UTC watched form submissions and fetch/XHR POST requests for a Luhn-valid card number, expiry date and CVV. Once it had all three, it attempted to send them to https://1688360.cc/card.php through navigator.sendBeacon. Cards entered into hosted payment iframes, such as those supplied by Stripe or Adyen, were outside its reach; cards entered into a site’s own fields were exposed.
When the malware replaced an address near wallet or payment wording, it also sent the page URL, original addresses, cookies accessible through document.cookie and an html2canvas screenshot to https://1688360.cc/hit.php. Cookies marked HttpOnly were excluded from that collection mechanism.
On iPhones and iPads, the script fetched boot.js from 5vobauua3ojpklx.icu and eil786npto9u5bq.icu, checked the iOS version and loaded a hidden iframe. Report URI identified the delivered exploit kits as Coruna and DarkSword:
| Device version | Observed delivery |
|---|---|
| iOS 13–17 | Coruna through /A8/, plus a direct loader at /JIUJIU888/index.js |
| iOS 18.x | DarkSword through /B9/, /D11/ and /D12/ |
| iOS 26 | A separate /C10/ chain that, at the time of analysis, only fingerprinted the device |
The first iOS router domain was registered on November 9 at 17:52 UTC; the second was registered on November 16 at 16:38. Between 17:13 and 17:57 on November 16, the attacker added the second host and injected a Coruna iframe on every visit from iOS 18.6 or earlier. Those pages reloaded every 60 seconds to retry exploitation, providing a visible symptom.
The Coruna loader matched a sample Report URI analyzed in October from another campaign. Comments inside the kit described iOS 18.7.3 and later, and 26.3 and later, as patched.
Wallet receipts and cleanup
Report URI reported approximately $7,040 received by attacker wallets as of 19:25 UTC on November 16, attributing cryptocurrency theft to the campaign. BleepingComputer cautioned that some wallets predated the attack, making the campaign’s stolen total difficult to establish. Report URI traced the TRON wallet’s use back to March 2026.
BleepingComputer recorded these wallet balances and transaction counts on November 16:
| Cryptocurrency and attacker wallet | Receipts observed |
|---|---|
BTC: 19g9rZcPeiz8rUvyWpTRyXXhPnjsWrc3kW |
0.08298 BTC, about $5,380; 7 transactions |
LTC: ltc1q3wp7g6ds0ggg6fl6kncpa4sepn0q3qfacgred5 |
17.02 LTC, about $762; 3 transactions |
TRON: THvs6p56XkUiMkJeSc51cAP64u2RsTYqxa |
662.9 USDT plus 184 TRX, about $719; 50 transactions |
ETH: 0xC4026b06D82b0F0B363eda0642D61CfbDc17884e |
0.074 ETH, about $100; 6 transactions |
| BNB Smart Chain: same EVM address | 82 USDT, about $82; 2 transactions |
The sources give conflicting Bitcoin transaction counts and Ethereum receipts: Report URI’s snapshot at 19:25 UTC on November 16 listed four Bitcoin transactions and 0.055 ETH, while BleepingComputer’s figures for November 16, with no specific observation time given, listed seven Bitcoin transactions and 0.074 ETH across six transactions. Report URI described the BTC as unspent. It also reported funds being swept between 13:03 and 13:05 UTC, including Ethereum USDC sent to a HitBTC deposit address.
BleepingComputer also identified wallets with zero receipts and transactions: Solana FVtL8NMYS9PA1v3HE67XUGCtGA9JaZUvqav2fU2LrV5n, TON UQAgM1VqSZQiJLSG5w-ovurq5CZdxLEK3_7CMmwALTA5e09p, Bitcoin Cash qzkaaf8n6grmpr0d9lx8xutn3r9lk722f566hhpe58 and Dogecoin DBEGrxRF7KMSuhTS4c1MFviStU6efdMnu5. The TON raw address was 0:2033556a49942224b486e70fa8beeaeae4265dc4b10adffec2326c002d30397b.
The researchers checked 1,611 distinct snippets, largely located through their crawl data, and preserved infected files with response headers, SHA-256 hashes and fetch times. They considered the 178-organization count a likely undercount because their search covered only snippets they could locate in time.
Their 19:24–19:59 sweep found 186 infected snippets; the eventual total reached 188. Mass cleanup occurred around 20:40–21:10, including Ledger at 20:41, Smartsheet at 20:56 and BBC at 21:07. At 20:56, 169 snippets remained infected. By 21:52 UTC, only TalkTalk’s remained infected among the 188 previously identified files.
Detection and protective steps
Report URI said monitoring unexpected changes to trusted JavaScript, newly loaded scripts and unusual external connections could expose this activity. An appropriate Content Security Policy in enforcement mode could block key parts of the attack, including when the initial script arrived from a trusted host.
Its November 16 indicators included 1688360.cc at 136.113.106.136 for payload delivery and collection; iOS routers 5vobauua3ojpklx.icu at 34.96.213.201 and eil786npto9u5bq.icu at 34.87.36.58; and l7bcsnwc7nzr3uo.icu for Coruna telemetry at /api/iptj. It recommended blocking the listed domains and their subdomains.
Additional indicators were webshell.lol for the earlier injector, linkforge.cc for its SEO-panel carrier, and fallback command-and-control domains je4ft3gn8vxudum.icu, q1ls1ho9x7wsxlu.icu and ios-hack.icu. The researchers also listed p55abnw2pnsz0bo.icu, 1y69gy2mdzaltz1.icu and gm38duxoihbmy5o.icu as sharing certificates and IP addresses with the kit.
Payload markers included window._k7, window.__k7b, the script attribute data-channel-code="02111110" and Coruna telemetry channel BIGNIAO. The November 16 track.js SHA-256 hashes were:
- 17:13 build:
814a963c0da480e2449d9b6664480156e1cd6d731014117401bf635badec3a0f - Latest observed build, 17:57:
f7b84b9a94f749f8ced3f0112d0a66894e8bbc3b4aa5592021d1b8976a9bad40
Report URI said it could share its preserved snippet evidence with affected organizations and CERTs. Optimizely said its investigation continued and that it would publish relevant updates on its status site.
Visitors to affected sites on November 16 should review cryptocurrency transfer destinations, monitor payment-card accounts and contact their issuer about suspicious transactions, as BleepingComputer advised. They should also watch for suspicious account activity, especially in sensitive services they were logged into. Report URI recommends updating affected iPhones and iPads to iOS/iPadOS 18.7.3 or later, or 26.3 or later.




