This section describes injection attacks in which malicious content is inserted into WordPress pages.
This section describes the character strings that should not be used in the administrator password of a WordPress site.
This section explains how to check for malware deployed in processes (memory) on a WordPress site.
What kind of attacks can hackers launch on a WordPress site? We will explain about the following
We have compiled a list of precautions for malware removal for a group of WordPress sites spanning multiple domains on a single server.
We will explain why a site is infected with malware in WordPress and moves itself to another site, and why the malicious code comes back after a while, no matter how many times you remove it.
There have been cases where the WordPress staging environment has been contaminated with malware and malware has spread to this site. It is necessary to operate the WordPress staging environment in a security-conscious manner.
In some cases, malware-infected sites may not be able to delete malicious files due to permission errors (write permission errors).
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.
Analyze wordpress malware that revives in an instant or changes the permissions (write permissions) of index.php and htaccess files.
WordPress sites, no matter how small, are actually exposed to hacking attacks on a daily basis. We will explain how to detect this WordPress hacking and block IPs.
We will describe a case where the public_html folder was not writable due to malware infecting WordPress, and the permissions could not be changed, making it impossible to remove the malware.
We will explain the method of brute force attack that tries to break through the administrator’s password through XMLRPC.php in WordPress and how to prevent it.
Malware that reads files that do not originally exist and writes them to various folders with “$wp_update_file=” in WordPress is detected very often these days.
The following are the three vulnerabilities that are most likely to be exploited if discovered on a WordPress site. If your site contains any plug-ins or other components that are vulnerable to these vulnerabilities, we recommend that you take action as soon as possible.
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
This section explains how to prevent a brute force attack on XMLRPC.php in WordPress.
We would like to introduce a case in which malware infection led to a lawsuit by a client who requested us to investigate the status of malware infection.
