🔎 HOW TO CHECK IF YOUR WEBSITE IS VULNERABLE
If your organisation uses Optimizely Web Experimentation, don't assume you're safe just because your website is loading normally.
Step 1 — Check whether Optimizely is integrated
Open your website → Press F12 → Network → Reload the page.
Search for:
optimizely
cdn.optimizely.com
Optimizely experimentation snippets
Also inspect your application source code, tag manager and third-party script inventory.
Step 2 — Audit Optimizely Project JavaScript
Log in to your Optimizely account:
Review Project JavaScript.
Inspect active and archived experiments.
Check custom HTML and JavaScript snippets.
Compare current code with trusted historical versions.
Identify unknown code, external script loaders and unexpected modifications.
Step 3 — Search for Indicators of Compromise (IOCs)
Search your source code, script files, CDN logs, CSP reports and network telemetry for:
1688360[.]cc webshell[.]lol track.js window._k7 window.__k7b data-channel-code="02111110" BIGNIAO
Also check the published malicious domains and file hashes from the incident investigation.
Do not execute suspicious scripts to test them.
Step 4 — Check browser network activity
Open Developer Tools → Network.
Investigate:
Unknown external JavaScript requests.
Unexpected POST requests to unfamiliar domains.
Suspicious cookie or screenshot transmission.
Unexpected wallet-address modifications.
Scripts loaded dynamically by the Optimizely snippet.
Step 5 — Review your security logs
Check:
CSP violation reports.
WAF and CDN logs.
DNS query logs.
Firewall outbound connections.
Authentication and session activity.
Prioritise the November 16 UTC exposure window, while checking for related activity outside that period.
Important: A clean browser test today does not prove that historical visitors were not exposed.
🛠️ HOW TO REMEDIATE
APPLICATION LAYER
Disable affected Optimizely integrations on sensitive pages.
Remove unauthorised JavaScript after preserving forensic evidence.
Restore a verified clean version of Project JavaScript.
Audit all experiments and third-party scripts.
Implement restrictive CSP policies.
Monitor JavaScript changes continuously.
INFRASTRUCTURE LAYER
Block confirmed malicious domains through DNS and outbound network controls.
Review CloudFront, WAF, ALB and application logs.
Investigate suspicious outbound connections.
Review AWS CloudTrail, IAM and API-key activity.
Check EC2 and EKS workloads for related indicators.
Configure security alerts for suspicious egress and DNS activity.
IDENTITY & DATA PROTECTION
Revoke potentially exposed API tokens.
Rotate affected integration credentials.
Invalidate potentially compromised sessions.
Investigate payment-card exposure.
Coordinate with payment providers and affected customers.
PREVENTION
Introduce third-party JavaScript inventory.
Enforce CSP and reporting.
Implement script change detection.
Add security approval for production integrations.
Integrate security validation into CI/CD.
✅ HOW TO VERIFY THE FIX
No known malicious indicators remain in active scripts.
Optimizely project code matches a verified clean version.
CSP blocks unauthorised script execution and data connections.
DNS and firewall controls block confirmed malicious destinations.
No suspicious outbound requests appear in monitoring.
Credentials and sessions have been remediated where necessary.
Security teams have reviewed the historical exposure window.
Remember: No alerts ≠ No compromise.
Verify the application, browser and infrastructure layers independently.