Get Off Those Maliciously Loaded Scripts!
Download this free Anti-Malware Plugin for WordPress.

Thank you for posting this new rogue plugin code to me. I have added the pattern of this new threat to my definition updates so that it can now be found and automatically fixed with my plugin scan. Please let me know if you find any more like this.

I removed the link in that text for security reasons. Please send me any malicious files (complete and unedited) directly via email so I can see the full original threat in those files as well as any potentially benign content that might have been added to disguise the threat or may have been there before the malicious content was injected.

You can always use the “Forgot Password” link on the login form: https://gotmls.net/wp-login.php

Or, if you are already logged in you can use the standard profile URL in the wp-admin:
/wp-admin/profile.php

If you are logged into the site you can go to your profile in the wp-admin, or if you are not logged into the site you can use the forgot password link to reset your password.

I have whitelisted this usage only because it is still used in this fairly active pods plugin, even though it was found in /plugins/pods/deprecated/deprecated.php which shows that even the developers know that this code is deprecated and should be removed. This code probably isn’t even safe any more because the file it includes has not existed in any WordPress distribution since 3.8.9 which is over 10 years old now. So if this code was executed on any WordPress site that has updated within the last ten years then it would cause a fatal error for trying to include a file that doesn’t exist. But it’s not malicious so I have decided to whitelist it for now.

I may even change my mind and re-include this code later because it is unsafe and if you were to use my plugin to fix this file and remove that include line then it would only serve to prevent your site from crashing on this error if your json_encode function were somehow blocked or removed from your PHP libraries.

Thanks for reporting this but I do absolutely need more information if I am to fix this issue. Namely, I need to know which plugin files are being wrongly identified as a threat. Can you please send me those files so that I can examine the code in them and fix the definition that is flagging this code?

You can email the files directly to me or send me a link to where I can download these plugins myself.

There are no conflicts with my plugin and any other security plugin that I am aware of.

In general, there are some feature that might be duplicated within various security plugins but they each work a little differently and so one might work better in certain circumstances than the the next, it all depends on the type of attack and the kind of mitigation employed for that attack. For example, the Brute-Force Protection in my plugin is invoked prior to the WordPress bootstrap, so my plugin will redirect brute-force attacks before WordPress (and most other plugins) are loaded and this will reduce the load on your server which could prevent a DDoS attack from bringing down the site, but it might also prevent other security plugins from logging the attack (because they are not yet loaded or connected to your database before the attack is deflected). I wouldn’t call this a direct conflict but it could affect the statistics recorded by those other plugins.

I have had instances in the past were other security plugins have either hijacked one of my hooks into the WordPress code library or even changed one of my own lines of code, which had caused a substantial failure of my plugin to preform essential tasks, but I was always able to work out those conflicts and find a suitable solution for all involved.

If you even find any issues with my plugin working in conflict with another plugin then please report it to my right away and I will find a solution for you.