Reading: Malware in third-party scripts tied to BBC, Zoom and other major sites

Malware in third-party scripts tied to BBC, Zoom and other major sites

Published
3 min read
Advertisement

Malicious code was found inside third-party script and widget responses used by major websites, and Hudson Rock says the same poisoned delivery chain now reaches well beyond the first sample set. The evidence ties browser-based financial theft and iPhone exploit-kit stages to the same infrastructure, but it still does not show how many visitors loaded the harmful version or how many devices were touched.

The report centers on web traffic that looked routine on the surface and was not. Hudson Rock recovered malicious Optimizely project files and a minute-ly loader, then later matched archived response bytes, sizes and SHA-256 hashes from 15 website captures across 16 vendor responses. Kirk, working from Ohey, supplied the archived response verification and iOS-routing analysis that extended the picture to Kissmetrics and StorifyMe, while the mobile branch was linked to Coruna and DarkSword.

The stronger finding is not just that malicious code appeared, but where it sat. In Optimizely’s case, the injection lived inside customer projectJS configurations alongside legitimate experimentation code. Some versions used a plain loader, others encoded the URL, and the and HSBC UAE specimens embedded a complete fallback payload. Hudson Rock also said the shared responses and repeated injection establish a multi-customer delivery problem, which is harder to dismiss than a single bad file tucked into one site.

- Advertisement -

That reach matters because the same poisoned infrastructure was traced across major web properties. Kirk’s 15-capture table overlapped, Zoom and GitLab and added 12 properties, while the two tables together identified 21 named web properties with the stated evidence. Hootsuite and Talkwalker shared one poisoned project, and Talkwalker’s homepage HTML directly referenced 4894383279964160.js. The wider investigation also pointed to historical Optimizely response evidence for, Salesforce, Mutual of Omaha and, including /js/5728063363743744.js for.

What the report does not settle is just as important. It does not identify whether the original access came through provider infrastructure, publishing credentials, integrations or separate customer accounts, and it does not establish a compromise of the named websites’ backend systems or every customer of these providers. Hudson Rock also reviewed Amirul Cyber’s OptimJack research and said its asset leads helped expand the original sample set, but the findings still document a subset of activity, not an incident-wide victim count.

.com’s average monthly audience of 149 million outside the UK explains why this kind of delivery problem draws attention, but that figure is audience context, not a count of affected visitors. Kirk later reported 51 traced sites in the wider investigation, yet the number of malicious page loads, successful thefts and compromised devices remains unknown. For readers tracking whether poisoned scripts are still sitting in vendor pipelines, that unanswered count is the story’s sharpest gap.

Advertisement
Share This Article