A report alleges that malicious code delivered through Optimizely affected more than 186 websites and could have exposed visitor credentials and payment information. What should site operators and visitors check, and how much of the report is confirmed?
What should we check after the reported Optimizely CDN malware injection?
Answers
For a site operator, start by checking whether your pages loaded the affected Optimizely code and whether visitors could have received it during the reported incident. Inventory tags across your sites, including ones managed outside the engineering team.
Review security alerts and available network logs for unexpected destinations, then block suspicious traffic where appropriate. Preserve relevant logs and coordinate with your security and incident response teams before deciding what customer notifications or other remediation are needed. A site using Optimizely is not, by itself, proof that its visitors were compromised.
Reply to this answer
Treat the details as allegations until you can corroborate them. The discussion describes payment card skimming, cookie theft, wallet address substitution, and attacks against iPhones and iPads, but those claims need independent verification. The original report also comes from a company selling a security product, which is a reason to check its evidence carefully, not automatically dismiss it.
Reply to this answer
If you think you visited an affected site, don't assume your device is infected. Watch payment accounts for unfamiliar transactions and contact your card issuer if you spot anything suspicious. If you entered a password on a site confirmed to be affected during the relevant period, changing it and checking account activity would be sensible.
For an iPhone or iPad, install available updates and follow guidance from the device vendor or a trusted security professional if you have a specific reason to suspect compromise. The discussion doesn't provide a reliable do-it-yourself test for the alleged exploit kits.
Reply to this answer
This is also a good time to review who can publish third-party tags and how changes are approved. Marketing tools can put executable code on a lot of pages quickly. Engineering and security need visibility into those changes, not just an alert after something starts sending data somewhere unexpected.
Reply to this answer
DNS filtering or firewall rules for newly registered domains may catch some malicious destinations early. They aren't a complete fix though. Legitimate new domains can get blocked too, and an attacker doesn't have to use a newly registered domain.
Reply to this answer
Add your answer
Answers are reviewed before publication.
Torkavi-5n:
Browser extensions can also generate unfamiliar outbound traffic, so an alert needs investigation before it gets attributed to the injected code.