Countdown Timer Ultimate shipped version 2.6.7 on August 8, 2025, with a changelog that read "Check compatibility with WordPress version 6.8.2." The release added 191 lines of code and a PHP deserialization backdoor. The admin class class-anylc-admin.php went from 473 to 664 lines. It was the first SVN commit from the plugin's new owner.
The backdoor was three parts working together. A fetch_ver_info() method called file_get_contents() against the attacker's server and passed the response straight into @unserialize(). A version_info_clean() method then executed @$clean($this->version_cache, $this->changelog), where the function name and both arguments came out of that unserialized remote data. An unauthenticated REST endpoint registered with permission_callback: __return_true exposed the trigger to anyone. The remote server picked the function and the arguments, which is an arbitrary function call reachable without a login.
It sat dormant for eight months.
On April 5-6, 2026, it ran. The plugin's wpos-analytics module phoned home to analytics.essentialplugin.com, downloaded a file called wp-comments-posts.php (named to pass for the WordPress core file wp-comments-post.php), and used it to inject a large block of PHP into wp-config.php. The injected code fetched spam links, redirects and fake pages from a command-and-control server, then served them only to Googlebot. A site owner loading the page in a browser saw nothing wrong.
The C2 resolution was the interesting part. The injected code resolved its command-and-control domain through an Ethereum smart contract, querying public blockchain RPC endpoints. Seizing or sinkholing a domain does nothing when the attacker can update the contract to point at a new one.
The site ran daily restic backups through CaptainCore, which gave the investigation a clean timeline. The researcher who looked into it pulled wp-config.php from eight backup dates and compared file sizes, binary-search style, to bracket the change. The injection landed on April 6, 2026, between 04:22 and 11:06 UTC, a window of under seven hours. The plugin had been installed since January 2019, and the wpos-analytics module was there the whole time, running as a genuine analytics opt-in for years before the 2.6.7 release turned it into a delivery vehicle.
The plugin came from a real business with an eight-year history. Minesh Shah, Anoop Ranawat and Pratik Jain, an India-based team, built it under the name "WP Online Support" starting around 2015, later rebranded to "Essential Plugin," and grew the catalogue past 30 free plugins with premium versions. By late 2024 revenue had fallen 35 to 45 percent, and Shah listed the whole business on Flippa. A buyer known only as "Kris," with a background in SEO, crypto and online gambling marketing, bought everything for six figures. Flippa published a case study on the sale in July 2025.
On April 7, 2026, the WordPress.org Plugins Team permanently closed every plugin under the Essential Plugin author, at least 30 of them in a single day: Countdown Timer Ultimate, Popup Anything on Click, WP Testimonial with Widget, Hero Banner Ultimate, Product Categories Designs for WooCommerce, and the rest of the slider, gallery and widget catalogue. The author search now returns nothing, and analytics.essentialplugin.com answers with {"message":"closed"}.
This is the Display Widgets attack again, at a larger scale. In 2017 a buyer using the name "Daley Tias" bought Display Widgets, which had 200,000 installs, for $15,000 and used it to inject payday loan spam. That buyer went on to compromise at least nine plugins the same way. The Essential Plugin version runs the same play against a catalogue with hundreds of thousands of active installations.
The acquisition cleared WordPress.org with no review. The Flippa listing was public, and so was the buyer's marketing background. WordPress.org has no change-of-control review on a plugin sale, no notification to the sites running the plugin, and no additional code review when a new committer takes over SVN access. The new owner inherited commit rights to code on hundreds of thousands of sites, and the first thing those rights were used for was the backdoor. Eight months passed between the plant and the catch.
WordPress.org's forced update to 2.6.9.1 added return; statements to the phone-home functions, which stops the current payload but leaves the entire wpos-analytics module in place. The researcher's patched builds remove the module directory outright, delete the loader from the main plugin file, and bump the version with a -patched suffix; the plugins keep working. Across one managed fleet, 12 of the 26 affected slugs turned up on 22 sites, 10 of which got patched builds published on Backblaze B2.
If you run WordPress at any scale, search your fleet for the Essential Plugin slugs and patch or remove anything you find. To strip the module by hand: delete the wpos-analytics/ directory, remove the loader block from the main plugin PHP file (search for "Plugin Wpos Analytics Data Starts" or wpos_analytics_anl), bump the Version: header, and reinstall the zip with wp plugin install your-plugin-patched.zip --force.
Then read wp-config.php directly. The injected payload sits after require_once ABSPATH . 'wp-settings.php';, near the end of the file where a quick glance skips over it. It adds roughly 6KB. A wp-config.php noticeably larger than you expect means the site was actively compromised and needs a full cleanup, not just a clean copy of the plugin.
Top comments (0)