Applying updates is the basis of maintenance. But reports show that the update itself can be tampered with , including around WordPress. This article looks at how supply chain attacks work using public information, then sorts out how to balance "apply quickly" with "wait a little", and how to reduce the scripts your site loads from outside. The aim is calm planning, not alarm.
What a supply chain attack is
Instead of attacking your site directly, the attacker targets something your site already trusts . A WordPress site trusts several things:
What you trust Examples
Update delivery Update servers, the official directory, paid-plugin update channels
The vendor itself Developer accounts, build systems, who owns the vendor
Files loaded from outside JavaScript served from a CDN, third-party tags, font delivery
When an admin decides "there's an update, apply it" or "this script is well known, load it", that trust is turned against them.…