<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[tema.name: websites, Joomla and WordPress fixes]]></title><description><![CDATA[tema.name: websites, Joomla and WordPress fixes]]></description><link>https://temaname.hashnode.dev</link><image><url>https://cdn.hashnode.com/uploads/logos/6afa0010b5785800dd339b23/7e4b9c6b-b434-4cc2-a43e-fbbbfa747de9.png</url><title>tema.name: websites, Joomla and WordPress fixes</title><link>https://temaname.hashnode.dev</link></image><generator>RSS for Node</generator><lastBuildDate>Fri, 20 Nov 2026 17:53:07 GMT</lastBuildDate><atom:link href="https://temaname.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[Joomla site hacked? What to do in the first hour (and what not to do)]]></title><description><![CDATA[A calm checklist for a hacked Joomla site: what to save, how to lock access, find the entry point and get Google to trust the site again.]]></description><link>https://temaname.hashnode.dev/joomla-site-hacked-what-to-do-in-the-first-hour-and-what-not-to-do</link><guid isPermaLink="true">https://temaname.hashnode.dev/joomla-site-hacked-what-to-do-in-the-first-hour-and-what-not-to-do</guid><category><![CDATA[joomla]]></category><category><![CDATA[Security]]></category><category><![CDATA[Web Development]]></category><dc:creator><![CDATA[Artem (tema.name)]]></dc:creator><pubDate>Sun, 15 Nov 2026 18:59:42 GMT</pubDate><content:encoded><![CDATA[<p>When a Joomla site gets hacked, the owner usually finds out from someone else: a customer sees spam, Google shows "This site may be hacked", or the host suspends the account. The first hour decides how much work the cleanup will be. Here is the order I follow on client sites.</p>
<h2>1. Do not delete anything yet</h2>
<p>The natural reaction is to delete suspicious files or restore last week's backup. Both can make things worse:</p>
<ul>
<li>deleted files are evidence: they show how the attacker got in</li>
<li>last week's backup may already contain the backdoor, so the site gets reinfected in a day</li>
</ul>
<p>First make a full copy of the infected site: all files and a database dump. Store it outside the server.</p>
<h2>2. Confirm what kind of hack it is</h2>
<p>Typical Joomla infections look different:</p>
<ul>
<li><strong>Redirects</strong> to casino, pharmacy or dating sites, often only for mobile visitors coming from Google</li>
<li><strong>Spam pages</strong> in Japanese or with "cheap" keywords that appear in <code>site:yourdomain.com</code></li>
<li><strong>Defacement</strong>: the home page replaced with a message</li>
<li><strong>Hidden mailer</strong>: the server sends spam, the host blocks outgoing mail</li>
<li><strong>Admin takeover</strong>: new Super Users you did not create</li>
</ul>
<p>Check Google Search Console &gt; Security issues, and open your site from a phone through a Google search result, not by typing the address.</p>
<h2>3. Lock the doors</h2>
<ul>
<li>Change passwords for the hosting panel, FTP or SSH, and the database</li>
<li>In Joomla, check Users &gt; Manage for unknown Super Users and block them</li>
<li>Enable two-factor authentication for all administrators</li>
<li>If the host offers it, restrict <code>/administrator/</code> by IP for now</li>
</ul>
<p>Changing the Joomla admin password alone is not enough: a backdoor file does not need a password.</p>
<h2>4. Find the entry point</h2>
<p>Most Joomla hacks I see come from one of these:</p>
<ol>
<li>An old Joomla version (3.x or an unpatched 4.x)</li>
<li>An outdated extension with a known vulnerability</li>
<li>A nulled (pirated) template or extension</li>
<li>A weak or reused admin password</li>
<li>Another infected site in the same hosting account</li>
</ol>
<p>Look at the access log for POST requests to unusual PHP files, and at files changed around the date the problem started.</p>
<h2>5. Clean, then update</h2>
<p>Replace the Joomla core with a clean copy of the same version, reinstall extensions from their original sources, then review what is left by hand: templates, <code>images/</code>, <code>media/</code>, <code>tmp/</code>, <code>.htaccess</code> and <code>configuration.php</code>. Only after the site is clean, update Joomla and every extension. If the site still runs Joomla 3, the update path to a supported version is part of the fix, not a separate project.</p>
<h2>6. Tell Google the site is clean</h2>
<p>If Search Console shows a security warning, request a review after cleaning. Make spam URLs return 404 or 410, check that the sitemap and <code>robots.txt</code> are your own, and request reindexing of the main pages.</p>
<h2>When to call someone</h2>
<p>If the hack comes back after cleaning, if you cannot find the entry point, or if the site makes money every hour it is down, it is cheaper to hand it over.</p>
<p>I wrote a longer guide on this: <a href="https://tema.name/en/blog/joomla-website-hacked-what-to-do-2026.html">Joomla website hacked: what to do in 2026</a>. And if you want it done for you: <a href="https://tema.name/en/services/joomla-hacked-recovery.html">Joomla hacked site recovery</a>, with a fixed quote before the start.</p>
]]></content:encoded></item></channel></rss>