Most WordPress security advice focuses on keeping plugins updated, and for good reason. Outdated plugins are the most common way sites get hacked. But there’s another side to plugin risk that gets less attention: what happens when the update itself is the problem?
Plugins are businesses and hobby projects run by people. People sell their plugins, lose interest, run out of time or have their accounts compromised. When a plugin with a large install base changes hands, the new owner inherits the ability to push code to every site that has it installed. Most new owners are legitimate. A few are not.
This is supply chain risk, and it’s become a real concern across the software world, not just WordPress. Here’s how it shows up in practice and what you can do about it.
How plugin supply chain problems happen
Plugins are sold
Popular free plugins with many active installs are valuable. Companies buy them to grow their user base, to upsell premium versions or to integrate them into their products. Usually, this is fine and sometimes it’s good: a well-funded team may maintain the plugin better than a tired solo developer.
Occasionally, buyers have other motives. Over the years, there have been cases where plugins were bought and then updated to inject spam links, advertising or tracking code, or to collect data in ways users didn’t expect. The plugin’s name, history and reviews stayed the same; only the intent behind it changed.
Plugins are abandoned
When a developer stops maintaining a plugin, it doesn’t disappear. It keeps running on every site that has it. When a vulnerability is discovered, nobody fixes it. Attackers know this and actively look for vulnerable plugins that will never be patched.
Developer accounts are compromised
Attackers sometimes gain access to a developer’s account and push malicious code through the normal update channel. In 2024, several plugins on WordPress.org were updated with malicious code after developer credentials were compromised, injecting code designed to create rogue administrator accounts. WordPress.org responded by closing the affected plugins and later introduced mandatory two-factor authentication for accounts with permission to commit plugin and theme updates.
Premium plugins outside the repository
Premium plugins distributed by vendors have their own update systems. Their security depends on the vendor’s infrastructure. And nulled copies of premium plugins, distributed for free on dubious sites, are a supply chain attack by design; they often carry backdoors from the start.
Why automatic trust is the problem
Most of us update plugins with a click and move on. That habit is correct for security patches, but it means we trust every update completely. When the source of that update changes, that trust needs reassessing.
The aim isn’t to stop updating; that would be far more dangerous. The aim is to update with awareness, so you notice when something changes.
Practical defences
1. Keep fewer plugins
Every plugin is a dependency you trust. Fewer plugins means fewer owners, fewer update channels and fewer chances for something to go wrong. Review your plugins regularly and remove anything you don’t really need.
2. Prefer established, accountable developers
Plugins from developers and companies with a long track record, public contact details, clear support and a history of responsible security handling are lower risk. That doesn’t make them perfect, but accountability matters.
3. Watch for ownership changes
Signs that a plugin may have changed hands include:
- A new author name or company on the plugin page.
- A sudden change in the plugin’s description, branding or upsells.
- New features that don’t fit the plugin’s purpose, like tracking, advertising or links to unrelated services.
- A surge in updates after a long quiet period.
- Support forum posts from users noticing unexpected behaviour.
When you notice an ownership change on a plugin you depend on, read the next few changelogs carefully and test updates on staging before applying them to production.
4. Read changelogs for important plugins
For critical plugins, like those handling payments, logins, forms or security, skim changelogs before updating. Vague entries like “minor improvements” on a plugin that has never been vague before are worth a closer look. Changelogs that mention new data collection, external services or telemetry deserve attention too.
5. Use staging for high-risk sites
For stores, membership sites and business-critical sites, apply updates on staging first, test key functions and look for anything unusual: new admin menu items, new outgoing requests, new scripts on the front end or new database tables.
6. Monitor for unexpected behaviour
After updates, monitoring helps catch problems early:
- File integrity monitoring shows exactly which files an update changed.
- Activity logs reveal new administrator accounts, which several supply chain attacks have created.
- Outgoing request monitoring, available in some security tools and in Query Monitor’s HTTP API panel, shows new connections to external servers.
- Front-end script checks reveal new third-party scripts appearing on your pages.
7. Subscribe to vulnerability intelligence
Vulnerability databases and security vendors publish alerts about malicious updates and compromised plugins, often within hours of discovery. Subscribing to these alerts, or using a security service that checks your plugin list against them, means you hear quickly when a plugin you use is affected.
8. Pin and verify versions in professional workflows
If you manage plugins through Composer or version control, you can pin specific versions and review diffs before upgrading. Seeing exactly what changed between versions makes unexpected code much easier to spot. For agencies managing many sites, this kind of controlled rollout is worth the effort.
9. Never use nulled plugins or themes
This deserves repeating. Pirated premium plugins are one of the most reliable ways to infect a site, because the attacker controls the code from the beginning.
What to do when a plugin goes bad
If you discover a plugin you use has been compromised, sold to an untrustworthy owner or abandoned with known vulnerabilities:
- Check whether your sites ran the affected version. Plugin version history and update logs help here.
- Treat affected sites as potentially compromised. Look for new administrator accounts, unexpected files and outgoing connections.
- Remove or roll back the plugin. If a safe earlier version exists and the plugin is essential, roll back temporarily while you plan a replacement.
- Rotate credentials if there’s any chance data or accounts were exposed.
- Find a replacement. Test alternatives on staging, migrate data where needed and switch.
- Notify clients if you manage sites for others, explaining what happened and what you did.
Planning for abandoned plugins
Even without malice, abandonment is a slow-moving risk. Keep a plugin inventory that records, for each plugin:
- Why it’s installed.
- When it was last updated by its developer.
- Whether there’s a viable alternative.
Review it every few months. When a plugin goes quiet for a long time, especially one that handles user input or payments, start planning its replacement before a vulnerability forces your hand.
For essential functionality with no good alternative, consider whether a small custom plugin, maintained by you or your developer, would be safer than relying on an abandoned third-party one.
A simple supply chain routine
You don’t need an elaborate process to manage this risk. Once a month, look through the plugin list on each important site and ask three questions. Has anything changed author or owner? Has anything gone quiet for a long time? Has anything started behaving differently, with new admin notices, new menu items or new scripts on the front end? Note the answers in your plugin inventory. Most months, nothing changes. When something does, you’ll notice early.
Treat every plugin as a long-term relationship rather than a one-time install.
Frequently asked questions
Should I stop automatic updates because of supply chain risk?
Not for most sites. Unpatched vulnerabilities are a far bigger risk than malicious updates. For critical sites, apply updates through staging. For simpler sites, keep updates flowing and rely on monitoring and vulnerability alerts.
How do I know if a plugin has been sold?
Watch the plugin page for author changes, read changelogs and support forums, and pay attention to sudden changes in features, branding or upsells. Security news sources often report notable ownership changes.
Are premium plugins safer than free ones?
Not automatically. Premium plugins from reputable vendors often have dedicated teams, but they can also be sold, abandoned or compromised. Judge each plugin by its developer’s track record and maintenance.
What’s the biggest single protection?
Using fewer plugins from accountable developers, combined with monitoring that alerts you to unexpected changes.
Final thoughts
Every plugin update is an act of trust in whoever controls that plugin today. Keep your plugin list short, prefer accountable developers, watch for ownership changes, read changelogs for critical plugins, test updates on staging for important sites and monitor for unexpected behaviour. You don’t need to fear updates; you need to update with your eyes open.




