As most security experts will tell you, over 30% of all malware infestations are because of a database infection.
This kind of infection is destructive and often constitutes a persistent threat.
Cleaning them up can be very tasking and time-consuming to you, the website owner.
The vector of infection can be:
- a situation where a developer copies and pastes a code without understanding what it actually does.
- via an installed plugin or extension.
- or a deliberate infestation that occurred because the website owner has not enforced available two-factor authentication and someone gains access to his or her system.
The truth is that it doesn't really matter how it happens.
One thing that is certain is that this often stays hidden and the authors can selectively call them to function without anyone being any wiser.
But even more so is that the account will stay compromised and will cause malicious files to keep on reappearing.
Today, we are announcing Malware Database Scanner.
This new feature gets to the bottom of such problems and completely eliminates DB infections.
It does this by getting DB connection details from WordPress configuration files.
Then it safely and reliably backs up suspicious DB data ensuring that each step can be unmade in case an issue arises.
Clean up the infection, ensure that the database is functioning as intended, and then roll out the new and healthy database.
This happens 100% out of sight without you needing to do anything at all.
No SQL knowledge, no connection strings, passwords, etc needed.
For the moment, only WordPress databases are supported.
And all WordPress CMS hosted on our systems have access to this feature.
But the feature will be extended to include all content management systems (CMS) once released.
Please note that while this has been enabled, it is still a beta feature.
Our team is closely monitoring its performance and hoping that it will help protect you even better.
If you noticed any odd database behavior, do let us support team know at once.
Thanks and have a great weekend.
{$signature}
