|Teamspeak Server Hosting Discuss Teamspeak Servers with your peers.|
Copy of "ATTENTION TEAMSPEAK USERS! Posted by: [florence]" on TeamSpeak.org
As of about a week ago, many users within the Teamspeak community informed us of a possible virus issue -- specifically with the "keypress.dll" file which is installed by the Teamspeak client.
Since we were informed of this issue the Teamspeak Team has been heavily involved in trying to determine the accuracy of this claim. After rigorous internal testing and numerous phone calls into all of the major antivirus companies including Symantec (Norton Antivirus), Network Associates (McAfee), and Trend Micro, NONE of these companies can verify NOR deny that a virus actually exists in "keypress.dll".
To the best of our collective knowledge, it is so far more likely that this is a "false positive" -- meaning that the antivirus application is finding
data in keypress.dll that LOOKS like the same sort of data found in an infected file containing the Trojan "PWS-Wexd" (virus)...even though the file is most likely not infected at all.
If you are still truly concerned that this may actually be a virus, please try visiting the following link:
This URL contains detailed information on the PWS-Wexd Trojan, including a section on "indications of infection" -- which we have meticulously verified so far do NOT exist on anyone's supposed infected computer.
At this time we have put together a new Teamspeak client installation executable which you may download from:
Simply shutdown your Teamspeak client if it is running and re-install Teamspeak using this executable right on top of your existing installation and the problem should go away. It is NOT necessary to first uninstall your existing Teamspeak client and you will also NOT lose your current Address Book and other client settings.
It is our every intent to resolve matters such as these in a timely manner...and with as much information to validate a working solution as possible. We want to thank you for your patience as we work through this issue.
Please visit the following forum thread for further information and discussion:
- The TeamSpeak Team