Someone quietly bought 30 WordPress plugins and planted backdoors in all of them. Not one. Thirty. The one getting attention right now is Countdown Timer Ultimate, which was force updated by the WordPress.org team after they caught it phoning home to a suspicious domain and dropping a backdoor file designed to look almost identical to a legitimate WordPress core file. The kind of thing we would miss if we were not looking carefully.
Here is where it gets genuinely clever in a way that should make us uncomfortable. The injected code only showed the spam and fake pages to Googlebot. Real users and site admins saw nothing. The site looked fine. It was quietly being used to game search rankings while we had no idea. And traditional security responses like taking down the command and control domain would not have worked anyway, because the attacker routed their C2 domain through an Ethereum smart contract. Knock one domain offline, they update the contract and point to a new one. Game over for the old playbook.
This is a supply chain attack, and it is not exotic anymore. It is becoming a repeatable business model. Buy a trusted plugin with an established install base, inherit all the implicit trust those site owners have, and then weaponize it quietly. The "trusted name" is the product being acquired here, not the code.
Read this up: Supply chain attack, the most popular topic in cyber security conversations recently. So a supply chain attack is when hackers poison a trusted ingredient that goes into the software we use — like someone tampering with flour at the mill instead of robbing the bakery. Because modern apps are built from hundreds of small pieces of code shared online, one poisoned piece can secretly infect millions of apps at once. We can't avoid it with strong passwords, because the attack happens to the people who make our software, long before it reaches us.