June 25th, 2024

Backdoor slipped into multiple WordPress plugins in ongoing supply-chain attack

A supply-chain attack compromised 36,000 websites using backdoored WordPress plugins. Malicious code added to updates creates attacker-controlled admin accounts, manipulating search results. Users urged to uninstall affected plugins and monitor for unauthorized access.

Read original articleLink Icon
Backdoor slipped into multiple WordPress plugins in ongoing supply-chain attack

A supply-chain attack has affected WordPress plugins on around 36,000 websites, with five plugins identified as being backdoored. Malicious functions were added to updates on WordPress.org, creating attacker-controlled admin accounts on compromised sites. The injected code aims to manipulate search results and is relatively straightforward, dating back to June 21, 2024. The affected plugins include Social Warfare, BLAZE Retail Widget, Wrapper Link Elementor, Contact Form 7 Multi-Step Addon, and Simply Show Hooks. Supply-chain attacks like this have become a prevalent method for malware distribution, exploiting users who trust software updates. Investigation is ongoing to determine how the malware was introduced into the plugins. Users are advised to uninstall the affected plugins, check for unauthorized admin accounts, and monitor for suspicious activity. WordPress, BLAZE, and Social Warfare have not yet responded to inquiries regarding the incident.

Link Icon 3 comments
By @markx2 - 4 months
I find this astonishing.

I worked at Automatic (in Support / Spam blog hunting / Akismet) in 2011 and after some bad plugin updating from various sources Matt asked me to start vetting wporg plugin updates.

I cannot code in PHP. Lots of reading later I could recognise dodgy code, or code that looked odd.

I set up a gmail account where _every_ new plugin commit was sent to, and I create a ton of filters, each looking for certain code. Those filters were then sent to me and were filtered again - think "Nasty, Maybe, Check"

When something bad happened, I'd review the commits, see the nasty, remove it, update the version, commit to the wporg repo and at the same time take over the account. (Again I can't code PHP but I'm listed as a developer in the plugin repo). That way plugin user was protected.

That was 13 years ago .. why the hell doesn't WP have a better system?

By @tonetegeatinst - 4 months
Glad they listed the plugins. I know that its not uncommon to read about some infected app that was on the app store and yet they never directly mention the app by name, just that is been removed.
By @beefnugs - 4 months
i wonder if there is a mathematical proof that future AI can never respect wordpress due to infinite history of bad press