<?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/"
	
	xmlns:georss="http://www.georss.org/georss"
	xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#"
	>

<channel>
	<title>htaccess &#8211; WordPress Security Blog</title>
	<atom:link href="https://blog.website-malware-removal.com/tag/htaccess/feed" rel="self" type="application/rss+xml" />
	<link>https://blog.website-malware-removal.com</link>
	<description></description>
	<lastBuildDate>Fri, 03 Apr 2026 01:30:49 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
<site xmlns="com-wordpress:feed-additions:1">226935356</site>	<item>
		<title>How to allow WordPress XMLRPC access only from the local network or your domain</title>
		<link>https://blog.website-malware-removal.com/10808</link>
		
		<dc:creator><![CDATA[wpdoctoradmin]]></dc:creator>
		<pubDate>Fri, 03 Apr 2026 01:30:49 +0000</pubDate>
				<category><![CDATA[WordPress Security]]></category>
		<category><![CDATA[htaccess]]></category>
		<guid isPermaLink="false">https://blog.website-malware-removal.com/?p=10808</guid>

					<description><![CDATA[This section explains how to allow WordPress XMLRPC access only from the local network or your own domain. What is XML-RPC? XML-RPC (XML Remote Procedure Call) is a mechanism that allows you to post, edit, delete articles, upload media, and manage comments from outside without logging in to the WordPress administration screen by exchanging XML format data via HTTP. It exists as a file xmlrpc.php in the root directory of WordPress. It has been enabled by default since WordPress 3.5 (2012), but REST API is now the mainstream, and XML-RPC remains for backward compatibility. XMLRPC can be used as a springboard for brute force attacks (password brute force) or DDoS attacks (pinback exploits). Configure .htaccess to restrict access except from the local network or your own domain. Add the following settings to .htaccess in the same hierarchy as xmlrpc.php. &#60;Files xmlrpc.php&#62; Order Deny,Allow Deny from all Allow from 127.0.0.1 Allow from ::1 Allow from 123.123.123.123 &#60;/Files&#62; 127.0.0.1 and ::1 mean localhost. 123.The 123.123.123.123 part should be the IP of your company&#8217;s local network. Harmful Effects of Restrictions Setting IP restrictions may affect some services and applications. Please check in advance. Official WordPress apps (iOS / Android) Official WordPress smartphone apps use XML-RPC to post and edit articles. Restrictions will prevent you from operating from the app. Cooperation with external services Jetpack has features that rely on XML-RPC, and some of them may stop working after the restriction; automatic posting to WordPress using IFTTT or Zapier may also stop. External Blog Editors Editors for posting articles from the desktop, such as MarsEdit (Mac) and Windows Live Writer, use XML-RPC and will not be available. *But if the IP of your PC is fixed, you can use them by setting that IP to HTACCESS as permitted. &#60;Files xmlrpc.php&#62; Order Deny,Allow Deny from all Allow from 127.0.0.1 Allow from ::1 Allow from your ip here &#60;/Files&#62;> Pinback/Trackback You will not receive pingback notifications from other sites. Free] WordPress:Malware Scan &#038; Security Plugin [Malware and Virus Detection and Removal] does not disable XMLRPC completely, but only detects and blocks excessive XMLRPC access and brute force attacks. We hope you will feel free to use this service.]]></description>
		
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">10808</post-id>	</item>
		<item>
		<title>How to exclude WordPress CSP (Content Security Policy) settings from the admin screen</title>
		<link>https://blog.website-malware-removal.com/10696</link>
		
		<dc:creator><![CDATA[wpdoctoradmin]]></dc:creator>
		<pubDate>Tue, 13 Jan 2026 01:24:40 +0000</pubDate>
				<category><![CDATA[WordPress Security]]></category>
		<category><![CDATA[htaccess]]></category>
		<category><![CDATA[javascript]]></category>
		<category><![CDATA[security]]></category>
		<guid isPermaLink="false">https://blog.website-malware-removal.com/?p=10696</guid>

					<description><![CDATA[This section explains how to exclude WordPress CSP settings from the admin screen. How to deal with WordPress admin screen collapsing or malfunctioning with CSP (Content Security Policy). CSP (Content Security Policy) specifies how external scripts such as JAVASCRIPT and CSS on a website are loaded into the browser, preventing unauthorized scripts from being loaded into the browsers of users accessing the site, It is a mechanism to prevent cross-site scripting. However, if CSP is set too strictly, it often results in malfunctions, such as corruption of the WordPress administration screen layout and partial disabling of some functions. However, if the CSP setting is too lax, security will be compromised. For this reason, it is best to separate the WordPress administration screen from the site&#8217;s display area to ensure a high level of security for visitors to the site, and to reduce the possibility of problems with the administration screen. Apply CSP settings only to the display part of the site and exclude the administration screen. 1 When CSP is output with add_action For example, if you are outputting CSP settings with the following code add_action('send_headers', function () { header( "Content-Security-Policy: default-src 'self';" ); }); For the WordPress admin page, you can apply the CSP settings only to the display part of the site by including the IF statement to exclude. ↓Example of modification add_action('send_headers', function () { if (is_admin()) { return;//if wordpress admin screen, do nothing and return. } header( "Content-Security-Policy: default-src 'self';" ); }); 2 If you are outputting CSP with htaccess If you are using htaccess, use SetEnvIf to exclude CSP adaptation in the admin &#60;IfModule mod_setenvif.c&#62; SetEnvIf Request_URI "wp-admin" no_csp &#60;/IfModule &#60;IfModule mod_headers.c&#62; Header set Content-Security-Policy "default-src 'self'" env=!no_csp &#60;/IfModule&#62; The second line makes Apache recognize the environment variable no_csp if the URL contains wp-admin. Then on the last line add env=!no_csp to the CSP configuration so that the CSP configuration is output in the header only if the environment variable is not no_csp. *SetEnvIf seems to work for X server and Sakura, but it may not work for some servers. In this case, it may be better to use the add_action method to set CSP settings to exclude the admin page. However, it seems that the add_action method may not work correctly when used in conjunction with cache plugins. We would appreciate it if you could take this into consideration. CSP settings that exclude the administration screen as described above can be easily specified with the security plugin we have developed. Please use it if you wish. Free WordPress:Malware Scan &#38; Security Plug-in [Malware and Virus Detection and Removal]]]></description>
		
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">10696</post-id>	</item>
		<item>
		<title>How to exclude wp-admin (wordpress admin) in wordpress CSP settings?</title>
		<link>https://blog.website-malware-removal.com/10687</link>
		
		<dc:creator><![CDATA[wpdoctoradmin]]></dc:creator>
		<pubDate>Tue, 06 Jan 2026 01:53:16 +0000</pubDate>
				<category><![CDATA[WordPress Security]]></category>
		<category><![CDATA[htaccess]]></category>
		<category><![CDATA[javascript]]></category>
		<category><![CDATA[security]]></category>
		<guid isPermaLink="false">https://blog.website-malware-removal.com/?p=10687</guid>

					<description><![CDATA[This section explains how to exclude wp-admin from the CSP settings in WordPress. The CSP content security policy setting causes various problems in the wordpress admin. CSP is a setting that allows the browser to load various external javascripts and styles, but the WordPress administration screen makes extensive use of inline scripts and styles. However, the WordPress admin screen is not designed to be used for this purpose. However, if the csp settings are loosened for the WordPress admin screen, it will not make much sense from a security standpoint. Place a .htaccess file in the wp-admin folder and disable CSP settings only when accessing the WordPress administration screen. Since the wordpress admin screen can only be accessed when logged in, it is considered safe to exclude the csp setting. To exclude CSP settings only for the WordPress administration screen, create an .htaccess file in the wp-admin folder and include the following line. Header not set Content-Security-Policy This statement will mean that only the wp-admin folder will be excluded from the CSP settings by unsetting it. We hope this helps. Free] WordPress: Malware Scan &#038; Security Plugin [Malware and Virus Detection and Removal]]></description>
		
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">10687</post-id>	</item>
		<item>
		<title>If default-src and script-src in the CSP Content Security Policy are set at the same time, which has priority?</title>
		<link>https://blog.website-malware-removal.com/10676</link>
		
		<dc:creator><![CDATA[wpdoctoradmin]]></dc:creator>
		<pubDate>Wed, 17 Dec 2025 01:25:24 +0000</pubDate>
				<category><![CDATA[WordPress Security]]></category>
		<category><![CDATA[htaccess]]></category>
		<category><![CDATA[javascript]]></category>
		<category><![CDATA[security]]></category>
		<guid isPermaLink="false">https://blog.website-malware-removal.com/?p=10676</guid>

					<description><![CDATA[If default-src and script-src in the CSP Content Security Policy are set at the same time, this section explains which has priority. What is the CSP Content Security Policy? CSP Content Security Policy (CSP Content Security Policy) is a policy that specifies which types of sources (scripts, images, stylesheets, etc.) are allowed to be loaded and from where, to prevent XSS (Cross Site Scripting: an attack in which external scripts are executed on a site) and, to some extent, to prevent users accessing the site from executing such malicious scripts even if malicious code is embedded due to site tampering. It can be implemented by writing settings in the HTACCESS file. This can be implemented by writing the settings in the HTACCESS file. CSP has been implemented in many corporate sites in recent years, and some vendors require that it be properly configured for internal auditing purposes. What happens if default-src and script-src are set at the same time? CSP specifies the source of the source to be loaded for each item, such as default-src (batch specification) and script-src (specification of JAVASCRIPT loading) in HTACCESS, as shown below. The following is an example of a very strict setting that allows scripts to be loaded only within the domain of your site. Header set Content-Security-Policy "default-src 'self'; script-src 'self';" What happens if default-src (specified in bulk) and other settings such as script-src are out of sync? The following settings are: default-src (batch specification) for self (only own domain is allowed), script-src is https://cdn.example.com, https://api.example.comの2ドメインからのスクリプトの読み込みが許可されるという意味に The following settings are used. Header set Content-Security-Policy "default-src 'self'; script-src https://cdn.example.com https://api.example.com;" A common mistake is that the script-src setting is combined with default-src. In other words, it is often mistakenly assumed that the sources that can be loaded by script-src are &#8216;self&#8217; (own domain) and https://cdn.example.comかつhttps://api.example.com;. In fact, however, they are not combined, and &#8220;default-src &#8216;self'&#8221; is overridden and ignored by the script-src setting. This means that the only sources that can be read by script-src are the two domains https://cdn.example.com https://api.example.com;. If you want to allow your own domain in script-src, you need to specify self again as shown below. Header set Content-Security-Policy "default-src 'self'; script-src 'self' https://cdn.example.com https://api.example.com;" The default-src will be overwritten (replaced) by other settings, but it is easier to understand if you think of it as a kind of insurance policy that allows you to specify all items that are not set at once. We hope this helps. Free WordPress:Malware Scan &#038; Security Plugin [Malware and Virus Detection and Removal].]]></description>
		
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">10676</post-id>	</item>
		<item>
		<title>SSL and CSP do not prevent hacking</title>
		<link>https://blog.website-malware-removal.com/10654</link>
		
		<dc:creator><![CDATA[wpdoctoradmin]]></dc:creator>
		<pubDate>Thu, 04 Dec 2025 01:48:12 +0000</pubDate>
				<category><![CDATA[WordPress Security]]></category>
		<category><![CDATA[free]]></category>
		<category><![CDATA[hacked]]></category>
		<category><![CDATA[htaccess]]></category>
		<category><![CDATA[malware]]></category>
		<category><![CDATA[removal]]></category>
		<category><![CDATA[scan]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[virus]]></category>
		<guid isPermaLink="false">https://blog.website-malware-removal.com/?p=10654</guid>

					<description><![CDATA[Converting WordPress to SSL and setting up a CSP (Content Security Policy) does not prevent hacking. We will explain the reasons for this. Why SSL (HTTPS) does not prevent hacking SSL encrypts notifications between the web server and the user&#8217;s browser so that servers, WIFI, and other devices that mediate data transmission can read the contents of those communications and not know what data is being sent or received. Incidentally, the following information is not protected even if SSL is used (1) IP address of the destination (2) Domain name (SNI) * The URL of the page being accessed and queries under the domain will be kept confidential. (iii) Timing and traffic volume of the connection Therefore, it is possible to prevent WordPress login IDs and passwords from being read and exposed in the process of SSL conversion. Why can&#8217;t SSL prevent hacking? However, most WordPress hacking is done through brute force attacks, in which the administrator&#8217;s password is determined by brute force, or by hackers gaining direct access to vulnerabilities in plug-ins and other vulnerabilities. Such attacks cannot be prevented by encrypting communications using SSL, because the hacker&#8217;s unauthorized communications themselves are not filtered out. Why CSP settings do not prevent hacking Recently, it has become common to set CSP (Content Security Policy). CSP (Content Security Policy) is a mechanism for specifying which JS scripts, images, CSS, etc. from which sources are allowed to be loaded in HTACCESS files and other files. Browsers will read these settings and prevent loading of JS, etc. on unauthorized domains. The CSP setting may prevent users from suffering secondary damage by preventing the browser from loading malicious JS scripts embedded by hackers on the site. However, what CSP can prevent is the loading of malicious scripts, etc., into the content after the hacker has already successfully defaced the site, and the user&#8217;s browser will execute them. (This may not be prevented if the CSP settings and the malicious embedded scripts are on the same server.) CSP is an insurance policy that may prevent users from accessing the site and suffering secondary damage in the event that the site is hacked. How do I prevent WordPress from being hacked? To prevent WordPress from being hacked, it is important to take basic security measures, such as using plug-ins that specialize in preventing hacking, in addition to SSL and CSP settings. Security Plug-ins Free WordPress:Malware Scan &#038; Security Plug-in [Malware and Virus Detection and Removal]. Basic Security Measures What are some meaningful and not-so-meaningful security measures in WordPress? We hope you find this information helpful.]]></description>
		
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">10654</post-id>	</item>
		<item>
		<title>Automate WordPress security-related maintenance with plugins.</title>
		<link>https://blog.website-malware-removal.com/10583</link>
		
		<dc:creator><![CDATA[wpdoctoradmin]]></dc:creator>
		<pubDate>Tue, 16 Sep 2025 01:59:44 +0000</pubDate>
				<category><![CDATA[WordPress Security]]></category>
		<category><![CDATA[check]]></category>
		<category><![CDATA[database]]></category>
		<category><![CDATA[free]]></category>
		<category><![CDATA[hacked]]></category>
		<category><![CDATA[htaccess]]></category>
		<category><![CDATA[index.php]]></category>
		<category><![CDATA[malware]]></category>
		<category><![CDATA[plugin]]></category>
		<category><![CDATA[protection]]></category>
		<category><![CDATA[removal]]></category>
		<category><![CDATA[scan]]></category>
		<category><![CDATA[scanner]]></category>
		<category><![CDATA[security]]></category>
		<guid isPermaLink="false">https://blog.website-malware-removal.com/?p=10583</guid>

					<description><![CDATA[The paid version of our WP Doctor Malware Scanner Pro introduces features and settings that are particularly useful for security-related maintenance of WordPress sites. Security measures with WordPress plug-ins1 Automatic malware scanning, email notification when malware is detected The paid version of WP Doctor Malware Scanner Pro automatically updates the latest malware detection patterns collected and added from malware removal requests, our dummy sites, and online malware information. files at any given time, and notifies you by email if any malware is found. This means that if you are infected with malware, you will be able to deal with it at an early stage. WordPress Plug-in for Security Measures 2 Automatic Vulnerability Check and Email Notification of Vulnerabilities 60-70% of the time WordPress is hacked, it is because of vulnerabilities in older plugins. For this reason, it is an extremely powerful security measure to constantly monitor for dangerous vulnerabilities that could allow a site to be tampered with, and if a vulnerability is found, to close it by updating the site or by other means. WP Doctor Malware Scanner Pro automatically checks your site for vulnerabilities from our constantly updated vulnerability database, and notifies you by e-mail if a vulnerability is found. WordPress Plugin for Security Measures 3 Detects hacking attempts being made on your site and automatically blocks hacker IPs. WordPress is the world&#8217;s most popular CMS, and it is said that 20-30% of all websites in the world are created with WordPress. For this reason, hackers attack a vast number of WordPress sites with automated hacking tools at random. Most of them will not succeed, but even the rare ones will be able to be penetrated and tampered with if they can find a large number of sites with dangerous vulnerabilities left unaddressed. Monitoring and detecting such hacking attempts, and automatically blocking the IPs that are attempting to do so, stops the hacker&#8217;s vulnerability attack in its early stages, and alerts the hacker that you are monitoring the hacking activity on the site, which greatly improves site security. Other free WAF features The free version of WP Doctor Malware Scanner Pro also includes one of the most versatile WAFs (Web Application Firewalls) available to increase the security of your site. Examples of security functions available for free Login Lockdown Login capture Prevent WordPress version leakage Block access to wlwmanifest.xml Prohibit Index listings Prohibit WPSCAN Ban brute force attack IP to XMLRPC,wp-login Ban on REST API Ban direct access to Include files Ban PHP access to Upload folder Comment protection, protection from spam Ban on posting comments via proxy Comment form capture Repair and protection of htaccess and index.php Process monitoring functionality etc. For more information, please click here. How to purchase the paid version of WP Doctor Malware Scanner Pro The paid version of WP Doctor Malware Scanner Pro can be purchased from the purchase tab of the plugin&#8217;s administration page after the plugin has been installed on your site. You can pay by credit card via Stripe.]]></description>
		
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">10583</post-id>	</item>
		<item>
		<title>Japanese SEO Spam, a malware that fills Google search results for WordPress sites with Japanese product pages that you don&#8217;t remember creating.</title>
		<link>https://blog.website-malware-removal.com/10574</link>
		
		<dc:creator><![CDATA[wpdoctoradmin]]></dc:creator>
		<pubDate>Thu, 11 Sep 2025 01:39:22 +0000</pubDate>
				<category><![CDATA[WordPress Security]]></category>
		<category><![CDATA[backdoor]]></category>
		<category><![CDATA[check]]></category>
		<category><![CDATA[free]]></category>
		<category><![CDATA[hacked]]></category>
		<category><![CDATA[htaccess]]></category>
		<category><![CDATA[index.php]]></category>
		<category><![CDATA[malware]]></category>
		<category><![CDATA[plugin]]></category>
		<category><![CDATA[removal]]></category>
		<category><![CDATA[scan]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[virus]]></category>
		<guid isPermaLink="false">https://blog.website-malware-removal.com/?p=10574</guid>

					<description><![CDATA[We will explain about Japanese SEO Spam, a malware that fills the Google search results of WordPress sites with pages of Japanese products that you do not remember creating. How does malware contaminate Google search results? There are three types of malware that contaminate Google search results with branded product pages that have not been created. (1) The link in the contaminated search results is not from your site&#8217;s domain → (2) The link in the search results is not from your company&#8217;s site, but from another site that has been hacked and altered to create a malicious page. Therefore, it is necessary for the operator of the other domain site that has been tampered with to deal with the problem. (2) The search result links to your site&#8217;s domain in the tainted search result, but the link destination does not exist. → In this case, this is SEO spam that takes advantage of the property of WordPress to create search result pages that do not exist. Not because your site has been tampered with, but because the hacker has taken the liberty of registering a nonexistent search results page with the search engine. It is effective to introduce a mechanism (e.g., outputting a noindex header) to prevent non-existent search result pages from being registered with search engines. (2) The domain of your site is the link destination in the tainted search results, and the linked page leads to an illegal product site. *When you access the illegal page, you will first fly to the site&#8217;s domain and instantly see [string].bookslit[.] sa[.]. com, etc., and you may jump to an unauthorized site. → In this case, it is highly likely that hackers have exploited a vulnerability and entered your site&#8217;s server, and the site&#8217;s data and files have been tampered with. We recommend that you first run a malware and vulnerability check on your plug-ins. Free WordPress:Malware Scan &#038; Security Plugin [Malware and Virus Detection and Removal]. If you are unable to log in to the WordPress administration screen, it is possible that hackers have also tampered with the HTACCESS file, which controls server settings. How are contaminated search results registered in the search results? The way a hacker has tampered with your site and registered a malicious page may be by creating that malicious page on your company&#8217;s server, or by tampering with your sitemap and registering the page in Google search results. A sitemap is data that tells search engines which pages are on a site that can be accessed by the following URLs. https://Your site URL/sitemap.xml As an example, a site that has been hacked shows that the sitemap has been falsified and illegal pages have been registered as shown below. In some malware, this page does not actually exist on the server, and when this URL is accessed, a malicious program forcibly redirects the user to another arbitrary site. How to deal with malware Japanese SEO Spam If there are symptoms of such malware, there may be a backdoor somewhere on the server that generates a sitemap, controls [&#8230;]]]></description>
		
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">10574</post-id>	</item>
		<item>
		<title>base64_decode,base64_encode commonly found in WordPress malware</title>
		<link>https://blog.website-malware-removal.com/10569</link>
		
		<dc:creator><![CDATA[wpdoctoradmin]]></dc:creator>
		<pubDate>Mon, 08 Sep 2025 01:32:02 +0000</pubDate>
				<category><![CDATA[WordPress Security]]></category>
		<category><![CDATA[database]]></category>
		<category><![CDATA[free]]></category>
		<category><![CDATA[htaccess]]></category>
		<category><![CDATA[javascript]]></category>
		<category><![CDATA[malware]]></category>
		<category><![CDATA[plugin]]></category>
		<category><![CDATA[removal]]></category>
		<category><![CDATA[scan]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[virus]]></category>
		<guid isPermaLink="false">https://blog.website-malware-removal.com/?p=10569</guid>

					<description><![CDATA[We will explain about base64_decode and base64_encode, which are commonly found in WordPress malware, why this function often appears and how to recover this function. Why are base64_decode and base64_encode often included in WordPress malware? base64_encode is a method of mapping data such as strings to 64 different characters separated by a specific length. This makes it easier to handle various data as strings and record them in databases, and is used to prevent garbled or corrupted data. base64_decode is a function to decode it back. Data that would be misspelled if separated by a specific length is filled with == in base64_encode. Also, base64_decode and base64_encode are functions of PHP (the programming language in which WordPress is made), but in JAVASCRIPT (a scripting language that runs in a browser), the function names are btoa and atob, which are also often used for malicious code. It is also often used in malicious code. This encoded base64 string has the characteristic of making the original content difficult to recognize at first glance. For this reason, they are often used to obfuscate malware in order to prevent the code from being recognized as doing what it is supposed to do, or to avoid malware detection (pattern matching). Undo base64_encoded strings To undo base64_encode and see the contents, online services such as https://www.base64decode.org/ are useful. The following figure shows an image of a decoded string of malware base64_decoded. You can see that this string contains a setting that alters the WordPress HTACCESS file, making it impossible to log in. In the above example, the obfuscation could be removed with a single step of base64_decode, but some malware may use multiple base64_encodes, gzinflate (data compression), str_rot13 (string shifting), etc. in combination with the obfuscation process. (data compression) and str_rot13 (string shifting). Example str_rot13(base64_rncode(base64_encode(gzinflate(string to be hidden)))) Detect and remove base64-based obfuscated malware base64 obfuscation patterns can be detected with a high degree of accuracy using our [Free] WordPress: Malware Scanning &#038; Security Plug-in [Malware and Virus Detection and Removal]. Unlike PC viruses, WordPress malware has a huge number of patterns with extremely diverse obfuscation processes, and the WPDoctor WordPress: Malware Scanning &#038; Security Plug-in is designed to match this characteristic, with short and large number of detection patterns to scan thousands of files quickly. This plugin has been designed to be able to scan thousands of files at high speed with a short and large number of detection patterns. We hope you will find it useful.]]></description>
		
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">10569</post-id>	</item>
		<item>
		<title>Malware restored on the server simply by accessing the WordPress site</title>
		<link>https://blog.website-malware-removal.com/10564</link>
		
		<dc:creator><![CDATA[wpdoctoradmin]]></dc:creator>
		<pubDate>Wed, 03 Sep 2025 01:26:31 +0000</pubDate>
				<category><![CDATA[WordPress Security]]></category>
		<category><![CDATA[hacked]]></category>
		<category><![CDATA[htaccess]]></category>
		<category><![CDATA[index.php]]></category>
		<category><![CDATA[malware]]></category>
		<category><![CDATA[removal]]></category>
		<category><![CDATA[scan]]></category>
		<guid isPermaLink="false">https://blog.website-malware-removal.com/?p=10564</guid>

					<description><![CDATA[We will explain the method of malware restoration on the server simply by accessing the WordPress site. Why malware that has been removed on the server is automatically restored just by accessing the site This type of malware is very common, and in many cases, the malware is parasitic and reinfects the program files that are executed whenever WordPress renders a site page on the system. As an example, the files that WordPress always executes are the following files. (Other files deep within the system may also be infected) index.php wp-config.php wp-blog-header.php theme-functions.php The figure below is a screenshot of an example of malware infecting index.php. In order for WordPress to display the site, it reads require __DIR__ . &#8216;/wp-blog-header.php&#8217;; which WordPress loads to display the site, there is obfuscated malicious code that is executed each time the site is accessed. I have tried to de-obfuscate this code in order to analyze it. After repeating base64 decoding and de-obfuscation several times, the original bare code appeared. We can see that the malware notifies a social networking site called Telegram that it is infected. It is likely that automated hacking tools are used to hack into a vast number of WordPress sites, and only successful sites are notified to Telegram, after which the hackers continue their attack. Thus, malware very often contains Telegram.org links or URLs. The following code shows a text file pulled from several URLs and executed with an eval function. The eval function is a PHP function that interprets text as a program and executes it Most likely the above site is another site that has been hacked by hackers. The malware body is placed on this site, and every time index.php is executed, the malware is pulled from other infected sites and reinfected. Since this malware pulls and executes the malware body on an external server, its function can be changed at any time by hackers. How to get rid of malware that reinfects itself automatically To get rid of this type of malware, index.php wp-config.php wp-blog-header.php theme-functions.php However, since other malware may be installed deep within WordPress, it is often not possible to remove the malware by simply removing the above files. For this reason, you can detect and remove more malware by using a malware scanning and removal plug-in that mechanically and comprehensively scans WordPress files. (If you are unable to log in to your WordPress site, the HTACCESSS file may have been tampered with.)]]></description>
		
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">10564</post-id>	</item>
		<item>
		<title>Removing WordPress malware with AI is currently difficult and may break the site</title>
		<link>https://blog.website-malware-removal.com/10558</link>
		
		<dc:creator><![CDATA[wpdoctoradmin]]></dc:creator>
		<pubDate>Tue, 26 Aug 2025 02:15:03 +0000</pubDate>
				<category><![CDATA[WordPress Security]]></category>
		<category><![CDATA[error]]></category>
		<category><![CDATA[htaccess]]></category>
		<category><![CDATA[index.php]]></category>
		<category><![CDATA[malware]]></category>
		<category><![CDATA[plugin]]></category>
		<category><![CDATA[removal]]></category>
		<guid isPermaLink="false">https://blog.website-malware-removal.com/?p=10558</guid>

					<description><![CDATA[We will explain the dangers of malware removal by AI. I tried to get rid of malware while listening to AI&#8217;s opinion, but the site became unviewable. I have tried deleting unknown files (that I was told were strange) regarding the wordpress malware, and getting in and out of themes and plugins, but nothing has changed. I have consulted with chatgpt and cherry servers and tried everything, but nothing is restored. I would like to be able to view the site, please. You consulted with AI such as chatgpt and others and asked them various things to get rid of malware, but now you can&#8217;t see the site. AI has various limitations in its capability and mechanism, and it is difficult to get rid of malware by AI, and it may destroy the site or server. We will explain the reasons for this. AI&#8217;s advice will be the most general, but it will not necessarily take into account the situation of the site. The advice given by ChatGPT to remove malware, while correct in some cases, includes advice that may cause the site to display poorly, for example, the advice to rename the plugin folder given by CHatGPT may cause more errors if the theme is using plugin functionality, etc., and will ensure that the site will not display poorly if you evacuate the theme. For example, the advice given by CHatGPT to rename the plugin folder may cause more errors if the theme uses plugin functionality, etc., and moving the theme back will certainly cause the site to malfunction. The initialization of the HTACCESS advice by ChatGPT may be the correct response, since malware may have tampered with it and made it impossible to log in, but the script for the tampering is embedded in index.php and memory, so even if it is repaired, it may soon be re-infected and you will still not be able to log in. It is highly likely that the infection will not change the situation where you will still not be able to log in again. AI cannot connect to the server and inspect the files exhaustively. Since AI does not have the ability to directly connect to the server, it cannot directly examine or repair the location of the WordPress malware, so it can only advise you on how to do so. However, this advice may also be based on commands to be executed on the server or programs that may or may not work properly. Examples of commands presented by AI These commands do not work on many shared servers, and there is no guarantee that the commands will work as intended, which may cause more errors on the server in some cases, which may be detrimental. grep -R --line-number -E "(base64_decode&#124;gzinflate&#124;str_rot13&#124;eval\(&#124;assert\(&#124;system\(&#124;shell_exec(&#124;passthru\(&#124;exec()" . For these reasons, if you are going to take AI&#8217;s advice on WordPress malware removal, you should carefully examine the content of the advice, taking into account the possibility that the content may cause unnecessary damage to your site. However, even careful examination of the content often requires specialized knowledge. [&#8230;]]]></description>
		
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">10558</post-id>	</item>
		<item>
		<title>How to deal with a 500 Internal Server Error on the post edit screen of the admin screen or the add plugin screen due to htaccess being edited without permission in WordPress.</title>
		<link>https://blog.website-malware-removal.com/10505</link>
		
		<dc:creator><![CDATA[wpdoctoradmin]]></dc:creator>
		<pubDate>Tue, 20 May 2025 02:15:18 +0000</pubDate>
				<category><![CDATA[WordPress Security]]></category>
		<category><![CDATA[error]]></category>
		<category><![CDATA[htaccess]]></category>
		<category><![CDATA[index.php]]></category>
		<guid isPermaLink="false">https://blog.website-malware-removal.com/?p=10505</guid>

					<description><![CDATA[This section describes how to deal with a 500 Internal Server Error on the &#8220;Edit Post&#8221; screen or &#8220;Add Plugin&#8221; screen of the administration screen due to htaccess being edited without permission in WordPress. Tampering with htaccess If you are unable to log in to the WordPress admin screen, or if the post edit screen or add plugin screen gives you a 500Internal Server Error (or blank, or even a 403 error), HTACCESS has been tampered with and access to files with the .php extension Access to files with a .php extension may be blocked. Example of a tampered HTACCESS &#60;FilesMatch ".*\.(py&#124;exe&#124;phtml&#124;php&#124;PHP&#124;Php&#124;PHp&#124;pHp&#124;pHP&#124;phP&#124;PhP&#124;php5&#124;PHP5&#124;Php5&#124;PHp5&#124;pHp5&#124;pHP5&#124;phP5&#124;PhP5&#124;php7&#124;PHP7&#124;Php7&#124;PHp7&#124;pHp7&#124;pHP7&#124;phP7&#124;PhP7&#124;php8&#124;PHP8&#124;Php8&#124;PHp8&#124;pHp8&#124;pHP8&#124;phP8&#124;PhP8&#124;suspected)$"&#62; Order Allow,Deny Deny from all &#60;/FilesMatch&#62; This description of the configuration due to tampering prohibits access to files with any PHP-related extensions. If the HTACCESS file in the top directory of WordPress has the above description, it is highly likely that the site has been hacked and tampered with. How to deal with HTACCESS tampering The above description of blocking access to the PHP extension has been added by hackers to prevent WordPress operators from removing malware using malware scanning plug-ins, etc., so there is no problem if you delete it. Access the WordPress server with FTP software, download the HTACCESS file in the top directory, remove the tampering, and upload it back to the original server. Once you are able to access the administration screen, install the malware scanning disinfection plugin and perform other malware scanning disinfection. If the tampering reverts immediately or cannot be uploaded If HTACCESS tampering reverts back to its original state immediately, or if the file cannot be overwritten by uploading even after rewriting file permissions, there may be malware resident in the server process (memory) to re-tamper with the file. In this case, you will need to stop the process with a special program. Reference Repair HTACCESS and Index.php, which are instantly tampered with again in WordPress. However, if you have been infected with memory-resident malware, there is often a combination of malware disinfection measures on the part of various hackers. Malware that automatically executes the program itself residing in memory is infecting index.php. There is another tampered HTACCESS in the upper hierarchy. The write permission of the folder on the upper hierarchy is also being made continuously un-writable by other processes. Resident in a process of another domain on the same server. etc. In these cases, the aforementioned programs may not be able to compete. We recommend that you contact a WordPress malware removal specialist.]]></description>
		
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">10505</post-id>	</item>
		<item>
		<title>How can I prevent AI such as ChatGPT and Grok from learning and searching for content on my WordPress site and using it for output?</title>
		<link>https://blog.website-malware-removal.com/10487</link>
		
		<dc:creator><![CDATA[wpdoctoradmin]]></dc:creator>
		<pubDate>Thu, 24 Apr 2025 07:26:16 +0000</pubDate>
				<category><![CDATA[WordPress Security]]></category>
		<category><![CDATA[htaccess]]></category>
		<guid isPermaLink="false">https://blog.website-malware-removal.com/?p=10487</guid>

					<description><![CDATA[We will explain how to prevent AI such as ChatGPT and Grok from learning and searching for output on your WordPress site content without your permission. Learning of content by AI and output of results by real-time search Generative AI is currently booming. However, the generative AI such as ChatGPT and Grok do not indicate the link (learning source) that directs traffic to the site, and functions such as DeepResearch indicate the reference source in a way that users are not likely to press the link in a very obvious way*, This situation is becoming less beneficial for content creators. This situation is based on the specifications of the generated AI as of April 2025, and the specifications may change in the future. Prohibit learning by ChatGPT and Grok AI and referencing of content in real-time search in robots.txt To stop such learning and use of content by generated AI in robots.txt, put the following in robots.txt in the top directory on the server. (Download and add the robots.txt file using FTP software) User-agent: GPTBot User-agent: ChatGPT-User User-agent: Grok Disallow: / If you want to disallow a specific directory, use the following User-agent: GPTBot User-agent: ChatGPT-User User-agent: Grok Disallow: /knowledge/ After testing with the above, real-time references to learning and content were stopped. However, this method may cause the generated AI to slip through the robots.txt instructions for a one-time access only. Please refer to &#8220;Block Even Stronger&#8221; for how to deal with this case. What if there is no robots.txt on the server? WordPress will automatically generate a robots.txt file when the robots.txt address is accessed if there is no robots.txt file on the server. https://wordpress site domain/robots.txt Copy and paste this text into a text editor to create a robots.txt file, add the above settings to the file, and upload it to the server. More powerful blocking To block access to generated AI even more strongly, you can use HTACCESS to block access to generated AI itself. To block access to the site with HTACCESS using ChatGPT or Grok user agent, put the following in HTACCESS. &#60;IfModule mod_rewrite.c&#62; RewriteEngine On RewriteBase / RewriteCond %{HTTP_USER_AGENT} ^.*(GPTBot&#124;ChatGPT-User).*$ [NC,OR] RewriteCond %{HTTP_USER_AGENT} ^.*(Grok&#124;python-requests).*$ [NC] RewriteRule ^ - [F,L] &#60;/IfModule&#62; Reference site *It describes how to block not only ChatGPT and Grok, but also all kinds of generated AI. https://perishablepress.com/ultimate-ai-block-list/#block-ai-via-apache (It may be premature to block as completely as the above article) Embed Terms of Service for Generated AI in your pages You can also prevent access to content by automatically outputting the Terms of Use for Generated AI at the bottom of the content on all pages with the following code. add_filter( 'the_content', 'filter_the_content_term_for_generatedai', 1 ); function filter_the_content_term_for_generatedai( $content ) { if ( is_singular() ) { return $content . "&#60;div style='padding:10px;border:solid 1px #ccc;box;box-sizing:border-box;font-size:12px;'&#62;&#60;strong&#62;Terms of Use for Generated AI&#60;/strong&#62;&#60;br&#62; This page prohibits the use, quotation, or summarization of any page, in whole or in part, by the Generated AI. However, if the following conditions are met, the specification of content using generated AI is permitted.&#60;br&#62;1. it is not for the purpose of learning by the [&#8230;]]]></description>
		
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">10487</post-id>	</item>
		<item>
		<title>Examples of WordPress malware damage wp-blog-header.php, wp-cron.php, and .htaccess files are generated by themselves in their own folders</title>
		<link>https://blog.website-malware-removal.com/10477</link>
		
		<dc:creator><![CDATA[wpdoctoradmin]]></dc:creator>
		<pubDate>Thu, 17 Apr 2025 01:27:28 +0000</pubDate>
				<category><![CDATA[WordPress Security]]></category>
		<category><![CDATA[htaccess]]></category>
		<category><![CDATA[index.php]]></category>
		<guid isPermaLink="false">https://blog.website-malware-removal.com/?p=10477</guid>

					<description><![CDATA[Here is an example of WordPress malware damage where wp-blog-header.php, wp-cron.php, and .htaccess files are generated in people&#8217;s folders without their permission. Numerous wp-blog-header.php, wp-cron.php, and .htaccess files are generated without permission outside the public_html and /var/www folders on the WordPress site&#8217;s server. If this occurs, it is very likely that the site has been infiltrated by hackers and malware or backdoors have been installed. The reason why wp-blog-header.php and .htaccess files are generated in other people&#8217;s folders is that low-quality malware programs automatically spread the infection to all WordPress files on the server and randomly replicate themselves in folders without WordPress files. The reason for this is that the low quality malware program automatically spreads to all WordPress folders on the server. Why wp-blog-header.php is automatically generated wp-blog-header.php is a file that is executed each time a WordPress page is displayed. This makes it a convenient file for hackers to embed malicious code for automatic malware restoration or redirect hacks that redirect site users to other sites without their permission. For this reason, hackers write the malware-infected wp-blog-header.php into various folders. When the malicious code embedding is removed, the infection is overwritten via another malware file and automatically replaced with the malicious file, thereby reviving the infection. *Not only wp-blog-header.php, but also index.php and wp-settings.php are similar files, so these files may be written without permission. Why .htaccess is automatically generated The most common reason why .htaccess is automatically tampered with is often to write settings that prevent administrators from accessing the WordPress administration screen. Other reasons why malware files are automatically written to the folder Other times, malware or hackers write fake files that look like WordPress file names such as wp-cron.php, wp-cofiq.php or wp-crom.php into your folders. The reason for this is often to install a backdoor, a file that provides an entry point into the server for hackers to continue hacking, or to install a program to send spam emails. Files often installed as backdoors Tiny File Manager Files often installed as spam mailers: GFX Xsender, leaf mailer How to deal with malware files installed outside of the WordPress web publishing area PHP files and htaccess files located outside of the WordPress public domain are basically not executable, so deleting them is the best way to deal with them. However, if your server has its own system that reads and uses files outside the public domain, you may need to delete them carefully. Other malware investigation and removal In addition, once tampering has been found in the server, there may still be malware or backdoors remaining in the deeper layers of WordPress. We recommend that you use a plugin or other tool that can comprehensively inspect and exterminate malware in the server. Free WordPress:Malware Scan &#038; Security Plug-in [Malware and Virus Detection and Removal]. Plug vulnerabilities Next, the vulnerability of the site that allowed the hacker to enter in the first place must also be plugged, or the same vulnerability can be used to re-infect the site. Reference 5 Free WordPress Security Measures]]></description>
		
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">10477</post-id>	</item>
		<item>
		<title>How to identify suspicious files in the top directory of WordPress</title>
		<link>https://blog.website-malware-removal.com/10432</link>
		
		<dc:creator><![CDATA[wpdoctoradmin]]></dc:creator>
		<pubDate>Fri, 14 Mar 2025 01:27:37 +0000</pubDate>
				<category><![CDATA[WordPress Security]]></category>
		<category><![CDATA[free]]></category>
		<category><![CDATA[htaccess]]></category>
		<category><![CDATA[index.php]]></category>
		<category><![CDATA[malware]]></category>
		<category><![CDATA[plugin]]></category>
		<category><![CDATA[removal]]></category>
		<category><![CDATA[scan]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[virus]]></category>
		<guid isPermaLink="false">https://blog.website-malware-removal.com/?p=10432</guid>

					<description><![CDATA[This section explains how to identify suspicious files (malware files) in the top directory of WordPress. File comparison of top directory structure of malware-infected and non-infected sites The figure below shows the file structure of the top directory of WordPress on the non-malware-infected site. The googlee***.html file is the authentication file for Google&#8217;s access analysis, and .user.ini is the server configuration file. The figure below shows the file structure of infected with malware. You can see that the files circled in red are files that do not originally exist in WordPress and have been given lax file names. If you open one of these files in a text editor, you will see that it has been obfuscated as shown below and is a typical malware file containing elliptic functions. Are there any incorrect files in the top directory of WordPress that should have been placed there? The standard files included in the WordPress top directory are as follows wp-admin (folder) wp-content (folder) wp-includes (folder) .htaccess is the server configuration file created when WordPress generates permalinks. index.php license.txt readme.html wp-activate.php wp-blog-header.php comment-submit.php wp-config.php wp-config-sample.php wp-cron.php wp-links-opml.php wp-load.php wp-login.php wp-mail.php wp-settings.php wp-signup.php wp-trackback.php xmlrpc.php Other than this, can I suspect that the files are malware if they are authentication files for Google&#8217;s access analysis, .user.ini, and the name of the file is a meaningless string of characters? If the file is opened in a text file editor and obfuscated, we are more suspicious of malware infection. In this case, we recommend that you run a malware scan once against all sites on the server. Free] WordPress: Malware Scan &#038; Security Plugin [Malware and Virus Detection and Removal]]></description>
		
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">10432</post-id>	</item>
		<item>
		<title>How to stop detecting malware resident in the process in WordPress</title>
		<link>https://blog.website-malware-removal.com/10418</link>
		
		<dc:creator><![CDATA[wpdoctoradmin]]></dc:creator>
		<pubDate>Thu, 06 Mar 2025 01:36:24 +0000</pubDate>
				<category><![CDATA[WordPress Security]]></category>
		<category><![CDATA[htaccess]]></category>
		<category><![CDATA[index.php]]></category>
		<guid isPermaLink="false">https://blog.website-malware-removal.com/?p=10418</guid>

					<description><![CDATA[This section explains how to stop detection of malware resident in the process in WordPress. What is process-resident malware? Process-resident malware is a malicious program that runs all the time in the server&#8217;s memory. Because it is resident in memory, this type of malware often has no main program file on the server. The most common type of process-resident malware that is currently confirmed is the type that automatically rewrites htaccess and index.php to prevent login to the administration screen and reinfect other malicious programs. Also confirmed is backdoor-type process-resident malware that keeps the server itself running programmatically in the process, allowing hackers to easily rewrite folders in the server by sending data. Such malware continues to programmatically execute the following commands, including infinite loops. command /usr/local/php/7.4/bin/php /home/path to wordpress/lock666.php command php /home/server user id folder/public_html/path to wordpress/d2a81c15 Instead of executing PHP in response to user access, the php command executes the rogue program directly in memory. Since the program remains in memory, many of them delete their own body files. For this reason, no matter how many files are inspected in the server, this malware cannot be found. Detect and remove process-resident malware Free WordPress:Malware Scan &#038; Security Plug-in [Malware and Virus Detection and Removal]. You can view and stop the list of potentially malicious processes by downloading, adding and activating the WordPress: Malware Scanning &#038; Security Plug-in. WordPress admin > Malware Scan > Security tab > Scroll to the bottom of the screen You can stop the malicious process from the Process Manager. Please note that the function to detect and stop resident malware may not be available if certain commands are not allowed on the server side. Cautions for Stopping Processes The Process Manager function mechanically displays the processes that continue to run using PHP commands, so just because something is displayed here does not necessarily mean that the process is malicious. Please be careful when working with this function, as it may cause server batch processing or other important processes to stop. In our experience, the following processes are most likely to be malware The file itself that the process is executing does not exist on the server. The process has been running for a long time (more than a few hours) (or has been observed repeatedly over a long period of time). The command points to a file in the WordPress core files, and the file does not exist in the WordPress core files. There are no files in the WordPress core files that require direct PHP command execution. The file name that the process is executing is a random meaningless string. Or, the file name is that of a common process-resident malware, such as the following. lock666.php, small.php, moon.php, wjsindex.php, wp-confiq.php (not wp-config.php) and other file names are often used by process-resident malware]]></description>
		
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">10418</post-id>	</item>
		<item>
		<title>Check for WordPress site malware deployed in process (memory)</title>
		<link>https://blog.website-malware-removal.com/10388</link>
		
		<dc:creator><![CDATA[wpdoctoradmin]]></dc:creator>
		<pubDate>Wed, 12 Feb 2025 01:27:58 +0000</pubDate>
				<category><![CDATA[WordPress Security]]></category>
		<category><![CDATA[check]]></category>
		<category><![CDATA[htaccess]]></category>
		<category><![CDATA[index.php]]></category>
		<guid isPermaLink="false">https://blog.website-malware-removal.com/?p=10388</guid>

					<description><![CDATA[This section explains how to check for malware deployed in processes (memory) on a WordPress site. Malware that deploys and executes malicious code in server processes and erases its own code from the server Malware has become more sophisticated in recent years, and some malware first causes its own malicious code to reside in the server process (memory) in an infinite loop, and then deletes its own code (files) from the server. Some of the infinite loop code rewrites HTACCESS and INDEX.PHP to reinfect the server with malware, while others have the functionality of the server itself and use it as a springboard for attacks on other sites. Reference Technical analysis of WordPress hack with PHP script lock360.php as running process Such malware cannot be found no matter how many files are searched on the server. This is because the malware exists only on the process. Get and display processes running on the server To retrieve and display only the PHP processes running on the server that are likely to be malicious processes, we can directly execute commands on the server called ps auwwx &#124; grep -v grep &#124; grep -i php If you get output like the following, it is very likely that malware has been deployed on the process. 10207 2777 0.0 0.0 361172 38688 ? S 07:33 0:03 /opt/plesk/php/7.3/bin/php /var/www/httpdocs/wp-admin/css/colors/blue/lock360.php 10207 → Process ID. 07:33 → Start time of the process 0:03 → Time taken to start running the process /opt/plesk/php/7.3/bin/php → command to run PHP /var/www/httpdocs/wp-admin/css/colors/blue/lock360.php → the file that keeps running (the malware may have already deleted its own file from the server) Why is the resulting file of this command most likely malware? The reason for this is, The file wp-admin/css/colors/blue/lock360.php does not exist in the core WordPress files, PHP is generally only executed by command for batch processing, and WordPress has no built-in program to do batch processing. There is no way that a file that is executed for a long period of time could be in the core WordPress files. Execute the above command from a PHP program and display the output The most common way to execute commands on the server is remotely from a command prompt via an SSH connection, but you can also do this from a PHP program. Copy and paste the code below in a text editor and save it as, for example, processcheck.php. &#60;?php exec("ps auwwx &#124; grep -v grep &#124; grep -i php",$output); print_r($output); Upload this to the server and access it with a browser to view the PHP processes currently running on the server. Some servers may not allow you to retrieve the data in this way, but major rental servers such as Sakura Server and X Server seem to be able to retrieve and display the data properly. If you find a suspicious process, stop the process. Processes can be stopped by executing the following commands on the server, kill -9 123456 -9 → means &#8220;force stop&#8221;. 123456 → Specify the ID of the process.]]></description>
		
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">10388</post-id>	</item>
		<item>
		<title>Malware wp-blog-header.php, wp-cron.php, .htaccess proliferating outside of the public folder on the server in WordPress</title>
		<link>https://blog.website-malware-removal.com/10349</link>
		
		<dc:creator><![CDATA[wpdoctoradmin]]></dc:creator>
		<pubDate>Mon, 06 Jan 2025 01:41:27 +0000</pubDate>
				<category><![CDATA[WordPress Security]]></category>
		<category><![CDATA[backdoor]]></category>
		<category><![CDATA[check]]></category>
		<category><![CDATA[free]]></category>
		<category><![CDATA[htaccess]]></category>
		<category><![CDATA[malware]]></category>
		<category><![CDATA[removal]]></category>
		<category><![CDATA[scan]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[virus]]></category>
		<guid isPermaLink="false">https://blog.website-malware-removal.com/?p=10349</guid>

					<description><![CDATA[If you find multiple wp-blog-header.php, wp-cron.php, and .htaccess files outside of the public folder on your server in WordPress, be careful. These files are most likely malware that propagates automatically. If you have WordPress files in a location other than the public folder on the server with WordPress If there are many .php or HTACCESS files located in folders other than the public WordPress folder (www, public_html), such as htpasswd, script, xserver_php, mail, or folders above them, the server is infected with malware and malware damage may have spread to the entire server. If you have a large number of .php or HTACCESS files located in folders other than htpasswd, script, xserver_php, mail, or the folders above them, they may be infected with malware and the malware may have spread to the entire server. As an example .htaccess wp-blog-header.php wp-cron.php and moon.php or PHP files with random strings. If you download these files using FTP software, open them with a text editor, and see the following obfuscation, the malware is automatically spreading the infection to all folders. PHP files only work on the server, so even if you open the malware with a text editor, it will not infect your PC. Why is malware generated in every folder at the server location? The reason for this is that somewhere on the server there is a type of malware called a backdoor that automatically writes malware to every folder on the server. PHP file malware cannot take effect without access, so it does not make sense if it is outside the public folders, but because of the low quality of the backdoor, it can write a lot of malware not only to the folder where WordPress is located, but also to private folders. *But if a malicious HTACCESS file is written outside the public folder, it can adversely affect the lower level folders, making it impossible to log in to WordPress or disabling some functions of the administration panel. How to deal with malware written outside the public folder If you are sure that the malware is not in the public folder of the server, you can remove it by deleting the file as is. However, it is possible that a backdoor or other malware may have infected some of the folders where WordPress is located, so it is also necessary to inspect and remove malware from WordPress as a whole. (If you do not delete the main body file of the malware that is infecting WordPress, it will re-infect the WordPress site.) Free WordPress:Malware Scan &#038; Security Plug-in [Malware and Virus Detection and Removal]. We also need to close the vulnerability that allowed hackers to deface the site in the first place. Reference Five WordPress security measures If left unchecked, malware can lead to exclusion from search results, inaccessibility of the site, and users being redirected to other malicious sites where they can be infected with viruses. If you feel that the situation is out of control, please consider consulting a specialist as soon as possible.]]></description>
		
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">10349</post-id>	</item>
		<item>
		<title>Analysis of WordPress malware that revives in an instant or changes permissions (write permissions) of index.php and htaccess files</title>
		<link>https://blog.website-malware-removal.com/10343</link>
		
		<dc:creator><![CDATA[wpdoctoradmin]]></dc:creator>
		<pubDate>Mon, 23 Dec 2024 01:49:51 +0000</pubDate>
				<category><![CDATA[WordPress Security]]></category>
		<category><![CDATA[free]]></category>
		<category><![CDATA[htaccess]]></category>
		<category><![CDATA[index.php]]></category>
		<category><![CDATA[malware]]></category>
		<category><![CDATA[removal]]></category>
		<category><![CDATA[scan]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[virus]]></category>
		<guid isPermaLink="false">https://blog.website-malware-removal.com/?p=10343</guid>

					<description><![CDATA[Analyze wordpress malware that revives in an instant or changes the permissions (write permissions) of index.php and htaccess files. Symptoms of process-resident malware This type of malware causes symptoms of sending users who visit a site to another malicious site or hooking fake pages into Google searches. It also features modifications to index.php, htaccess, wp-config.php, and other files to disable access to the site&#8217;s administrative functions. In addition, the malware files and tampering are immediately restored after disinfection, or are processed in an instant (automatic processing) by changing the write permissions of folders and files so that they cannot be disinfected. What is the technology of malware that resides in server processes (memory) and reinfects them in an instant? Our analysis of this type of malware revealed that it resides in the server process in the following manner. 1 Code for the main body of the malware, which improves various files to execute malicious actions on the site, is pulled in from the outside using the $_POST function, etc., and executed. 2 Erasing its own files with code such as unlink($_SERVER[&#8216;SCRIPT_FILENAME&#8217;]) 3 Even if you delete your own file, the code is already loaded into memory, so execution continues. 4 Next, write the infinite loop to the server process do{ //Code for the infinite loop }while(1) 5 The above infinite loop code contains code that monitors site tampering and disinfection operations on the site operator&#8217;s side, such as changing permissions, and re-executes the tampering. As soon as the site operator disinfects the malware, the malware 1 is reinfected. In other words, the file of the body of this malware does not exist in the server, but only in an infinite loop in the memory of the server process. How to get rid of server process-resident malware? Since this malware does not exist as a file, it can only be removed (stopped) in the following two ways 1 Restart the server (or PHP) 2 Stop PHP infinite loop by server command Examples of commands php system("kill process id"); Once the process is stopped, any other tampering or malware that exists as a file can be detected and removed with plug-ins such as the [Free] WordPress:Malware Scan &#038; Security Plug-in [Malware and Virus Detection and Removal]. However, common shared servers do not allow server restarts, and executing commands on the server often requires a special PHP program to mediate. The format for executing commands on the server using PHP as an intermediary is as follows shell_exec("command");]]></description>
		
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">10343</post-id>	</item>
		<item>
		<title>If you get a 403Forbidden error on the bottom page of your WordPress site or on the admin page, you may be infected with malware</title>
		<link>https://blog.website-malware-removal.com/10305</link>
		
		<dc:creator><![CDATA[wpdoctoradmin]]></dc:creator>
		<pubDate>Fri, 22 Nov 2024 01:14:08 +0000</pubDate>
				<category><![CDATA[WordPress Security]]></category>
		<category><![CDATA[backdoor]]></category>
		<category><![CDATA[error]]></category>
		<category><![CDATA[free]]></category>
		<category><![CDATA[htaccess]]></category>
		<category><![CDATA[index.php]]></category>
		<category><![CDATA[malware]]></category>
		<category><![CDATA[removal]]></category>
		<category><![CDATA[scan]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[virus]]></category>
		<guid isPermaLink="false">https://blog.website-malware-removal.com/?p=10305</guid>

					<description><![CDATA[If you get a 403Forbidden error on the bottom page of your WordPress site or on the admin page, you may be infected with malware Suddenly your WordPress site gets a 403Forbidden error A 403 error can mean that the server is forbidding access to the site. While this is often caused by an error in the HTACCESS description or a permissions issue, it can also be caused by a malware infection. *The HTACCESS file is a file that writes various server settings in the top directory of WordPress Malware may alter and rewrite the HTACCESS file to prohibit access to the WordPress administration screen and certain pages within the administration screen, making it impossible to detect and remove the malware. Malware may randomly install the above malicious HTACCESS files in the server, resulting in a 403 error for the entire WordPress site, including the lower-level pages and folders. Examples of HTACCESS file tampering As an example of a tampered HTACCESS file, the following tampering code may be embedded in the file. &#60;FilesMatch ".*\.(py&#124;exe&#124;phtml&#124;php&#124;PHP&#124;~ A list of multiple extensions~.&#124;phP8&#124;PhP8&#124;suspected)$"&#62; Order Allow,Deny Deny from all &#60;/FilesMatch&#62; &#60;FilesMatch "^(index.php&#124;wp-login.php&#124;~ A list of multiple file names~&#124;wp-crom.php&#124;wp-confiq.php)$"&#62; Order Allow,Deny Allow from all &#60;/FilesMatch&#62; FilesMatch &#8220;.*\. (py&#124;exe&#124;phtml&#124;ph ~ Deny from all means that files with extensions such as py, exe, phtml, php, etc. should not be accessible. This description is causing 403 errors. FilesMatch &#8220;^(index.php&#124;wp-login.php&#124;wp- ～ Allow from all This line means that the malware only allows access to files that are convenient for hackers (backdoors, etc.). Such tampering may be of low quality code and can be generated in the server at random. This may result in a 403 error for the entire site on the server or a blank screen, making it impossible to display the site itself. How to deal with unauthorized tampering HTACCESS files If such a tampered HTACCESS file has been installed on the server, it is necessary to delete the HTACCESS file itself if it is in an unnecessary place, and if the malicious code is included in a legitimately installed HTACCESS by WordPress, it is necessary to remove only the malicious code part. If the malicious code is included in the HTACCESS file, it is necessary to remove only the malicious code part. Generally, WordPress installs only one HTACCESS file in the top directory of WordPress. However, plug-ins and themes may be installed in the upload folder or in the plug-ins&#8217; or themes&#8217; folders. HTACCESS files can also be randomly placed in deeper folders by malware, making it difficult to find them all. In such cases, we recommend that you use a malware scanning plug-in to perform a comprehensive scan. Free] WordPress:Malware Scan &#038; Security Plug-in [Malware and Virus Detection and Removal]. However, since HTACCESS tampering is caused by a wide variety of code patterns, it may not be possible to detect all of them even if you use the above plug-ins. Please consider consulting a specialist if you are unable to completely remove the tampering or if there is a possibility that the tampering is still present.]]></description>
		
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">10305</post-id>	</item>
		<item>
		<title>How to prevent a brute force attack on XMLRPC.php in WordPress</title>
		<link>https://blog.website-malware-removal.com/10300</link>
		
		<dc:creator><![CDATA[wpdoctoradmin]]></dc:creator>
		<pubDate>Wed, 13 Nov 2024 01:30:35 +0000</pubDate>
				<category><![CDATA[WordPress Security]]></category>
		<category><![CDATA[check]]></category>
		<category><![CDATA[free]]></category>
		<category><![CDATA[htaccess]]></category>
		<category><![CDATA[malware]]></category>
		<category><![CDATA[plugin]]></category>
		<category><![CDATA[removal]]></category>
		<category><![CDATA[scan]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[virus]]></category>
		<guid isPermaLink="false">https://blog.website-malware-removal.com/?p=10300</guid>

					<description><![CDATA[This section explains how to prevent a brute force attack on XMLRPC.php in WordPress. A brute force attack with XMLRPC in WordPress XMLRPC is a feature that provides various remote control functions, such as WordPress submissions via xmlrpc.php in the top directory of WordPress. However, this function can also be used in a brute force hacking attack to send various login passwords to see if they can be used to log in and determine the password. For example, WPSCAN has a function that executes the function wp.getUsersBlogs via XMLRPC to find passwords that allow login. WPSCAN is a well-known security (hacking) tool that also checks for WordPress vulnerabilities and has a brute force attack function. The following is a sample code that calls this function in PHP. $ch = curl_init(); curl_setopt($ch, CURLOPT_URL, "http://Wordpress URL/xmlrpc.php"); curl_setopt($ch, CURLOPT_POST, true); curl_setopt($ch, CURLOPT_RETURNTRANSFER, true); $content = array(); $params = array( 'username', 'password', $content); $params = xmlrpc_encode_request('wp.getUsersBlogs', $params); curl_setopt($ch, CURLOPT_POSTFIELDS, $params); $result = curl_exec($ch); curl_close($ch); echo ($result); If the login ID and password are different, the output is as follows XMLRPC is used to determine whether the login was successful or not and to determine the password by brute force. Preventing XMLRPC Attacks To prevent a brute force attack on XMLRPC, you can write code to disable access to xmlrpc.php in the HTACCESS file located in the top directory of WordPress. # Block WordPress xmlrpc.php requests order deny,allow deny from all You can also disable XMLRPC functionality by adding the following to your theme&#8217;s Functions.php. Add_filter( 'xmlrpc_enabled', '__return_false' ); However, completely blocking XMLRPC may interfere with the use of WordPress applications and certain plugins. In this case, it may be necessary to block a large number of accesses to xmlrpc.php during a specific period of time. This function can be easily set up for free with the [Free] WordPress:Malware Scan &#038; Security Plugin [Malware and Virus Detection and Removal]. Please use it if you like.]]></description>
		
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">10300</post-id>	</item>
	</channel>
</rss>
