Optimizely: who approves changes to your website scripts?
The Optimizely incident exposes the authority granted to external code inside a page. Connect each change to its owner, delivered content and observed browser behavior.
Leggi in portogheseIn this article
- What is established and what still needs investigation
- Assign an owner to publishing authority
- Define what needs to keep working
- Check the limits of the delivered policy
- Pair integrity with an update process
- Close the response with verifiable acceptance
- Frequently asked questions
- Related reading
- Sources and references
By Pentesty
What is established and what still needs investigation
In its November 17 notice, Optimizely says it fixed a vulnerability used to inject malicious JavaScript into customer projects, removed the code and took steps to secure affected accounts. The record reviewed remains in monitoring; it does not detail the signup mechanism described in news reports.
Report URI’s research found 188 compromised snippets associated with 178 organizations among 1,611 examined on November 16. Its update reports all observed infected files clean by 23:11 UTC that day. The sample does not measure every customer, visitor or compromised device.
Define what needs to keep working
Select a representative journey, such as checkout or sign-in, in an authorized environment with synthetic data. Decide where experimentation is needed and where its execution should be restricted. Agree this with product owners: removing an integration without observing the flow can interrupt a legitimate function.
Record behavior before the intervention, the approved change and the operation observed afterward. Use minimized network captures and application records without payment details, credentials or personal data. The analysis of script authority inside a session provides a complementary perspective; it concerns a separate incident with no demonstrated connection to this one.
Check the limits of the delivered policy
A CSP allowing the supplier’s domain does not establish file integrity. The script-src documentation explains that strict-dynamic can propagate trust from a script authorized by a nonce or hash to scripts it loads. Also assess dependencies on unsafe-eval before changing the policy.
In staging, compare the policy received by the browser with the destinations actually needed. Define a harmless test and its expected outcome, then check both blocking and journey continuity. Reports help identify dependencies; approval needs to record which controls were actually exercised and which combinations remained outside the sample.
Pair integrity with an update process
As the SRI documentation explains, the browser compares a resource with an expected hash; different content is rejected. Cross-origin resources require appropriate CORS. A frequently changing snippet needs an explicit process for approving new bytes and updating the integrity reference.
Test an approved version and a harmlessly modified copy, without using the incident’s malware. Record the expected rejection and who may approve a legitimate update. If the integration cannot pin content, document that limitation and assess alternative delivery or isolation before accepting the exception.
Close the response with verifiable acceptance
Ask the supplier for affected project identifiers, known intervals and investigation limits. Correlate that information with your records before concluding which data was accessible. Clean delivery now does not reconstruct the past. The analysis of marketing supplier access revocation helps organize that separate question through an independent case.
Before restoring the integration, record approval, the observed version, the journey tested and outstanding issues with named owners. Separate technical restoration from exposure assessment and customer communications. Repeat acceptance when the project, policy or publishing path changes.
Frequently asked questions
Does using Optimizely confirm exposure?
No. Check the product, project, pages and interval used by your company. The published sample is not a diagnosis of every customer.
Does cleaning the files close the investigation?
No. It describes a later observation. Earlier exposure requires your records and supplier information, with gaps identified.
Can SRI be applied without coordinating updates?
Legitimate changes also alter the hash. Define approval, reference updates and journey testing to avoid unexpected disruption.
What evidence belongs in acceptance?
Bring together the accountable identity, approved change, observed content, journey outcome and exceptions. State the environment and period covered by testing.
Sources and references
- Optimizely: public incident notice
- BleepingComputer: incident reporting
- SecurityWeek: reporting and evidence limits
- Help Net Security: investigation context
- CISO Advisor: Portuguese reporting
- SempreUpdate: Portuguese reporting
- CpC: Portuguese analysis and observation limits
- Report URI: November 16 research and update
- MDN: CSP sources and trust propagation
- MDN: resource integrity and CORS
- OWASP: third-party JavaScript management
Original Pentesty analysis, published November 17, 2026. The proposed scenarios are editorial guidance, with scope and validation to be defined for each environment.