Wrong trojan detection (BoeBot.Explorer)

  • Thread starter Thread starter Henry Habermacher [MVP Access]
  • Start date Start date
H

Henry Habermacher [MVP Access]

Following steps result in a wrong detection of a trojan (BoeBot.Explorer)

- Create a New Text Document on the desktop
- Rename "New Text Document.txt" to "something.vbs"
- Open something.vbs by doubleclicking it

==> Microsoft AntiSpaware Alert appears, telling

========================================================================
[X] Warning, BoeBot.Explorer Trojan is trying to Install!
========================================================================
Microsoft AntiSpyware has detected the threat PoeBot.Explorer trying to
install a Script on your computer. If you would like to allow
PoeBot.Explorer to install the Script click the 'Allow' Buton below.

Name: PoeBot.Explorer
Type: Trojan
Threat Level: Severe

(!) Click more information about this threat ...

========================================================================
what would you like to do?

[Allow] [Remove!]

[] Always ignore this threat
========================================================================

And an additional bug: Clicking on more information results in "The
requested information is not
currently available"

Remove tells me it could successfully remove this Trojan?!? what ever it may
have removed. My empty .vbs fils is still here.

But I'm pretty shure, this trojan doesn't exist on my machine at all. It's
just a wrong alert if I'm starting a .vbs File without any content.

If I just add a comment sign (') to the first line of the newly created file
AntiSpyware just informs me that a script is beeing to be executed.

HTH to reproduce

Greetings from Phuket/Thailand

Henry Habermacher, MVP Access
 
There's no automatic upgrade during the beta--new builds are requiring new
downloads. I reproduced on .509, fwiw.
 
I have the same thing, but it happend to me after
clicking on my autoexec. file in windows. Hidden. I just
posted in general about this and am now just reading
this. So I guess I need not worry. Correct? Michael
 
I think you are correct--thanks for providing a concrete example where a
user could be unnecessarily alarmed by this misdetection.

The autoexec.bat file normally lives in the root of the drive windows boots
from, and isn't normally hidden--you can look at it with notepad, for
example. If you confirm that it is empty via notepad, or by looking at the
length in a file listing, that'd be enough evidence for me that this is the
same issue.

Thanks for reading before posting!
 
Back
Top