Detection of Hotbar

[Matthias Oberlinner]

Hi,

I would like to know why MS Anti-Spyware BETA does not
recognize the Hotbar Application as Spyware
(http://www.hotbar.com). While the real-time engine
identifies actions of this application as Spyware
behavior, a complete scan does not find Hotbar.
Additionally a "Microsoft Certified Partner" logo can be
found on the website of Hotbar
(http://www.hotbar.com/installation/browsing/install.aspx)
.. The following article describes the questionable
behavior in detail:
http://www.adwarereport.com/mt/archives/000150.html.

Could someone from MS please answer the following
questions:
* Is the "Microsoft Certified Partner" logo official and
if it is, what does it imply?
* Why is a known Spyware application not detected, while
its behavior is reportet?

Thank you,
Matthias Oberlinner

 

[Engel]

http://www.pchell.com/support/hotbar.shtml

 

[matthias oberlinner]

thanks, but this does not answer my questions.
i know already that hotbar is bad.

matthias oberlinner

 

[Bill Sanderson]

I don't think this group can provide what you are asking.

You could do a Tools, suspected spyware report, and lay out exactly which of
the guidelines that Microsoft publishes you feel that this app violates:

http://support.microsoft.com/?kbid=892340

Unfortunately the relevant links in this KB article are broken because
content is being moved and the article hasn't been revised to show the new
locations.

Theres a more general white paper which is still available showing criteria:

http://www.microsoft.com/athome/security/spyware/software/isv/analysis.mspx

 

[Matthias Oberlinner]

thank you.
I was pointed to this group by the MS Premium Service,
because Anti-Spyware is not yet a fully supported product.
I will try to extract the information from the articles
you mentioned.

Matthias Oberlinner

 

[Bill Sanderson]

The KB article that I've linked to in the previous message should be
authorititative, and link to a clear list of criteria for listing. The
links are now broken. I've made a request to fix this--and others are
welcome to do so as well via the feedback at the bottom of the article.

So--recheck that KB article periodically--I can't predict how long it may
take to fix.