Urgent.News

What's breaking now, across thousands of outlets.

Tech

Researchers find Optimizely serving malicious JavaScript to sites of 178 orgs including Zoom, CNN, HSBC, Salesforce, GitLab, Ledger, BBC, Equifax, IKEA, more (Scott Helme/Report URI Blog)

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

This LinkedIn post explains how to identify Salesforce custom fields, active flows, and active validation rules that lack descriptions. Such items are crucial to understand because their purpose often resides in the memory of senior administrators, and their absence can lead to confusion for new users. The author provides three Tooling API and SOQL queries, along with a few lines of Python code using the pandas library, to generate a list of these components.

The output includes the component type (field, flow, or validation rule), the component name, the administrator who last modified it, whether it is still active, and the last change date. By presenting this list, the author aims to facilitate a discussion between senior administrators and new users, enabling the latter to better understand the Salesforce environment they are working with.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

This story

This is one outlet's version. Read the fullest account.

Every outlet that reported this, and when →

Read the original at blog.report-uri.com →

More in Tech

OpenAPI Components: Reuse vs Duplication

Quick answer: Reuse an OpenAPI component with $ref whenever the same schema, parameter, or response is genuinely one concept used in multiple places; it gives you a single source of truth and keeps…

Every Rule We Added Had a Bug. So We Stopped Adding Rules.

We wrote a handful of small rules on November 12. Each one was a line or two. Each one was obviously right. A read-only review found a real bug in nearly every one of them before they shipped.

  • Every rule added to Since tool had a bug.
  • Rules were used for questions beyond code review scope.
  • Team stopped adding rules, relying on code analysis instead.

More from Monday 16 November →