Situational Awareness Terminal
◈ Source Credibility Index
1. BLUF (Bottom Line Up Front)
On 16 November 2026 an unidentified actor wrote malicious JavaScript into the "Project JavaScript" field of Optimizely Web projects, and the code reached visitors of at least 178 organisations through Optimizely's own CDN. The payload swapped cryptocurrency addresses, skimmed card data, stole cookies and screenshots, and tried to deliver the Coruna and DarkSword iOS exploit kits. Optimizely's Official Narrative attributes the access to a flaw in its Experimentation account sign-up flow and says it has been fixed. The cause is not independently verified. It is highly likely the compromise occurred as described; it is only roughly even whether a sign-up authorization flaw, as opposed to another access path, was the entry point.
2. Key Judgments — Optimizely Supply Chain Compromise
- It is highly likely (≥85%) that the injection was real and wide. Report URI, via Dark Reading, examined 1,611 unique Optimizely scripts and found malicious code in 188 scripts tied to 178 organisations. Dark Reading, the dev.to write-up and microwire.info agree on these figures.
- The actor is probably financially motivated. The reported on-chain take was about $7,040 by 19:25 UTC on 16 November. Report URI links a TRON wallet to cash-outs on 3 November 2026 and in March 2026, and links the injector domain webshell.lol to an earlier wave through Kiss, StorifyMe and Minute Media. Victim counts for cards, cookies and iOS devices are not reported.
- The access vector is unresolved. Optimizely cites a vulnerability in its Experimentation account sign-up flow. Report URI says it cannot tell whether the cause was a compromised Optimizely system, a credential with cross-customer reach, or something else. A re-infection at Smartsheet after cleanup suggests the actor kept write access for a time.
- Containment is probable but unconfirmed. The Media Trust calls the threat contained, 1688360.cc was put on clientHold at 00:37 UTC on 17 November, and Optimizely says it removed the code and revoked tokens. No outside party has verified that the underlying path is closed.
- Defences were uneven. Allowing cdn.optimizely.com in a Content Security Policy (CSP) did not help. Of 256 hosts Report URI crawled, 24 were protected by a restrictive script-src. The code still ran at HSBC through an inline eval fallback, because 'unsafe-eval' is permitted.
3. Analysis of Competing Hypotheses (ACH)
| Hypothesis | Supporting Evidence | Contradicting Evidence | Evidence Gaps | Probability |
|---|---|---|---|---|
| H-A: A financially motivated actor abused an authorization or tenant-isolation flaw in Optimizely's account sign-up flow to write Project JavaScript into unrelated customers' projects. | Optimizely's statement names the sign-up flow and says it fixed the vulnerability. Strike Graph's Justin Beals describes the path as "a new account got write access to other tenants' projects", and Vigilant's Chris Nyhuis says a path around authorization boundaries must have existed. The single Project JavaScript field was written and the rest of each snippet was untouched. | Optimizely gave no mechanism and did not answer Dark Reading on scope or exposure window. The Smartsheet re-infection after cleanup fits a persistent foothold at least as well as a single flaw. Beals and Nyhuis are inferring and have no inside access. | Optimizely forensic findings, affected project IDs and change timestamps, and the date the flaw was first used. | 52% |
| H-B: The actor used a compromised Optimizely internal system, a privileged service, or a leaked credential or token with cross-customer reach. | Report URI lists this explicitly as open. Microwire.info says Optimizely revoked active tokens and reset access for affected accounts, which implies credential exposure was considered. Persistence after the first Smartsheet cleanup fits stolen access. | Optimizely's own account does not mention internal compromise. Token revocation is a standard response to any such incident and does not show the cause. | Credential or API-token audit logs, and whether the sign-up flaw and a credential issue are linked. | 27% |
| H-C: The operation mainly aimed at iOS device compromise, and the crypto theft was secondary. | The payload carries a loader for the Coruna and DarkSword exploit chains. Devices on iOS 18.6 or earlier reload every 60 seconds to retry the exploit. Report URI says the Coruna loader was byte-identical to an October sample from a different campaign. | All payload functions ran at once. Only older iOS versions were exposed, since 18.7.3+ and 26.3+ are patched. Observed revenue came from address swapping, and the wallet links point to financial operations. | Number of compromised iOS devices, any follow-on implants, and the relationship between the kit operators and this actor. | 7% |
| H-D (Maskirovka / Strategic Deception): The apparent signal is a deliberate disinformation, fabrication, or denial-and-deception operation designed to shape perception or mask a different course of action. | The code was concealed with base64 and atob(), and an inline eval fallback exists in case the domain is blocked. Optimizely's explanation is vague and has not been tested. | Report URI and The Media Trust observed the payload independently, and on-chain movements and a domain takedown are checkable. Obfuscation is routine and does not indicate narrative manipulation. No source alleges fabrication. | Independent telemetry on the vendor's disclosure, and whether any customer saw activity outside the stated window. | 3% |
ACH Assessment: H-A is best supported because it rests on the only primary statement from the vendor, plus two outside executives who reached the same inference. Its lead over H-B is narrow. No source contradicts another, so the gap reflects an unexplained cause and not a conflict. The three sources are not fully independent: Dark Reading and microwire.info both rely on figures that Report URI documented, and the 34 million page-visit estimate appears only in microwire.info with no named originator.
4. Key Assumption Check (KAC)
- Critical Assumptions:
- Report URI's counts are accurate. If its crawl missed projects, more than 178 organisations may have been exposed.
- The 16 November window is the whole exposure. Report URI says the payload served "for most of the day", and card skimming was added at 13:43 UTC. If injection began earlier or resumed, the exposure estimate would be too low.
- Optimizely's description of the flaw is accurate and complete. If the cause was credential-based (H-B), the fix may not close the path.
- Takedown of 1688360.cc ended collection. The actor reportedly re-infected Smartsheet and may use new infrastructure.
- One actor ran the whole operation. If access and payload came from separate parties, attribution and risk change.
- Information Gaps: Optimizely has not given a root cause, the exposure window, the first-access date, or the number of affected projects it counts. The number of cards, cookies and iOS devices exposed is not reported, since the $7,040 figure covers crypto only. Regional victim counts for the Asia-Pacific entities that microwire.info lists are not given. No victim organisation statements beyond microwire.info's claim that Equifax and Salesforce disabled the scripts. Closing these needs Optimizely's forensic report, customer breach notifications, and CDN and project audit logs.
- Bias & Deception Risks: Report URI documented the incident and is the origin of most technical detail. Dark Reading's vendor commentary comes from firms with products in the third-party-risk market, and the Optimizely statement is self-reported. Microwire.info is a first-person consumer piece with an unsourced visit estimate and a slightly different iOS description (redirecting to an exploit kit, where Report URI describes a hidden iframe). The "100% source alignment" is overstated because the sources share one primary origin. The attacker's use of obfuscation is an evasion technique, not evidence of a disinformation effort.
5. Implications and Strategic Risks — Optimizely Customers, Asia-Pacific
The compromise used a trusted vendor's CDN and certificate, so allow-lists and vendor approval did not stop it. If the cause is a tenant-isolation failure, similar write paths may exist at other script-delivery platforms, and the actor has shown it can return after cleanup. The actor ran earlier waves through other vendors (Kiss, StorifyMe, Minute Media), so more injections through other third parties are plausible.
Cyber / Information Space — Optimizely Web and Project JavaScript
Unless the root cause is confirmed closed, the same field could be written again. Report URI advises customers to inspect every project and experiment for 1688360.cc, atob( and unfamiliar code, and to rotate credentials. The Coruna loader's match to an October sample suggests reuse of exploit tooling across campaigns.
Economic / Social — Asia-Pacific financial, retail and telecom entities
Microwire.info lists HSBC entities in seven markets, Levi's sites in eight, and others including Vodafone Australia, TPG Telecom, Takeda and Rest Super. Card data typed into a site's own form fields on 16 November is treated by Report URI as exposed, so card reissuance, regulatory notification and chargeback costs may follow. Whether any region's notification rules apply has not been reported.
Security / Counter-Terrorism — iOS and iPadOS users on older releases
Per Report URI, the kits target iOS 18.6 and earlier, and 18.7.3+ and 26.3+ are patched. Exploitation outcomes are unreported. Devices that were unpatched on 16 November and reloaded pages repeatedly are the exposed group.
6. Recommendations and Outlook
- Immediate Actions (0–30 days): Track whether Optimizely publishes a root-cause statement, an exposure window and a project count. Watch for new domains hosting track.js or boot.js, and for further Smartsheet-style re-infections. Check customer disclosures against Report URI's published list of affected sites. Monitor the actor's wallets for new cash-outs and for links to the earlier March and 3 November operations. Compare CSP findings (script-src, connect-src, 'strict-dynamic', 'unsafe-eval') across reported victims. Track iOS patch uptake in the exposed population.
- Medium-Term Posture (1–12 months): Indicators of durable change include wider use of Subresource Integrity or hash pinning, tighter script-src policies, and removal of third-party testing scripts from checkout and login pages, as microwire.info and Fortra's Tyler Reguly recommend. Track whether script-delivery vendors publish tenant-isolation audits. Note any regulator action or litigation naming Optimizely or affected brands.
- Scenario Outlook: Best: Optimizely publishes a verifiable root cause, no further injections appear, and takedowns end the actor's collection. Most likely: the incident subsides with unresolved root-cause questions, partial victim disclosures, and the actor resurfacing through another vendor within weeks. Worst: the cause proves to be a credential or internal-system compromise that remains open, enabling renewed injection, or card and session data from 16 November is used in follow-on fraud. Triggers for the worst case include new attacker domains on Optimizely hosts and customer fraud reports.
7. Key Individuals and Entities
| Name | Role / Affiliation | Relevance to Assessment |
|---|---|---|
| Optimizely | Experimentation and A/B testing vendor whose CDN served the code | Attributes the incident to a sign-up flow vulnerability; has not stated the mechanism or window. |
| Unknown threat actor(s) | Unattributed | Wrote the payload into Project JavaScript. Linked on-chain to earlier operations in March and on 3 November 2026. |
| Report URI | British web security monitoring service | Primary source for technical detail, counts, CSP analysis and wallet tracing. |
| Scott Helme | Founder, Report URI (per Dark Reading) | Stated the access vector is unknown and is "for Optimizely to explain". |
| The Media Trust | Digital security firm | Tracks the malware as "Hydra-Cart"; describes the threat as contained. |
| Justin Beals | CEO and founder, Strike Graph | Questions whether Optimizely's fix addresses the cause or the symptom. |
| Tyler Reguly | Associate director, security R&D, Fortra | Advocates Subresource Integrity for version pinning. |
| Chris Nyhuis | CEO, Vigilant | States a path around customer authorization boundaries must have existed. |
| Affected organisations (Zoom, BBC, CNN, Salesforce, GitLab, IKEA, HSBC, Equifax, Smartsheet and others) | Optimizely Web customers | Visitors exposed to the payload. HSBC's CSP blocked track.js but not the inline copy. Smartsheet was cleaned and then re-infected. |
| Coruna and DarkSword | iOS exploit chains | Delivered through a hidden iframe to iOS 18.6 and earlier. The Coruna loader matched an October sample. |
8. Thematic Tags
Cybersecurity, supply chain attack, Optimizely, third-party JavaScript, payment card skimming, cryptocurrency clipboard hijacking, iOS exploit kits, Content Security Policy, Asia-Pacific
Explore more: Cybersecurity Briefs · Daily Summary · Support us
✗ NO Dissemination
✓ Cleared Analyst review
| Source | SCI | Role |
|---|---|---|
| devto | 3 | SOURCE_DOCUMENT |
| darkreading | 3 | SOURCE_DOCUMENT |
| microwire_info | 3 | SOURCE_DOCUMENT |