<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Decodeinfy</title>
    <description>The latest articles on DEV Community by Decodeinfy (@decodeinfy_60e750d3bbfab5).</description>
    <link>https://dev.to/decodeinfy_60e750d3bbfab5</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4206546%2F298e9bbb-aed2-4ef3-bf9f-0ed5dd37d123.jpg</url>
      <title>DEV Community: Decodeinfy</title>
      <link>https://dev.to/decodeinfy_60e750d3bbfab5</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/decodeinfy_60e750d3bbfab5"/>
    <language>en</language>
    <item>
      <title>How to Fix a WordPress Site Redirecting to Spam</title>
      <dc:creator>Decodeinfy</dc:creator>
      <pubDate>Mon, 16 Nov 2026 00:00:00 +0000</pubDate>
      <link>https://dev.to/decodeinfy_60e750d3bbfab5/how-to-fix-a-wordpress-site-redirecting-to-spam-51kh</link>
      <guid>https://dev.to/decodeinfy_60e750d3bbfab5/how-to-fix-a-wordpress-site-redirecting-to-spam-51kh</guid>
      <description>&lt;p&gt;&lt;em&gt;If your WordPress site sends visitors to spam pages, an attacker has added conditional redirect code to your site files or database. Here is how to reproduce the issue safely, locate the code, remove it, and find out how it got in.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Why WordPress sites redirect visitors to spam sites
&lt;/h2&gt;

&lt;p&gt;When a WordPress site gets hacked with redirect malware, the redirect rarely happens for every visitor. If every page redirected immediately, the site owner would spot the problem right away. Attackers use conditional rules so the site functions normally for you while redirecting specific groups of visitors to spam or scam websites.&lt;/p&gt;

&lt;p&gt;Malicious scripts evaluate HTTP request headers sent by a visitor's browser. They check two key details:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;User-Agent:&lt;/strong&gt; This identifies the device and browser. Attackers often target mobile visitors on iOS or Android devices while leaving desktop users untouched.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;HTTP Referer:&lt;/strong&gt; This records the page the visitor came from. The script checks if the visitor arrived from search engines like Google, Bing, or Yahoo.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;When a real user searches for your business on a smartphone and clicks your site in Google search results, their browser sends a mobile User-Agent and a Google HTTP Referer header. The malicious script detects both, overrides your normal site output, and issues an HTTP 301 or 302 redirect to an external URL. If you open a browser and type your URL directly into the address bar, there is no search referrer, so the page loads normally.&lt;/p&gt;

&lt;p&gt;This mechanism is closely related to search engine cloaking, similar to the techniques explained in our guide on the &lt;a href="https://ownertrail.decodeinfy.in/articles/wordpress-japanese-keyword-hack-googlebot-cloaking/" rel="noopener noreferrer"&gt;Japanese keyword hack and cloaking&lt;/a&gt;, where attackers serve different content to search engines and normal visitors.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to safely test and reproduce the redirect
&lt;/h2&gt;

&lt;p&gt;Testing conditional redirects by tapping links on your phone can be frustrating. Web browsers cache redirect responses aggressively, meaning your phone might keep redirecting even after you clean the site, or fail to show the redirect because you visited the site directly earlier.&lt;/p&gt;

&lt;p&gt;The safest way to reproduce and inspect the redirect is using command-line tools like &lt;code&gt;curl&lt;/code&gt;, which send requests without executing script payloads or caching headers.&lt;/p&gt;

&lt;p&gt;Open a terminal on your computer and run this command to inspect your homepage headers while simulating a mobile visitor arriving from Google:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl -I -A &lt;span class="s2"&gt;"Mozilla/5.0 (iPhone; CPU iPhone OS 16_0 like Mac OS X) AppleWebKit/605.1.15"&lt;/span&gt; -e &lt;span class="s2"&gt;"https://www.google.com/"&lt;/span&gt; https://your-site.com/
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Examine the first line of the output:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A clean site returns &lt;code&gt;HTTP/2 200 OK&lt;/code&gt; or &lt;code&gt;HTTP/1.1 200 OK&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;A compromised site returns &lt;code&gt;HTTP/2 302 Found&lt;/code&gt; or &lt;code&gt;301 Moved Permanently&lt;/code&gt;, followed by a &lt;code&gt;Location:&lt;/code&gt; header listing an unfamiliar domain name.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;You can also use Google Chrome Developer Tools. Open a new Incognito window, open Developer Tools (F12), switch to the Device Toolbar to select an iPhone or Android preset, and navigate to the Network tab. Under Network Conditions, uncheck "Use browser default" for User-Agent and set custom request headers to test how your server responds to search engine referrers.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where malicious redirect code hides on your server
&lt;/h2&gt;

&lt;p&gt;Malicious code must run early in the loading process to redirect visitors before your page finishes rendering. Attackers usually place code in one of five locations:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;The &lt;code&gt;.htaccess&lt;/code&gt; file:&lt;/strong&gt; On Apache web servers, attackers insert rewrite rules near the top of &lt;code&gt;.htaccess&lt;/code&gt;. These rules inspect the incoming request for search referrers or mobile strings and redirect matching requests directly at the web server level before PHP even runs.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Core startup files:&lt;/strong&gt; Attackers alter files like &lt;code&gt;index.php&lt;/code&gt;, &lt;code&gt;wp-config.php&lt;/code&gt;, or &lt;code&gt;wp-settings.php&lt;/code&gt;. They insert obfuscated PHP functions like &lt;code&gt;eval(base64_decode(...))&lt;/code&gt; or &lt;code&gt;gzuncompress()&lt;/code&gt; near the top of the file. Performing a regular &lt;a href="https://ownertrail.decodeinfy.in/articles/wordpress-file-integrity-check/" rel="noopener noreferrer"&gt;WordPress file integrity check&lt;/a&gt; helps detect core files that differ from official release versions.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Theme and plugin files:&lt;/strong&gt; Code can be added to your active theme's &lt;code&gt;functions.php&lt;/code&gt; file or hidden deep inside an installed plugin.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Standalone PHP files in upload folders:&lt;/strong&gt; Attackers often drop unauthorized PHP scripts into media directories. Finding &lt;a href="https://ownertrail.decodeinfy.in/articles/php-files-in-wordpress-uploads-folder-polyglot-malware/" rel="noopener noreferrer"&gt;PHP files in your WordPress uploads folder&lt;/a&gt; is a clear signal of leftover backdoor scripts used to maintain unauthorized access.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The WordPress database:&lt;/strong&gt; Malicious JavaScript can be injected into the &lt;code&gt;wp_options&lt;/code&gt; table inside fields like &lt;code&gt;siteurl&lt;/code&gt;, &lt;code&gt;home&lt;/code&gt;, or auto-loaded option entries designed to inject scripts into your site header or footer.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  How to clean malicious redirects from your site
&lt;/h2&gt;

&lt;p&gt;Cleaning a site requires systematically replacing code files rather than deleting individual lines by hand, because manual edits often leave hidden backdoor files behind.&lt;/p&gt;

&lt;p&gt;Follow these steps to clean your installation:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Create a backup:&lt;/strong&gt; Save a complete copy of your site files and database for reference before making changes.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Reset core files:&lt;/strong&gt; Download a fresh zip archive of your exact WordPress version from WordPress.org. On your server, replace the &lt;code&gt;wp-admin&lt;/code&gt; and &lt;code&gt;wp-includes&lt;/code&gt; folders entirely. Replace root files like &lt;code&gt;index.php&lt;/code&gt;, &lt;code&gt;wp-activate.php&lt;/code&gt;, and &lt;code&gt;wp-blog-header.php&lt;/code&gt;. Inspect &lt;code&gt;wp-config.php&lt;/code&gt; by hand to verify that every line belongs there.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Replace &lt;code&gt;.htaccess&lt;/code&gt;:&lt;/strong&gt; Delete your current &lt;code&gt;.htaccess&lt;/code&gt; file and create a new one containing standard WordPress rewrite rules.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Reinstall plugins and themes:&lt;/strong&gt; Delete all folders inside &lt;code&gt;wp-content/plugins/&lt;/code&gt; and reinstall fresh copies from official sources. Delete and reinstall your theme folders under &lt;code&gt;wp-content/themes/&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Clean media directories:&lt;/strong&gt; Search the &lt;code&gt;wp-content/uploads/&lt;/code&gt; directory for any files ending in &lt;code&gt;.php&lt;/code&gt;, &lt;code&gt;.php5&lt;/code&gt;, or &lt;code&gt;.htaccess&lt;/code&gt; and delete them. Upload folders should contain media files like images, videos, and PDFs, not executable code.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Check database options:&lt;/strong&gt; Log into phpMyAdmin or use WP-CLI to inspect your database. Check the &lt;code&gt;wp_options&lt;/code&gt; table to ensure &lt;code&gt;siteurl&lt;/code&gt; and &lt;code&gt;home&lt;/code&gt; match your domain. Inspect header and footer settings added by options plugins to remove embedded JavaScript redirects.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Finding out how the unauthorized access happened
&lt;/h2&gt;

&lt;p&gt;Cleaning your site removes the current redirect, but if you do not identify the entry point, the site can be reinfected. Work through these steps to investigate how access was gained:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Check server access logs:&lt;/strong&gt; Request your web server's HTTP access logs from your hosting provider. Search for &lt;code&gt;POST&lt;/code&gt; requests made around the time the redirect first appeared. Pay close attention to requests sent directly to files inside &lt;code&gt;wp-content/uploads/&lt;/code&gt; or repeated access to &lt;code&gt;xmlrpc.php&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Review file modification dates:&lt;/strong&gt; Use your FTP client or hosting file manager to sort files by modification date. If multiple files across different plugin or core folders share the exact same recent timestamp, open those files to inspect recent changes.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Audit user accounts and credentials:&lt;/strong&gt; Check &lt;code&gt;Users &amp;gt; All Users&lt;/code&gt; in your WordPress dashboard for unfamiliar administrator accounts. Change all passwords associated with the site, including WordPress admin accounts, database credentials, FTP/SFTP accounts, and hosting control panel logins.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Check plugin supply chain status:&lt;/strong&gt; Unpatched vulnerabilities in outdated plugins or sudden changes in plugin maintainers are common access vectors. Ensure all active plugins receive regular updates from verified developers.&lt;/p&gt;

&lt;h2&gt;
  
  
  How OwnerTrail alerts you to file changes and supply chain risks
&lt;/h2&gt;

&lt;p&gt;OwnerTrail is a free WordPress plugin available on &lt;a href="https://wordpress.org/plugins/ownertrail/" rel="noopener noreferrer"&gt;WordPress.org&lt;/a&gt;. It helps site owners monitor changes to their installation so unexpected file modifications can be reviewed immediately.&lt;/p&gt;

&lt;p&gt;Every day, OwnerTrail runs automatic checks on your core, plugin, and theme files against official WordPress.org releases. It reads unvouched files on your server to look for the shapes malware takes, and reports any PHP files found in folders like uploads, languages, fonts, upgrade, or backup directories where code does not belong.&lt;/p&gt;

&lt;p&gt;To help spot conditional redirects and search engine cloaking early, OwnerTrail fetches your pages as Googlebot. It checks what search engines see versus what normal visitors see, flagging SEO spam hacks and cloaking attempts.&lt;/p&gt;

&lt;p&gt;OwnerTrail also monitors plugin ownership and maintenance. It tracks plugin owner changes, checks public SVN commit history for new committers, identifies dormant plugins that suddenly release updates, and alerts you if a plugin has been closed on WordPress.org. Each plugin is assigned a trust score from 0 to 100, and you can enable email notifications with one click to receive alerts when something needs attention.&lt;/p&gt;

&lt;p&gt;For added control over file modifications, OwnerTrail includes Code lock, ensuring code on the site can only be changed over FTP, which only a site owner can loosen. From version 1.3.6, when an installed plugin changes hands, its next update is held until the site owner acknowledges the ownership change.&lt;/p&gt;

&lt;p&gt;OwnerTrail Pro is coming soon, adding features to approve exact update versions, restore changed files with undo history, quarantine unexpected files, grant time-limited developer access, and set custom policy gates.&lt;/p&gt;
&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;        &amp;lt;p&amp;gt;&amp;lt;strong&amp;gt;About OwnerTrail.&amp;lt;/strong&amp;gt; A free WordPress plugin that watches who controls every plugin on your site, flags plugins WordPress.org has closed, checks your code against WordPress.org's fingerprints, and fetches your pages as Googlebot to catch spam shown only to search engines. It detects; it is not a firewall. &amp;lt;a href="https://wordpress.org/plugins/ownertrail/"&amp;gt;Free on WordPress.org&amp;lt;/a&amp;gt;.&amp;lt;/p&amp;gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;
&lt;p&gt;Related: &lt;a href="https://ownertrail.decodeinfy.in/articles/wordpress-japanese-keyword-hack-googlebot-cloaking/" rel="noopener noreferrer"&gt;The Japanese keyword hack: SEO spam that hides from you and shows itself to Google&lt;/a&gt; and &lt;a href="https://ownertrail.decodeinfy.in/articles/wordpress-file-integrity-check/" rel="noopener noreferrer"&gt;WordPress file integrity check: was your plugin code changed?&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>wordpress</category>
      <category>security</category>
      <category>webdev</category>
      <category>php</category>
    </item>
    <item>
      <title>How to Remove the Japanese Keyword Hack from WordPress</title>
      <dc:creator>Decodeinfy</dc:creator>
      <pubDate>Sun, 08 Nov 2026 00:00:00 +0000</pubDate>
      <link>https://dev.to/decodeinfy_60e750d3bbfab5/how-to-remove-the-japanese-keyword-hack-from-wordpress-1ca9</link>
      <guid>https://dev.to/decodeinfy_60e750d3bbfab5/how-to-remove-the-japanese-keyword-hack-from-wordpress-1ca9</guid>
      <description>&lt;p&gt;&lt;em&gt;If Google shows search results for your website filled with Japanese text, your site has been compromised by SEO spam. Here is the step-by-step process to locate the malicious files, restore your clean WordPress installation, and request a fresh crawl from Google.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Confirming the Japanese keyword hack on your site
&lt;/h2&gt;

&lt;p&gt;The Japanese keyword hack is a form of search engine optimization (SEO) spam. Attackers add code to your site that generates thousands of pages full of auto-generated text and links to foreign store pages selling counterfeit goods. This spam is usually hidden from normal visitors but shown directly to search engine crawlers, a technique known as cloaking.&lt;/p&gt;

&lt;p&gt;You will often first notice this problem when your traffic drops or when you search for your brand name on Google and see Japanese text in the snippet descriptions. To confirm whether your site is affected, start by checking Google Search Console.&lt;/p&gt;

&lt;p&gt;Log into Google Search Console and navigate to the &lt;strong&gt;Pages&lt;/strong&gt; report under the Index section. Look for a sudden spike in indexed pages, or search the list for unexpected URLs. If you see hundreds or thousands of URLs containing random characters or terms you never published, your site has been indexed with spam.&lt;/p&gt;

&lt;p&gt;Next, confirm how your site appears to search engines by fetching a page as Googlebot. You can do this inside Google Search Console using the &lt;strong&gt;URL Inspection&lt;/strong&gt; tool. Enter your homepage URL or an affected page URL, click &lt;strong&gt;Inspect&lt;/strong&gt; , and then view the tested page HTML. If the HTML response contains Japanese text, Japanese titles, or links to external shopping domains that do not appear when you open your site in a normal browser, cloaking is active on your site. For a deeper look at why this happens, read our guide on &lt;a href="https://ownertrail.decodeinfy.in/articles/wordpress-japanese-keyword-hack-googlebot-cloaking/" rel="noopener noreferrer"&gt;how Japanese keyword hack cloaking works&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Finding where the spam script runs from
&lt;/h2&gt;

&lt;p&gt;Before you can remove the spam, you must locate the code that generates it. Malware behind this hack usually consists of two parts: a door opener file that intercepts incoming requests, and a generator script that fetches spam content from a remote server.&lt;/p&gt;

&lt;p&gt;Check the following places in your WordPress directory structure through your hosting control panel file manager or FTP client:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Start-up and core root files:&lt;/strong&gt; Open &lt;code&gt;index.php&lt;/code&gt;, &lt;code&gt;wp-config.php&lt;/code&gt;, &lt;code&gt;.htaccess&lt;/code&gt;, and &lt;code&gt;wp-settings.php&lt;/code&gt; in your main website folder. Look for unusual code near the top of these files, particularly lines that use functions like &lt;code&gt;base64_decode&lt;/code&gt;, &lt;code&gt;gzinflate&lt;/code&gt;, &lt;code&gt;eval&lt;/code&gt;, or &lt;code&gt;curl_exec&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Must-use plugins:&lt;/strong&gt; Open the folder &lt;code&gt;wp-content/mu-plugins/&lt;/code&gt;. Code inside this directory runs automatically on every request without appearing in your main WordPress admin plugin list. If you see files here that you or your developer did not intentionally install, inspect their contents.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;PHP files in the uploads folder:&lt;/strong&gt; Media uploads should only contain images, documents, and standard media formats. Open &lt;code&gt;wp-content/uploads/&lt;/code&gt; and search for any file ending in &lt;code&gt;.php&lt;/code&gt;. Executable scripts placed in uploads are almost always malicious. Learn more about identifying these scripts in our article on &lt;a href="https://ownertrail.decodeinfy.in/articles/php-files-in-wordpress-uploads-folder-polyglot-malware/" rel="noopener noreferrer"&gt;PHP files in the WordPress uploads directory&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Altered core or plugin files:&lt;/strong&gt; Hackers frequently insert small snippets of code into official core files inside &lt;code&gt;wp-includes/&lt;/code&gt; or existing plugins to ensure the spam regenerates even if you delete a stand-alone malware file. Review our guide on &lt;a href="https://ownertrail.decodeinfy.in/articles/wordpress-file-integrity-check/" rel="noopener noreferrer"&gt;checking WordPress file integrity&lt;/a&gt; to see how modified files are identified.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Restoring WordPress core, plugins, and themes from official releases
&lt;/h2&gt;

&lt;p&gt;Attempting to clean individual infected files manually is slow and risks leaving hidden code behind. The safest and fastest way to clean a site is to replace all core, plugin, and theme files with fresh, original files from official sources.&lt;/p&gt;

&lt;p&gt;Follow these exact steps to replace your core WordPress files:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Download a fresh copy of the official WordPress release from &lt;code&gt;wordpress.org&lt;/code&gt; that matches your current installed version.&lt;/li&gt;
&lt;li&gt;Extract the ZIP archive on your computer. Delete the &lt;code&gt;wp-content&lt;/code&gt; folder from the extracted files on your computer so you do not accidentally overwrite your uploads or custom code.&lt;/li&gt;
&lt;li&gt;Using your FTP client or hosting file manager, delete the existing &lt;code&gt;wp-admin&lt;/code&gt; and &lt;code&gt;wp-includes&lt;/code&gt; directories on your server.&lt;/li&gt;
&lt;li&gt;Upload the fresh &lt;code&gt;wp-admin&lt;/code&gt; and &lt;code&gt;wp-includes&lt;/code&gt; directories from your computer to your server.&lt;/li&gt;
&lt;li&gt;Replace the root files in your main site directory (such as &lt;code&gt;index.php&lt;/code&gt;, &lt;code&gt;wp-login.php&lt;/code&gt;, &lt;code&gt;wp-settings.php&lt;/code&gt;) with the fresh versions from the official download. Leave your existing &lt;code&gt;wp-config.php&lt;/code&gt; file in place.&lt;/li&gt;
&lt;li&gt;Open your server's &lt;code&gt;.htaccess&lt;/code&gt; file and replace its contents with the default WordPress rewrite rules.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Next, clean your plugins and themes. Go to &lt;code&gt;wp-content/plugins/&lt;/code&gt; on your server. Delete each plugin folder and re-download fresh copies directly from the WordPress.org plugin directory or your commercial vendor accounts. Repeat this process for your themes inside &lt;code&gt;wp-content/themes/&lt;/code&gt;, ensuring you replace every file with an unmodified original copy.&lt;/p&gt;

&lt;h2&gt;
  
  
  Securing administrator accounts, passwords, and security keys
&lt;/h2&gt;

&lt;p&gt;Replacing files removes the active malware, but you must also close the entry points that allowed the attacker to upload the files in the first place.&lt;/p&gt;

&lt;p&gt;First, log into your WordPress admin dashboard and go to &lt;strong&gt;Users&lt;/strong&gt;. Review every account listed with the Administrator role. If you see accounts you do not recognize, delete them immediately and attribute any content they created to your primary account.&lt;/p&gt;

&lt;p&gt;Second, change all passwords associated with the website. This includes:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;All WordPress administrator accounts&lt;/li&gt;
&lt;li&gt;Your hosting control panel login (cPanel, Plesk, or cloud dashboard)&lt;/li&gt;
&lt;li&gt;FTP, SFTP, and SSH user accounts&lt;/li&gt;
&lt;li&gt;Your WordPress database user password&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Third, reset your WordPress authentication keys and salts. Open your &lt;code&gt;wp-config.php&lt;/code&gt; file and locate the section containing &lt;code&gt;AUTH_KEY&lt;/code&gt;, &lt;code&gt;SECURE_AUTH_KEY&lt;/code&gt;, and related security definitions. Visit the official WordPress salt generator service at &lt;code&gt;api.wordpress.org/secret-key/1.1/salt/&lt;/code&gt; to generate a brand new set of random keys. Paste these new values over the old ones in &lt;code&gt;wp-config.php&lt;/code&gt; and save the file. Changing these keys invalidates all existing logged-in sessions and cookies across the site, forcing anyone currently logged in to re-authenticate.&lt;/p&gt;

&lt;h2&gt;
  
  
  Requesting Google to recrawl your clean website
&lt;/h2&gt;

&lt;p&gt;Once the malicious files are removed and your core files are restored, the spam pages on your site will return a 404 Not Found HTTP status code. However, search engine indexes may still display the cached Japanese titles and descriptions for several days or weeks until Google re-indexes the site.&lt;/p&gt;

&lt;p&gt;To accelerate this recovery process, log into Google Search Console:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Use the &lt;strong&gt;URL Inspection&lt;/strong&gt; tool to check your homepage and primary landing pages. Click &lt;strong&gt;Request Indexing&lt;/strong&gt; to prompt Googlebot to fetch the fresh, clean version of your pages.&lt;/li&gt;
&lt;li&gt;If you have an XML sitemap, regenerate it using your SEO plugin so it only lists valid, active pages. Go to &lt;strong&gt;Sitemaps&lt;/strong&gt; in Search Console and resubmit your main sitemap URL.&lt;/li&gt;
&lt;li&gt;Monitor the &lt;strong&gt;Pages&lt;/strong&gt; report over the coming weeks. You will see the number of indexed spam pages drop steadily as Google attempts to crawl the old spam URLs and receives 404 responses.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Leave the spam URLs reachable: do not shut them off in &lt;code&gt;.htaccess&lt;/code&gt; or robots.txt. Googlebot needs to access those URLs and receive a 404 or 410 response to confirm they are permanently gone and remove them from search results.&lt;/p&gt;

&lt;h2&gt;
  
  
  How OwnerTrail helps monitor your site for changes
&lt;/h2&gt;

&lt;p&gt;OwnerTrail is a free WordPress plugin available on WordPress.org. It helps site owners stay informed about changes to their website environment before security issues lead to search engine spam.&lt;/p&gt;

&lt;p&gt;Every day, OwnerTrail performs essential automated integrity checks:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;It checks WordPress core, plugin, and theme files against the official release of each one to spot unexpected code modifications.&lt;/li&gt;
&lt;li&gt;It reads files that nothing vouches for, looking for the shapes malware takes.&lt;/li&gt;
&lt;li&gt;It reports PHP and other code files located in folders where executable code does not belong, such as the &lt;code&gt;uploads&lt;/code&gt;, &lt;code&gt;languages&lt;/code&gt;, &lt;code&gt;fonts&lt;/code&gt;, &lt;code&gt;upgrade&lt;/code&gt;, and &lt;code&gt;backup&lt;/code&gt; directories.&lt;/li&gt;
&lt;li&gt;It fetches your own pages as Googlebot to catch SEO spam, cloaking, and the Japanese keyword hack as early as possible.&lt;/li&gt;
&lt;li&gt;It watches who controls each plugin you have installed, flagging changes of ownership, new committers in public SVN commit history, dormant plugins that suddenly release updates, or plugins closed on WordPress.org.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;OwnerTrail gives each plugin a trust score from 0 to 100 and can email you immediately when a finding needs your attention. It also features Code Lock, ensuring code on the site can only be modified over FTP unless a site owner explicitly loosens the lock. From version 1.3.6, when a plugin changes hands, its next update is held until the site owner acknowledges the change.&lt;/p&gt;

&lt;p&gt;OwnerTrail detects and warns; it is not a firewall. To learn more about its detection capabilities and read detailed research, visit &lt;a href="https://ownertrail.decodeinfy.in/" rel="noopener noreferrer"&gt;the official OwnerTrail website&lt;/a&gt;.&lt;/p&gt;
&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;        &amp;lt;p&amp;gt;&amp;lt;strong&amp;gt;About OwnerTrail.&amp;lt;/strong&amp;gt; A free WordPress plugin that watches who controls every plugin on your site, flags plugins WordPress.org has closed, checks your code against WordPress.org's fingerprints, and fetches your pages as Googlebot to catch spam shown only to search engines. It detects; it is not a firewall. &amp;lt;a href="https://wordpress.org/plugins/ownertrail/"&amp;gt;Free on WordPress.org&amp;lt;/a&amp;gt;.&amp;lt;/p&amp;gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;
&lt;p&gt;Related: &lt;a href="https://ownertrail.decodeinfy.in/articles/wordpress-japanese-keyword-hack-googlebot-cloaking/" rel="noopener noreferrer"&gt;The Japanese keyword hack: SEO spam that hides from you and shows itself to Google&lt;/a&gt; and &lt;a href="https://ownertrail.decodeinfy.in/articles/php-files-in-wordpress-uploads-folder-polyglot-malware/" rel="noopener noreferrer"&gt;A PHP file in your uploads folder is never supposed to be there&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>wordpress</category>
      <category>security</category>
      <category>webdev</category>
      <category>php</category>
    </item>
    <item>
      <title>The Japanese keyword hack: SEO spam that hides from you and shows itself to Google</title>
      <dc:creator>Decodeinfy</dc:creator>
      <pubDate>Fri, 30 Oct 2026 10:58:45 +0000</pubDate>
      <link>https://dev.to/decodeinfy_60e750d3bbfab5/the-japanese-keyword-hack-seo-spam-that-hides-from-you-and-shows-itself-to-google-kfd</link>
      <guid>https://dev.to/decodeinfy_60e750d3bbfab5/the-japanese-keyword-hack-seo-spam-that-hides-from-you-and-shows-itself-to-google-kfd</guid>
      <description>&lt;p&gt;&lt;em&gt;You open your site and it looks fine. Google has indexed hundreds of pages you never wrote. That gap is the whole trick, and it is checkable.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;The &lt;strong&gt;Japanese keyword hack&lt;/strong&gt; is one of the most common WordPress compromises, and one of the hardest for an owner to notice. The attacker does not deface your site. They add pages, thousands of them, selling counterfeit goods or pharmaceuticals, and they show those pages only to search engines. To you, logged in or just visiting, the site looks exactly as it did.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why you cannot see it
&lt;/h2&gt;

&lt;p&gt;The injected code checks who is asking for the page. It reads the &lt;code&gt;User-Agent&lt;/code&gt; header, and sometimes the visitor's IP or where they arrived from. If the request looks like Googlebot, it serves the spam. If it looks like an ordinary browser, it serves your real page. This is &lt;strong&gt;cloaking&lt;/strong&gt; : one URL, two different answers.&lt;/p&gt;

&lt;p&gt;So the damage lands entirely in Google's index. Your rankings get hijacked, your listings sprout Japanese titles, and Google eventually flags the site as hacked, all while your own browser shows nothing wrong.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where it hides
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;A few lines prepended to &lt;code&gt;wp-config.php&lt;/code&gt; or &lt;code&gt;index.php&lt;/code&gt;, so the code runs before WordPress on every request.&lt;/li&gt;
&lt;li&gt;A PHP file dropped into &lt;code&gt;wp-content/uploads&lt;/code&gt; and pulled in by an &lt;code&gt;.htaccess&lt;/code&gt; or &lt;code&gt;.user.ini&lt;/code&gt; rule.&lt;/li&gt;
&lt;li&gt;A changed core or plugin file that no longer matches the genuine release.&lt;/li&gt;
&lt;li&gt;A rewritten &lt;code&gt;robots.txt&lt;/code&gt; or a fake &lt;code&gt;sitemap.xml&lt;/code&gt; pointing Google at the spam.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  How to check for it by hand
&lt;/h2&gt;

&lt;p&gt;Ask your own site for a page the way Googlebot would, and compare it with an ordinary request:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl &lt;span class="nt"&gt;-s&lt;/span&gt; https://example.com/ | &lt;span class="nb"&gt;wc&lt;/span&gt; &lt;span class="nt"&gt;-c&lt;/span&gt;
curl &lt;span class="nt"&gt;-s&lt;/span&gt; &lt;span class="nt"&gt;-A&lt;/span&gt; &lt;span class="s2"&gt;"Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)"&lt;/span&gt; https://example.com/ | &lt;span class="nb"&gt;wc&lt;/span&gt; &lt;span class="nt"&gt;-c&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If the two pages differ in size, title, language, or links, and you did not build them to, that is cloaking. Also search Google for &lt;code&gt;site:example.com&lt;/code&gt; and look for pages and languages you never published.&lt;/p&gt;

&lt;p&gt;One caution: a cloaked page does not always answer a spoofed Googlebot from the wrong IP. Serious attackers verify the request really comes from Google's address range, so a single curl can come back clean. The reliable tell is the gap between what Google has indexed and what your site actually contains.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Googlebot canary, every day
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://ownertrail.decodeinfy.in/" rel="noopener noreferrer"&gt;OwnerTrail&lt;/a&gt; runs this comparison for you, once a day, from your own server. It requests a handful of your pages three ways, as an ordinary browser, as Googlebot, and as a visitor arriving from a Google search, and compares the answers: the title, the language, the size, the links, and any redirect to another site.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Spam shown only to the crawler, a redirect that fires only for search visitors, or a sudden wall of links one view has and the others do not, is reported as a serious finding and emailed within the hour.&lt;/li&gt;
&lt;li&gt;It ignores the differences that are not cloaking: a firewall refusing a spoofed Googlebot (a 403 or 503), and the nonces, cache-busters and tracking tags that change on every request.&lt;/li&gt;
&lt;li&gt;No page content leaves your site.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;It will not remove the spam for you, that is a clean-up job, but it ends the months of not knowing. The sooner you see the gap, the less of your ranking you lose.&lt;/p&gt;
&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;        &amp;lt;p&amp;gt;&amp;lt;strong&amp;gt;About OwnerTrail.&amp;lt;/strong&amp;gt; A free WordPress plugin that checks every code file against WordPress.org's official fingerprints daily, reads unverified files for the shapes malware takes, asks your own pages as Googlebot to catch cloaked SEO spam, and watches who controls each plugin. No telemetry. &amp;lt;a href="https://ownertrail.decodeinfy.in/"&amp;gt;How it works&amp;lt;/a&amp;gt;.&amp;lt;/p&amp;gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;
&lt;p&gt;Related: &lt;a href="https://ownertrail.decodeinfy.in/articles/php-files-in-wordpress-uploads-folder-polyglot-malware/" rel="noopener noreferrer"&gt;PHP files hidden in your uploads folder&lt;/a&gt; and &lt;a href="https://ownertrail.decodeinfy.in/articles/wordpress-file-integrity-check/" rel="noopener noreferrer"&gt;how to check your files are genuine&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>wordpress</category>
      <category>security</category>
      <category>webdev</category>
      <category>php</category>
    </item>
    <item>
      <title>EssentialPlugin backdoor, replayed: 31 of 31 warned</title>
      <dc:creator>Decodeinfy</dc:creator>
      <pubDate>Tue, 27 Oct 2026 09:59:19 +0000</pubDate>
      <link>https://dev.to/decodeinfy_60e750d3bbfab5/essentialplugin-backdoor-replayed-31-of-31-warned-2o3e</link>
      <guid>https://dev.to/decodeinfy_60e750d3bbfab5/essentialplugin-backdoor-replayed-31-of-31-warned-2o3e</guid>
      <description>&lt;p&gt;&lt;em&gt;Thirty-one plugins, one backdoor, eight months of silence. We replayed OwnerTrail's rules against what was public at the time, week by week, to see when it would have spoken up.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The short answer: yes, on all 31.&lt;/strong&gt; Every plugin would have raised OwnerTrail's high-severity “new committer” finding, naming the account that shipped the backdoor, within a week of that account's first commit. The warning would have arrived &lt;strong&gt;41 to 321 days before the backdoor switched on&lt;/strong&gt; , with a median of 139 days.&lt;/p&gt;

&lt;p&gt;This page shows how we tested that, what OwnerTrail would and would not have done, and the limits of the claim.&lt;/p&gt;

&lt;h2&gt;
  
  
  What happened
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Around May 2025 a buyer acquired a portfolio of more than thirty WordPress plugins on Flippa for a reported six-figure sum, and with it their commit access.&lt;/li&gt;
&lt;li&gt;The new owner's first release, on 8 August 2025, carried a backdoor. It did nothing for eight months.&lt;/li&gt;
&lt;li&gt;Around 5 April 2026 it switched on: it rewrote &lt;code&gt;wp-config.php&lt;/code&gt; and injected spam pages and redirects across roughly 400,000 declared installs.&lt;/li&gt;
&lt;li&gt;On 7 April 2026 the WordPress Plugins Team closed all 31 plugins in a single day.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;WordPress.org checks that the old owner agreed to a transfer. It does not vet the buyer, review the new owner's first release, or tell anyone running the plugin that it changed hands. That gap is &lt;a href="https://meta.trac.wordpress.org/ticket/5509" rel="noopener noreferrer"&gt;documented and still open&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  How we replayed it
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;The data:&lt;/strong&gt; each plugin's full commit history from &lt;code&gt;plugins.svn.wordpress.org&lt;/code&gt;, fetched with the same request OwnerTrail makes. It is still public after the closure.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The site:&lt;/strong&gt; OwnerTrail installed on 6 January 2025, scanning once a week. It actually scans daily, so weekly is the cautious case.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The rules:&lt;/strong&gt; two of OwnerTrail's detection rules, unchanged in their logic: a first commit by an account not seen before (high severity), and a release after 180 or more days without commits (medium).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Not replayed:&lt;/strong&gt; the change of listed author and contributors, because the directory data for closed plugins is gone. Real installs would have had that signal too.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What it found
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Signal&lt;/th&gt;
&lt;th&gt;Plugins&lt;/th&gt;
&lt;th&gt;When&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;New committer, the account that shipped the backdoor (high)&lt;/td&gt;
&lt;td&gt;31 of 31&lt;/td&gt;
&lt;td&gt;18 on 17 November 2025; the rest between May 2025 and February 2026&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Released again after a long silence (medium), first&lt;/td&gt;
&lt;td&gt;10 of 31&lt;/td&gt;
&lt;td&gt;January to May 2025, around the handover&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Earliest warning&lt;/td&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;11 August 2025, three days after the backdoored release&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Warned before the backdoor switched on&lt;/td&gt;
&lt;td&gt;31 of 31&lt;/td&gt;
&lt;td&gt;41 to 321 days ahead, median 139&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;In the picture at the top of this page, each row is one plugin. The blue dot is the week OwnerTrail would have warned; the dark bar on the right is the day the backdoor switched on. The long grey lines are the months a site owner would have had to look, decide, and act.&lt;/p&gt;

&lt;h2&gt;
  
  
  What OwnerTrail would, and would not, have done
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;The free plugin&lt;/strong&gt; would have raised the finding, dropped the plugin's trust score, put it at the top of the list, and emailed the owner within the hour if email alerts were on. Since 1.2.0 it also offers one click to stop WordPress auto-updating a plugin that changed hands.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;OwnerTrail Pro&lt;/strong&gt; would have held the update of a plugin with that open finding until someone approved that exact version, and listed the new web addresses and risky calls in the release before it installed.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Its code check would not have caught the backdoor itself.&lt;/strong&gt; The bad code was inside the official releases, so it matched WordPress.org's own fingerprints. The code check would have caught what the backdoor did next: the rewrite of &lt;code&gt;wp-config.php&lt;/code&gt;, within a day in the free plugin and within fifteen minutes in Pro.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A new committer is not proof of harm. Most plugin sales are honest, and a new maintainer is often good news. OwnerTrail's job is to make the handover visible, so that a person decides rather than an automatic update.&lt;/p&gt;

&lt;h2&gt;
  
  
  The honest limits
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;This is a replay, not a live catch. Nobody ran OwnerTrail on these sites at the time.&lt;/li&gt;
&lt;li&gt;A warning only helps if someone reads it. That is why OwnerTrail emails within the hour, keeps a finding open until it is acknowledged, and in Pro can hold the update until a person decides.&lt;/li&gt;
&lt;li&gt;It would not have caught the separate &lt;a href="https://ownertrail.decodeinfy.in/articles/wordpress-plugin-supply-chain-attacks-2026/#shapedplugin" rel="noopener noreferrer"&gt;ShapedPlugin compromise&lt;/a&gt;, where the existing owner's build pipeline was turned against them and nothing about who held control changed.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Check your own site
&lt;/h2&gt;

&lt;p&gt;You can read any plugin's history by hand: its directory page lists the author and contributors, and its SVN log names everyone who ever committed. &lt;a href="https://ownertrail.decodeinfy.in/articles/how-to-check-who-owns-a-wordpress-plugin/" rel="noopener noreferrer"&gt;Here is how, step by step&lt;/a&gt;. Doing it every week for every plugin on every site you run is the part nobody manages, which is why the backdoor sat there for eight months.&lt;/p&gt;
&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;        &amp;lt;p&amp;gt;&amp;lt;strong&amp;gt;About OwnerTrail.&amp;lt;/strong&amp;gt; A free WordPress plugin that watches who controls every plugin on your site and whether anyone has changed its code, from public WordPress.org data only, with no telemetry. It is free on &amp;lt;a href="https://wordpress.org/plugins/ownertrail/"&amp;gt;WordPress.org&amp;lt;/a&amp;gt;. &amp;lt;a href="https://ownertrail.decodeinfy.in/#pricing"&amp;gt;See what is free and what Pro adds&amp;lt;/a&amp;gt;.&amp;lt;/p&amp;gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;
&lt;p&gt;Related: &lt;a href="https://ownertrail.decodeinfy.in/articles/wordpress-plugin-supply-chain-attacks-2026/" rel="noopener noreferrer"&gt;the 2026 supply-chain attacks, dated and sourced&lt;/a&gt; and &lt;a href="https://ownertrail.decodeinfy.in/articles/ways-a-wordpress-plugin-can-change-hands/" rel="noopener noreferrer"&gt;every way a plugin can change hands&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>wordpress</category>
      <category>security</category>
      <category>webdev</category>
      <category>php</category>
    </item>
    <item>
      <title>Is This WordPress Plugin Safe? A 5-Minute Check</title>
      <dc:creator>Decodeinfy</dc:creator>
      <pubDate>Mon, 26 Oct 2026 00:00:00 +0000</pubDate>
      <link>https://dev.to/decodeinfy_60e750d3bbfab5/is-this-wordpress-plugin-safe-a-5-minute-check-2lao</link>
      <guid>https://dev.to/decodeinfy_60e750d3bbfab5/is-this-wordpress-plugin-safe-a-5-minute-check-2lao</guid>
      <description>&lt;p&gt;&lt;em&gt;Before installing a plugin or keeping an old one, spend five minutes checking who maintains it, when it was last updated, its SVN commits, and its support threads.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Check the developer profile and ownership history
&lt;/h2&gt;

&lt;p&gt;When evaluating a plugin on WordPress.org, start by looking at who currently owns and maintains the project. Ownership of popular plugins can change hands quietly when original developers sell their work to commercial entities or third-party maintainers.&lt;/p&gt;

&lt;p&gt;To inspect the plugin maintainer on WordPress.org, follow these steps:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Go to the plugin page on WordPress.org.&lt;/li&gt;
&lt;li&gt;Look at the sidebar under the &lt;strong&gt;Author&lt;/strong&gt; field, or directly below the main title.&lt;/li&gt;
&lt;li&gt;Click the maintainer's username to view their WordPress.org public profile.&lt;/li&gt;
&lt;li&gt;Check how long the account has existed and what other plugins or contributions are attached to it.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;A sudden shift in authorship—such as a plugin transferring from a long-time open-source contributor to a newly registered account or an aggressive marketing agency—warrants further examination. If you want to dive deeper into tracking maintainers, see our detailed guide on &lt;a href="https://ownertrail.decodeinfy.in/articles/how-to-check-who-owns-a-wordpress-plugin/" rel="noopener noreferrer"&gt;how to check who owns a WordPress plugin&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Look for warning flags on WordPress.org
&lt;/h2&gt;

&lt;p&gt;WordPress.org displays specific indicators directly on a plugin's main page when potential issues arise or when maintenance stalls. Before downloading any zip file or clicking install, review these key metadata points on the right-hand sidebar:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Last Updated:&lt;/strong&gt; Check when the maintainer last pushed an update. If a plugin has not received an update in over two years, WordPress.org displays a prominent notice warning that it has not been tested with recent major WordPress releases.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Closure Banners:&lt;/strong&gt; If WordPress.org closes a plugin, a red or yellow banner appears at the top of the page stating that the plugin is no longer available for download.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Tested up to:&lt;/strong&gt; Compare the maximum tested WordPress version listed on the page against your current core version.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A closed plugin does not immediately break your site, but it means no future updates or security patches will be published through the official directory. If you discover an installed plugin has been removed, read our overview on &lt;a href="https://ownertrail.decodeinfy.in/articles/wordpress-plugin-closed-what-to-do/" rel="noopener noreferrer"&gt;what to do when a WordPress plugin is closed&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Inspect the public SVN commit history
&lt;/h2&gt;

&lt;p&gt;Every plugin hosted on WordPress.org stores its code in a public Subversion (SVN) repository. You can view every code change, commit message, and committer account directly through your browser without downloading the plugin.&lt;/p&gt;

&lt;p&gt;To review the public commit log:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Navigate to the plugin page on WordPress.org.&lt;/li&gt;
&lt;li&gt;Click the &lt;strong&gt;Development&lt;/strong&gt; tab in the navigation menu below the plugin title.&lt;/li&gt;
&lt;li&gt;Click the link for &lt;strong&gt;Development Log&lt;/strong&gt; or browse the &lt;strong&gt;SVN repository&lt;/strong&gt; directly.&lt;/li&gt;
&lt;li&gt;Review the recent commit entries for unexpected changes, such as new accounts pushing massive code updates after months or years of inactivity.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Pay attention to sudden modifications in obfuscated external API calls, unexpected remote file requests, or structural rewrites pushed by unfamiliar username handles. For step-by-step instructions on reading repository logs, see our guide on &lt;a href="https://ownertrail.decodeinfy.in/articles/reading-a-wordpress-plugin-svn-commit-history/" rel="noopener noreferrer"&gt;reading a WordPress plugin SVN commit history&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Review the support forum and user reports
&lt;/h2&gt;

&lt;p&gt;The official support forum on WordPress.org provides real-time signal regarding whether a plugin functions predictably or introduces unwanted changes. User reports often highlight problems weeks before official notices are posted elsewhere.&lt;/p&gt;

&lt;p&gt;Click on the &lt;strong&gt;Support&lt;/strong&gt; tab on the plugin page and check these key areas:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Resolved Threads:&lt;/strong&gt; Look at the ratio of resolved to unresolved topics over the past two months.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Specific Error Complaints:&lt;/strong&gt; Look for threads reporting unexpected external redirects, unwanted promotional popups, unknown admin accounts, or unexplained performance drops.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Developer Responses:&lt;/strong&gt; Check whether the plugin team responds professionally to bug reports, or if support threads are ignored entirely.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If multiple users report that a recent update altered plugin behavior without documentation, hold off on updating or installing until the maintainers address the issue publicly.&lt;/p&gt;

&lt;h2&gt;
  
  
  Audit installed plugins inside wp-admin
&lt;/h2&gt;

&lt;p&gt;Checking plugins is not just a task for new installations; existing plugins on your site must be checked regularly. Inactive or unmaintained plugins remain on your server's disk and can pose unnecessary risks if neglected.&lt;/p&gt;

&lt;p&gt;Perform a quick monthly check inside your dashboard by doing the following:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Log in to your site and go to &lt;code&gt;Plugins &amp;gt; Installed Plugins&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Filter by &lt;strong&gt;Inactive&lt;/strong&gt; plugins. Deactivate and fully delete any plugin you no longer use. Leaving unused code on your server increases your attack surface.&lt;/li&gt;
&lt;li&gt;Click &lt;strong&gt;View details&lt;/strong&gt; on remaining active plugins to check their current version, author links, and compatibility notes directly from wp-admin.&lt;/li&gt;
&lt;li&gt;Verify that the plugin author link points to the expected domain and developer.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;If a plugin changes author, or its updates have ceased altogether, decide whether to keep the plugin or find an actively maintained alternative.&lt;/p&gt;

&lt;h2&gt;
  
  
  Automate plugin safety checks with OwnerTrail
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://wordpress.org/plugins/ownertrail/" rel="noopener noreferrer"&gt;OwnerTrail&lt;/a&gt; is a free WordPress plugin available on WordPress.org that checks your site and its plugins for you, every day.&lt;/p&gt;

&lt;p&gt;It does the checks above on its own, every day:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;It checks WordPress core, plugin, and theme files against the official releases published on WordPress.org.&lt;/li&gt;
&lt;li&gt;It looks inside files that are not part of any official release, such as PHP in your uploads folder, for the telltale shapes of malware.&lt;/li&gt;
&lt;li&gt;It opens your pages the way Google does, to catch spam that hackers show only to search engines, such as the Japanese keyword hack.&lt;/li&gt;
&lt;li&gt;It notices when a plugin gets a new owner or a new developer, when an abandoned plugin suddenly updates, and when WordPress.org closes a plugin.&lt;/li&gt;
&lt;li&gt;It gives every plugin a trust score from 0 to 100, and can email you when something needs your attention.&lt;/li&gt;
&lt;li&gt;When a plugin changes hands, it holds that plugin's next update until you have looked (free, from version 1.3.6).&lt;/li&gt;
&lt;li&gt;Its Code lock means code on your site can only be changed over FTP, unless you loosen it.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;In a historical replay against 31 backdoored plugins from 2025–2026, OwnerTrail generated warnings on all 31 plugins between 41 and 321 days before the backdoors activated, with a median lead time of 139 days. OwnerTrail detects irregularities and warns the site owner. It is not a firewall: pair it with one, and with backups.&lt;/p&gt;
&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;        &amp;lt;p&amp;gt;&amp;lt;strong&amp;gt;About OwnerTrail.&amp;lt;/strong&amp;gt; A free WordPress plugin that watches who controls every plugin on your site, flags plugins WordPress.org has closed, checks your code against WordPress.org's fingerprints, and fetches your pages as Googlebot to catch spam shown only to search engines. It detects; it is not a firewall. &amp;lt;a href="https://wordpress.org/plugins/ownertrail/"&amp;gt;Free on WordPress.org&amp;lt;/a&amp;gt;.&amp;lt;/p&amp;gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;
&lt;p&gt;Related: &lt;a href="https://ownertrail.decodeinfy.in/articles/how-to-check-who-owns-a-wordpress-plugin/" rel="noopener noreferrer"&gt;How to check who owns a WordPress plugin&lt;/a&gt; and &lt;a href="https://ownertrail.decodeinfy.in/articles/wordpress-plugin-closed-what-to-do/" rel="noopener noreferrer"&gt;A WordPress plugin was closed: what it means and what to do&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>wordpress</category>
      <category>security</category>
      <category>webdev</category>
      <category>php</category>
    </item>
  </channel>
</rss>
