Poisoned third-party malware scripts were found on, Zoom and other major websites. Hudson Rock linked the code to browser-based financial theft and delivery of iPhone exploit-kit stages.
The evidence covers 21 named web properties..com alone carries an average monthly audience of 149 million outside the UK, which shows the reach of the delivery path without proving how many visitors were exposed.
Kirk’s 15-capture table
Kirk from Ohey supplied archived response verification for 15 website captures, with response bytes, size and SHA-256 for 16 vendor responses. That work overlapped Hudson Rock’s findings for, Zoom and GitLab and added 12 properties, bringing the documented set to 21 named web properties.
Hudson Rock independently matched those hashes to the archive records and directly recovered nine poisoned vendor files. The files were not just suspicious names in a request chain.
They were malicious code inside responses served from third-party providers’ own script and widget endpoints. In Optimizely, the injection sat inside customer projectJS configurations beside legitimate experimentation code.
Optimizely projectJS injection
Some versions used a plain loader. Others encoded the URL. The and HSBC UAE specimens embedded a complete fallback payload, which means the malicious behavior was not a single line copied into every customer file.
The shared responses and repeated injection point to a multi-customer delivery problem. They also show why a visitor could load a poisoned script without the named websites’ backend systems being compromised.
Hudson Rock also reviewed Amirul Cyber’s OptimJack research. That review tied Hootsuite and Talkwalker to one poisoned project, and Talkwalker’s homepage HTML directly referenced 4894383279964160.js.
, Zoom and GitLab
The broader evidence now includes, Salesforce, Mutual of Omaha and through specific historical Optimizely response records. The file is /js/5728063363743744.js, and Kirk reports 51 traced sites in the wider investigation.
The unresolved point is the route by which the malicious code entered the third-party delivery systems. Until that is mapped, the safest reading is narrow and practical: treat third-party script integrity as the weak point, not the site name in the browser bar.







