Thanks for the update on this enejb.
With the (still) ongoing problems caused by the timthumb vulnerability and its aftermath of code fragments and other artifacts, we’d been a bit paranoid about any suspicious file reported by the scanners we’ve been using.
(Which isn’t much, considering a lot of us don’t work for some large corp that can afford the licensing fees charged by providers of these heavy-duty scanning apps, systems and services.)
