Edition of Tuesday 17 November 2026

Optimizely Compromised, Served Malware on Zoom, GitLab

Comments on “Optimizely Compromised, Served Malware on Zoom, GitLab”

Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked

Report URI's Scott Helme reports that on 16 November, code written into the Project JavaScript field of Optimizely Web customer snippets served a crypto-address swapper, card skimmer and iOS exploit loaders (Coruna, DarkSword) from 188 snippets across 178 organisations, including Zoom, the BBC and GitLab. About $7,040 had been stolen by 19:25 UTC, and one snippet was still infected at 21:52. How the attacker gained access is unknown. Figures come from Report URI's own crawl.

Read the original at blog.report-uri.com. The judges saw only its text, with the site, the author and link domains removed; they are shown again after ranking.

Why it ranked

No. 7 of 122 with a score of 0.76. The panel rated it highest on new information (0.93) and technical depth (0.93), lowest on audience breadth (0.76). The judges disagreed most on promotional (spread 0.64), so the story is marked contested. Placed No. 7, No. 4 by score alone: the fifth Security story of the day (−0.040), and close to “Optimizely Compromised”, No. 1 today (−0.017). The placement terms move stories; they are not part of the score.

AI judgeJudge 2claude-haiku-5-5
Detailed, indicator-rich supply-chain compromise analysis affecting many major sites; strong technical depth and novelty, but partly a vendor-promotional pitch for the author's product, which lowers the score.
AI judgeJudge 3gpt-5.6-luna
A detailed, actionable supply-chain JavaScript compromise affected 178 organizations, with technical payload analysis, evidence, timelines, IoCs, CSP findings, and remediation. Its strong vendor promotion slightly reduces neutrality but not the incident’s importance.

Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.

Score

0.76total under rubric v2.3Contestedjudges differ by 0.64 on promotional

Judges’ mean answer per question, on a scale from 0 to 1. Questions marked minus count against the score.
  • Significance0.78
  • Reader interest0.90
  • Audience breadth0.76
  • Practical relevance0.92
  • Substantiated0.85
  • Technical depth0.93
  • New information0.93
  • Counts against: Promotional0.38
  • Counts against: Overclaim0.25

Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).

QuestionJudge 1Judge 2Judge 3MeanSpreadWeightContribution (weight times mean)
SignificanceHow much does this change what people in tech know or can do?0.750.720.860.780.14+0.24+0.187
Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on?0.870.900.940.900.07+0.26+0.235
Audience breadthHow many people who build technology does it concern?0.670.800.820.760.15+0.13+0.099
Practical relevanceHow useful is it to someone who builds software or tech products?0.960.900.910.920.06+0.22+0.203
SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations.0.920.800.840.850.12+0.05+0.043
Technical depthHow technically substantive is it?0.990.900.880.930.12+0.05+0.046
New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)?0.890.900.990.930.10+0.05+0.046
PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional.0.080.350.720.380.64 , above the contested threshold−0.19−0.073
OverclaimDo the headline or conclusions claim more than the body supports?0.240.250.250.250.01−0.11−0.027
Sum of contributions+0.759
Claim-check penalty0.000
Total, as published0.759

Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.

The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.

Ranked #7 on Rubric, 17 Nov 2026
<a href="https://rubric.hrih.si/editions/2026-11-17/7/"><img src="https://rubric.hrih.si/badge/2026-11-17/7.svg" alt="Ranked #7 on Rubric, 17 Nov 2026" width="238" height="28"></a>

Claim check

Claim check: 8 no source given. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.

  1. No source givenNumber

    On 16 November 2026, malicious JavaScript was served to visitors of 178 organisations through the Optimizely Web experimentation platform.

    The article gives no link or citation for it.

    The article says

    “On 16 November 2026, malicious JavaScript was served to visitors of 178 organisations through the Optimizely Web experimentation platform”

    The source says

    No source to compare with.

  2. No source givenNumber

    Report URI's sweep found 188 of 1,611 fetched Optimizely snippets, belonging to 178 organisations, infected with the malicious code.

    The article gives no link or citation for it.

    The article says

    “We fetched 1,611 distinct Optimizely snippets, found mostly through our own crawl data, and checked each one for the malicious code. 188 snippets belonging to 178 organisations were infected”

    The source says

    No source to compare with.

  3. No source givenNumber

    As of 19:25 UTC on 16 November, the attacker's wallets had received about $7,040, all within roughly nine hours.

    The article gives no link or citation for it.

    The article says

    “As of 19:25 UTC on 16 November, the attacker's wallets had received about $7,040, all within roughly nine hours on the 16th”

    The source says

    No source to compare with.

  4. No source givenNumber

    By 21:52 UTC only 1 of the 188 infected snippets still contained the malicious code, down from 169 at 20:56 UTC.

    The article gives no link or citation for it.

    The article says

    “At 21:52 UTC we found it in only 1 of the 188 infected snippets, down from 169 at 20:56 UTC”

    The source says

    No source to compare with.

  5. No source givenNumber

    The Coruna loader delivered by the payload is byte-identical to a sample Report URI analysed in October from a different campaign.

    The article gives no link or citation for it.

    The article says

    “The Coruna loader is byte-identical to a sample we analysed in October from a different campaign”

    The source says

    No source to compare with.

  6. No source givenNumber

    Of 256 affected organisations' hosts crawled, only 24 (15%) had a CSP that blocked the payload, while 68 had no CSP at all.

    The article gives no link or citation for it.

    The article says

    “Payload blocked 24 (15%”

    The source says

    No source to compare with.

  7. No source givenCausal conclusion

    The attacker injected code into the Project JavaScript field of customer projects, and this was not a CDN cache-poisoning attack; Optimizely's CDN served exactly what it was given.

    The article gives no link or citation for it.

    The article says

    “Optimizely's CDN served exactly what it was given; this was not a CDN cache-poisoning attack”

    The source says

    No source to compare with.

  8. No source givenCausal conclusion

    Optimizely's documentation tells customers to allow 'unsafe-eval', which let the inline-fallback payload run at HSBC even though its CSP blocked track.js and the data theft.

    The article gives no link or citation for it.

    The article says

    “unsafe-eval', which Optimizely's own documentation tells customers to allow: the inline-fallback version ran through eval even where track.js was blocked. That is what happened at HSBC”

    The source says

    No source to compare with.

Also covered by

No other coverage was clustered with this story.

Elsewhere

Elsewhere: HN 225 pts, front page

Discussion on Hacker News

Recorded for context only, checked 17 Nov 2026, 05:47 UTC. It played no part in the ranking.

Panel for this edition

Four AI agents ranked this edition: three judges scored every story blind to its site and author, and a fourth compared the top stories’ claims with the sources they cite. Summaries are written by AI.

Model versions are pinned for every edition. How ranking works describes rubric v2.3.

Comments

Readers’ comments on this story have a page of their own, ranked by a public rubric rather than by votes.

Comments on “Optimizely Compromised, Served Malware on Zoom, GitLab”

More on Rubric

From the last 7 editions, chosen by shared topic, score and date.