
A major security incident has shaken the WordPress ecosystem after dozens of plug-ins were taken offline following the discovery of a hidden backdoor capable of distributing malicious code to thousands of websites. Backdoor
The breach highlights growing concerns around software supply chain attacks, particularly within widely used open-source platforms like WordPress, which powers a significant portion of the internet.

Table of Contents
Discovery of the Backdoor
The issue came to light after Austin Ginder, founder of Anchor Hosting, published a detailed blog post outlining what appears to be a coordinated supply chain attack.
According to Ginder, a plug-in developer known as Essential Plugin was acquired by an unknown buyer last year. Shortly after the acquisition, malicious code was quietly introduced into the source code of multiple plug-ins. Backdoor
The backdoor remained dormant for months before activating earlier this month. Once triggered, it began injecting harmful code into websites running the affected plug-ins, potentially exposing them to compromise, data theft, or further exploitation.
Scope and Impact
The scale of the incident is significant. Essential Plugin claims to have over 400,000 installations and more than 15,000 customers. Meanwhile, WordPress data indicates that the compromised plug-ins were actively installed on at least 20,000 websites.
Plug-ins play a critical role in extending WordPress functionality—from SEO tools to security features—but they also require deep access to website systems. This level of access makes them an attractive target for attackers seeking to infiltrate multiple websites through a single vulnerability.
A Growing Attack Trend
Ginder noted that this is the second known hijacking of a WordPress plug-in within weeks, underscoring a troubling trend. Security experts have long warned that malicious actors may acquire legitimate software projects and subtly alter their code to distribute malware at scale.
One key concern raised is the lack of transparency in plug-in ownership changes. WordPress users are not automatically notified when a plug-in changes hands, leaving site owners vulnerable to silent takeovers and hidden threats.
Response and Mitigation
In response to the discovery, the affected plug-ins have been removed from the WordPress directory and are now marked as permanently closed. However, the risk remains for websites that still have the compromised plug-ins installed.
Ginder strongly advises WordPress site owners to immediately audit their installations, identify any affected plug-ins, and remove them without delay. A full list of compromised plug-ins has been published in his blog post.
As of now, representatives from Essential Plugin have not issued an official response.
Broader Implications
This incident serves as a stark reminder of the vulnerabilities inherent in modern software ecosystems. While open-source platforms like WordPress offer flexibility and scalability, they also rely heavily on third-party contributions—making them susceptible to supply chain attacks.
For businesses and developers, the takeaway is clear: maintaining strict oversight of third-party tools, regularly auditing code, and implementing robust security practices are no longer optional—they are essential.
As cyber threats continue to evolve, the integrity of even trusted software components can no longer be taken for granted.



