I’ve recently seen the same false positive for this plugin using ClamAV. Might be worth contacting them to see what it is in your code that’s matching their database and what can be done to avoid the false positive.
Thread Starter
astopy
(@astopy)
Ok, scrap that. Apparently the times are stored in the DB with the GMT offset already added on, rather than doing the sensible thing and storing the times as UTC then adding the offset when the page is rendered. Entering 175320 in the GMT offset box did the trick.
