Field noteSep 18, 20262 min read1 source

Cloudflare Page Shield ML catches eight storefront payloads scanners missed

Cloudflare reports that its Page Shield ML flagged eight malicious JavaScript payloads on live storefronts, seven of which were absent from VirusTotal.

In one minute

Cloudflare reports that its Page Shield ML flagged eight malicious JavaScript payloads on live storefronts, seven of which were absent from VirusTotal. Cloudflare described four malicious JavaScript operations, spanning eight payloads, that its Page Shield ML model flagged on live storefronts. The operations covered affiliate hijacking, clickless affiliate theft via an off-screen iframe, a remote code backdoor, and a mobile

Cloudflare described four malicious JavaScript operations, spanning eight payloads, that its Page Shield ML model flagged on live storefronts. The operations covered affiliate hijacking, clickless affiliate theft via an off-screen iframe, a remote code backdoor, and a mobile cloaker that disables nine monitoring tools. When Cloudflare later checked the payloads, seven of the eight were absent from VirusTotal and URLScan returned no malicious verdict for any of them.

Reputation scanners that judge a script by its hash or URL can miss client-side attacks that only reveal themselves through behaviour in live browser traffic. Cloudflare's graph neural network parses JavaScript as a syntax tree, so it can recognise suspicious call patterns across minification and renaming without relying on a known URL or byte signature. Scripts flagged by the GNN, under 0.3% of analyzed traffic, go to a lightweight LLM on Workers AI for a second opinion, and customers are alerted when both agree.

The four operations shared no common signature and stayed dormant until device, country, time, referrer, or browser state matched their conditions. One Lnkr payload version sat indexed by URLScan with no classification for nearly two and a half years. Teams running storefronts cannot treat a one-time dependency scan as proof that the scripts executing on their pages are safe.

The post is a vendor report and does not disclose an overall false-positive rate or how many benign scripts were flagged. A useful signal will be whether Cloudflare publishes precision figures for Page Shield ML alongside its reported detections.

Evidence / sources

  1. 1blog.cloudflare.com/client-side-security-finds-4-malicious-campaigns
All Field Notes

Next reads

Read next

Open the graph
  1. 01topicSecurityExplore the security topic hub.
  2. 02topicWeb SecurityExplore the web-security topic hub.
  3. 03topicMl DetectionExplore the ml-detection topic hub.
  4. 04archiveField NotesOpen the latest editorial analysis.
  5. 05source ledgerSource LedgerInspect the public source evidence graph.
Who read this page?Machine requests, hidden until opened

Loading the privacy-safe route aggregate...

Open the JSON contract