<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>hacked site - Matteo Cisilino</title>
	<atom:link href="https://www.cisilino.com/en/tag/hacked-site/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.cisilino.com/en/</link>
	<description>Guide su WordPress, server e sicurezza</description>
	<lastBuildDate>Wed, 11 Nov 2026 17:51:59 +0000</lastBuildDate>
	<language>en-GB</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.4</generator>
	<item>
		<title>WordPress webshell: how to find it with file integrity checks</title>
		<link>https://www.cisilino.com/en/2026/11/11/wordpress-webshell-file-integrity/</link>
					<comments>https://www.cisilino.com/en/2026/11/11/wordpress-webshell-file-integrity/#respond</comments>
		
		<dc:creator><![CDATA[matteocisilino]]></dc:creator>
		<pubDate>Wed, 11 Nov 2026 17:42:00 +0000</pubDate>
				<category><![CDATA[csdn]]></category>
		<category><![CDATA[file integrity]]></category>
		<category><![CDATA[hacked site]]></category>
		<category><![CDATA[webshell]]></category>
		<category><![CDATA[WordPress malware]]></category>
		<guid isPermaLink="false">https://www.cisilino.com/?p=163</guid>

					<description><![CDATA[<p>How to find a webshell in WordPress: the integrity check compares file hashes with a manifest and reports modified or unexpected files.</p>
<p>The post <a href="https://www.cisilino.com/en/2026/11/11/wordpress-webshell-file-integrity/">WordPress webshell: how to find it with file integrity checks</a> first appeared on <a href="https://www.cisilino.com/en/">Matteo Cisilino</a>.</p>]]></description>
										<content:encoded><![CDATA[<p>A <strong>WordPress webshell</strong> is usually quiet. It is a file with an innocent name, maybe <code>cache-update.php</code>, slipped into a plugin folder. The site works fine and for months someone has a convenient back door into the server.</p>
<figure class="wp-block-image size-large"><img fetchpriority="high" decoding="async" src="https://www.cisilino.com/wp-content/uploads/2026/10/webshell-wordpress-file-integrity-check.webp" alt="WordPress webshell check: a grid of identical circles with one different circle ringed by a blue dashed line" width="1200" height="630"/></figure>
<h2>What the plugin checks to find a WordPress webshell</h2>
<p>Once a day, and on request, the plugin compares the MD5 hashes of its own files with a manifest shipped with the release. If there is no manifest, it uses a snapshot taken at activation. The result reports modified files, missing files and files that should not be in the folder. That last case is the WordPress webshell itself.</p>
<h2>Why a copy outside the site</h2>
<p>Whoever can plant a WordPress webshell by writing to the folder can also tamper with the manifest or switch the check off. That is why the result is also sent to the panel. The copy that lives off the machine is the only one an attacker cannot fix.</p>
<h2>What it is not</h2>
<p>The check <em>detects</em> tampering, it does not prevent it. It only looks at the Cisilino plugin&#8217;s files, not the whole site, so it won&#8217;t catch a WordPress webshell planted elsewhere. Think of it as a doorbell. Don&#8217;t mistake it for an antivirus scan.</p>
<h2>How to read an alert</h2>
<p>An unexpected file, a possible WordPress webshell, deserves immediate attention. Work out when it appeared, isolate the site, change the credentials, find out where it got in. The official guide to <a href="https://developer.wordpress.org/advanced-administration/security/hardening/" target="_blank" rel="noopener">WordPress security hardening</a> is a useful complement to this check. A &#8220;modified&#8221; or &#8220;missing&#8221; file can have a mundane cause, such as an interrupted update or a manual deletion. The check tells you that something is different, not why.</p>
<h2>Frequently asked questions</h2>
<h3>How do you find a WordPress webshell?</h3>
<p>By looking for files that shouldn&#8217;t be there. The plugin compares the hashes of its own files with a manifest and reports the ones that are modified, missing or unexpected.</p>
<h3>Does the check prevent an infection?</h3>
<p>No, it detects it. Whoever can already write files can also rewrite the check, which is why the result is copied to the panel.</p>
<h3>How often does the check run?</h3>
<p>Once a day, and also on request from the settings page.</p>
<h2>Read more</h2>
<ul>
<li><a href="https://www.cisilino.com/en/?p=91">Dangerous file uploads in WordPress: double extensions</a></li>
<li><a href="https://www.cisilino.com/en/?p=93">WordPress hardening with .htaccess: what to switch on</a></li>
<li><a href="https://www.cisilino.com/en/2026/10/29/cisilino-site-defense-network-security-plugin/">Cisilino Site Defense Network: the WordPress security plugin</a></li>
</ul><p>The post <a href="https://www.cisilino.com/en/2026/11/11/wordpress-webshell-file-integrity/">WordPress webshell: how to find it with file integrity checks</a> first appeared on <a href="https://www.cisilino.com/en/">Matteo Cisilino</a>.</p>]]></content:encoded>
					
					<wfw:commentRss>https://www.cisilino.com/en/2026/11/11/wordpress-webshell-file-integrity/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
