Hello @deanysys,
Thank you for using the plugin and positive comment.
The plugin in question would have been reported if WP Security Audit Log was able to determine which one was it. So the fact that it is not reported means that it was unable to detect it.
I would recommend you to check the custom post in question, see what it is etc. It might contain information about the plugin in question or contain enough information to lead you to the culprit.
Can you please keep us posted? Thank you.
Hey,
Thanks for the tips. I tried searching for the custom post, but it doesn’t exist. I also don’t see in Audit Log that anything else was done with that post or by that plugin, but then again I immediately blocked the IP with Wordfence.
So, not sure what happened there, but don’t see the plugin or the custom post that Audit Log says was created.
Haven’t seen any more of this thus far, been closely monitoring. We’ll see.
Thanks.
By any chance did you search the audit trail for the offending IP address? It would be interesting to see if there are more records / changes associated to that IP address.
Hello @deanysus,
We just released version 2.6.8, which has an improved sensor that does not report such issues. Please install the update and do not hesitate to get in touch should you encounter any further issues.
Thank you for using our plugin.
