Optimizely Web snippet abused to infect 178 websites with card skimmer and iPhone exploits
Compiled by RedTeamDaily · AI-assisted summaries · Human review not recorded for this version
Published
What happened
Malicious loader code was added to the Project JavaScript field of Optimizely Web snippets on 16 November 2026, affecting 178 organisations, including Optimizely's own login domain. Functions included a crypto clipper, a card skimmer, cookie and screenshot exfiltration, and iOS exploit routing (Coruna for iOS 13 to 17, DarkSword for iOS 18.4 to 18.7). Defenders should search Project JavaScript and custom code for unknown scripts, atob( calls and the reported C2 domains, review the change history, API tokens and integrations, and rotate credentials. Non-HttpOnly cookies and cards entered that day should be treated as exposed. CSP without unsafe-eval or strict-dynamic blocked the payload.
For security analysts · Written by AI from 1 source · Report an error
- Sources
- 1
Sources and verification
Sources and editorial review
No named human review has been recorded for this story. See the source evidence below.
No vendor or government source is linked to this story yet. Read the source reports; attribution is not independent verification.
How severity and exploitation labels work · All source reports · Report an error
What to do
- Check every Optimizely Web Project JavaScript field and experiment custom code for scripts you did not write, and for atob( calls.
- Review Optimizely change history, users, API tokens and integrations, then rotate credentials.
- Update iPhone and iPad devices to iOS 18.7.3 or later, or iOS 26.3 or later.
- Check crypto transfers and card statements from 16 November 2026 for anything unexpected.
Written by AI from the sources, checked against them
Source timeline (UTC) · 1 update
Explore this report
Ask AI about this story
Optional follow-up answers generated from our coverage. Check the linked sources before acting.
Ask your own questionWho and what is in it
Companies