The operator returns through a CMS update channel and CDN edge nodes
ATG-class eventJuly 2025 to March 2026
After the sanctions, the same operator pushed backdoors through the official update channel of a website CMS and installed a toolkit on CDN edge nodes that rewrote pages in transit, swapping crypto wallet addresses and inserting video. Researchers counted up to 580,000 visitors a day.
- Position
- A CMS update channel, and CDN edge nodes reached through their management servers
- Reach
- About 10,748 sites matched; up to 580,000 unique visitors a day (XLab)
- Category
- CDN Compromise
- Effect
- Deceive
- Thread
- The polyfill.io operator
What happened
QiAnXin XLab began the investigation in July 2025 and published in March 2026. It found two routes. First, the official update check of MacCMS, a content management system popular with streaming and film sites, delivered a PHP backdoor on an administrator's first login after installation, from a download link that expired after about three minutes. The backdoor injected JavaScript into every page the site served.
Second, compromised GoEdge management servers pushed a toolkit, which XLab named RingH23, to the CDN edge nodes they controlled. It included a module for the edge web server that hijacked downloads, injected JavaScript, replaced crypto wallet addresses and inserted segments into video streams, plus a rootkit that hid the operator's addresses. The injected code fired only for mobile visitors in China's time zone arriving from outside the site, at most once every ten hours per visitor, with a probability that varied by hour, and behind a remote switch. XLab counted about 10,748 matching sites and malicious script hosts peaking at 580,000 unique clients a day, and said the code was virtually identical to the polyfill.io scripts.
The ATG nexus
This is ATG at the delivery layer, run by an operator under sanctions. The edge module changes pages and wallet addresses between the site and the reader, after every check the site itself could make. The site's own server holds clean content, and the reader receives something else. That is Content Swapping, and the research's point that modification after load, after trust, defeats checks made at publication.
The sequence also completes the arc. Exposure and sanctions closed the public CDNs. The operator moved down the stack, into the software that delivers pages and the channel that updates them, and the targeting rules kept it quiet for scanners, administrators, desktops and the United States.
Limits of the comparison
Most of the account rests on one research team's work, and its attribution of the newer front domains is inference. Whether the operator bought or compromised the MacCMS update channel is unresolved. The CDN and cloud brands imitated by the operator's lookalike domains were not compromised.
On this site
- Whitepaper 7.4: CDN as Risk Multiplier
- Whitepaper 7.6: Typosquatted and Impersonating CDN Domains
- Introduction: Swapping What You See
- Concept: Content Swapping
- Concept: Supply Chain Injection
- Concept: Adversarial Asset Cycling
- Concept: Post-Load / Post-Trust Modification