Re: scans for root.exe

[Christian Kuhtz <ck () gnu org>]

Jacek Lipkowski wrote:
> On Thu, 16 Aug 2001, David Pick wrote:
>
> > These are attempts to use the "backdoor" left behind by the third
> > main variant of the CodeRed worm. What command are they trying to
> > execute? (should be passed as parameters to the query) or are they
> > just looking to see if it's there at all?
>
> don't assume root.exe is code red specific, i've seen cmd.exe copied to
> the scripts directory named root.exe in one box that was probably hacked
> using the double-unicode-decode bug (or whatever it's called). this was a
> few months ago.
>
> root.exe just seems to be a popular name...

So, how the heck do you positively confirm CR (v1 & v2) infection then?  Seems
all the eEye scanner does is check the response of GET /scripts/root.exe which
according to what you just wrote isn't necessarily indicative of CR.

Around here, we've had at least one case of suspected false positive (by eEye)
that would confirm that.  It had the root.exe backdoor, but it didn't have any
of the other signs of CRv2 (registry, no explorer.exe trojan etc).

So, how do you positively confirm CRv2 infection from the outside?  I haven't
been able to find any conclusive documentation.  If I missed it, please give
me a point with a fence post.

Thanks,
Chris

-- 
Christian Kuhtz <ck () arch bellsouth net> -wk, <ck () gnu org> -hm
Sr. Architect, Engineering & Architecture, BellSouth.net, Atlanta, GA, U.S.
"I speak for myself only."

----------------------------------------------------------------------------
This list is provided by the SecurityFocus ARIS analyzer service.
For more information on this free incident handling, management 
and tracking system please see: http://aris.securityfocus.com