I doubt that will work.

See here:

http://securityadmin.info/faq.asp#ftpfolder
http://securityadmin.info/faq.asp#hacked
http://securityadmin.info/faq.asp#re-secure
http://securityadmin.info/faq.asp#harden

Briefly, the attacker probably installed an FTP server like Serv-U FTP on
your computer and used up your internet connection bandwidth and hard drive
space. People think they don't need to secure their home computer and test
systems that don't have any important data, but you still do. Using the 8.3
file name such as by DIR /X is usually part of the solution, in order to
bypass certain reserved words in the file name such as COM1 that Windows
Explorer won't let you manipulate. [Disabling posix support would have
prevented this trick from being used to make the files hard to delete.] See
the links above for more details.

BTW, you not only need to delete the files, you better determine how you
were hacked and what other changes or software was installed on your
computer, or else you'll be hacked again. You were probably hacked by
something very simple to fix, like missing patches, no firewall, and/or you
left IIS FTP service running with the IUSR anonymous user having both read
and write permission to one folder. www.kerio.com and www.sygate.com are
free firewalls.

If you didn't leave the IIS FTP service running, then your computer was
completely compromised / remotely controlled, as new software was installed
on it.


[quoted text, click to view]

On Fri, 19 Dec 2003 15:51:17 -0800, "JonR"
[quoted text, click to view]

Best is to wipe and reinstall, but if you're *sure* it was just an
open FTP server, try:

How to Remove Files with Reserved Names in Windows:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;120716
You Cannot Delete a File or a Folder
http://support.microsoft.com/?id=320081

I also wish to add that we typically recommend, along with cert.org, that a
compromised box cannot be fully trusted and that the best practice is to
fdisk, format, and reinstall the OS after having been compromised.

There is some good general advice at:
http://www.cert.org/tech_tips/win-UNIX-system_compromise.html