Complaint Review: Buysmarter.com - Internet

Sir, the Sasser Virus doesn't come from websites, nor does it go to your desktop. You get Sasser when another exploited computer that's infected with the virus scans port 445 on your computer and finds it open. Then it installs itself. You don't know you are infected until your computer starts rebooting on it's own. I'd advise you to turn on your auto update in WinXP and *always* have an Anti-Virus program running when you are connected to the internet. I use Norton Anti-Virus and feel it's the best there is. You should also enable the firewall that comes with XP or find one online to install. I like ZoneAlarm. http://www.zonelabs.com/store/content/home.jsp They have both a free version and a pro version you can purchase from their website. If you are on a cable connect to the internet as I am and you don't turn off your computer when you aren't online, ZoneAlarm allows you to stop all internet activity when you don't need an online connection. This will keep you safer. -------- http://spywarewarrior.com/viewtopic.php?t=68 You might want to read thru this forum and check out the list of bad programs that are available online that claim to help you with spyware, adware, viruses, etc. This will help you in the future should you decide to try another program, so you don't get ripped off again. This isn't a full list by any means, but it's a good starting point. -------- Below is a website you can visit to read more on the sasser virus, but I included most of the basic info on it in this rebuttal for you. :-) http://www.f-secure.com/v-descs/sasser.shtml Sasser was written in Visual C++ and it spreads in a single executable which is packed and protected with several envelopes. System Infection When the worm enters the system it creates a copy of itself in the Windows Directory as 'avserve.exe'. This copy is added to the Registry as: [SOFTWARE\Microsoft\Windows\CurrentVersion\Run] "avserve.exe" = "%WinDir%\avserve.exe" To ensure that only one copy of the worm is running it creates a mutex named 'Jobaka3l'. Network Propagation Sasser exploits the the MS04-011 (LSASS) vulnerability to gain access the remote systems. The worm starts 128 scanning threads that try to find vulnerable systems on random IP addresses. Computers are probed on port 445 which is the default port for Windows SMB communication on NT-based systems. The probing might crash unpatched computers. When attacking the worm first determines the version of the remote operating system then uses the appropriate parameters to attack the host. Different parameters are used for - Windows XP (universal exploit) - Windows 2000 (universal exploit) - Windows 2000 Advanced Server (SP4 exploit) Other operating systems, such as Windows Me and NT are not infected by this worm. If the attack is successful a shell is started on port 9996. Through the shell port Sasser instructs the remote computer to download and execute the worm from the attacker computer using FTP. The FTP server listens on port 5554 on all infected computers with the purpose of serving out the worm for other hosts that are being infected. Transactions through the FTP server are logged to 'C:\win.log'. Summary of TCP ports used by the worm: 445/TCP: - The worm attacks through this port 5554/TCP: - FTP server on infected systems 9996/TCP: - Remote shell opened by the exploit on the vulnerable hosts The Vulnerability This vulnerability is caused by a buffer overrun in the Local Security Authority Subsystem Service of Windows NT-based systems. Detailed information on the vulnerability and the available fixes are at http://www.microsoft.com/technet/security/bulletin/MS04-011.mspx

Sir, the Sasser Virus doesn't come from websites, nor does it go to your desktop. You get Sasser when another exploited computer that's infected with the virus scans port 445 on your computer and finds it open. Then it installs itself. You don't know you are infected until your computer starts rebooting on it's own. I'd advise you to turn on your auto update in WinXP and *always* have an Anti-Virus program running when you are connected to the internet. I use Norton Anti-Virus and feel it's the best there is. You should also enable the firewall that comes with XP or find one online to install. I like ZoneAlarm. http://www.zonelabs.com/store/content/home.jsp They have both a free version and a pro version you can purchase from their website. If you are on a cable connect to the internet as I am and you don't turn off your computer when you aren't online, ZoneAlarm allows you to stop all internet activity when you don't need an online connection. This will keep you safer. -------- http://spywarewarrior.com/viewtopic.php?t=68 You might want to read thru this forum and check out the list of bad programs that are available online that claim to help you with spyware, adware, viruses, etc. This will help you in the future should you decide to try another program, so you don't get ripped off again. This isn't a full list by any means, but it's a good starting point. -------- Below is a website you can visit to read more on the sasser virus, but I included most of the basic info on it in this rebuttal for you. :-) http://www.f-secure.com/v-descs/sasser.shtml Sasser was written in Visual C++ and it spreads in a single executable which is packed and protected with several envelopes. System Infection When the worm enters the system it creates a copy of itself in the Windows Directory as 'avserve.exe'. This copy is added to the Registry as: [SOFTWARE\Microsoft\Windows\CurrentVersion\Run] "avserve.exe" = "%WinDir%\avserve.exe" To ensure that only one copy of the worm is running it creates a mutex named 'Jobaka3l'. Network Propagation Sasser exploits the the MS04-011 (LSASS) vulnerability to gain access the remote systems. The worm starts 128 scanning threads that try to find vulnerable systems on random IP addresses. Computers are probed on port 445 which is the default port for Windows SMB communication on NT-based systems. The probing might crash unpatched computers. When attacking the worm first determines the version of the remote operating system then uses the appropriate parameters to attack the host. Different parameters are used for - Windows XP (universal exploit) - Windows 2000 (universal exploit) - Windows 2000 Advanced Server (SP4 exploit) Other operating systems, such as Windows Me and NT are not infected by this worm. If the attack is successful a shell is started on port 9996. Through the shell port Sasser instructs the remote computer to download and execute the worm from the attacker computer using FTP. The FTP server listens on port 5554 on all infected computers with the purpose of serving out the worm for other hosts that are being infected. Transactions through the FTP server are logged to 'C:\win.log'. Summary of TCP ports used by the worm: 445/TCP: - The worm attacks through this port 5554/TCP: - FTP server on infected systems 9996/TCP: - Remote shell opened by the exploit on the vulnerable hosts The Vulnerability This vulnerability is caused by a buffer overrun in the Local Security Authority Subsystem Service of Windows NT-based systems. Detailed information on the vulnerability and the available fixes are at http://www.microsoft.com/technet/security/bulletin/MS04-011.mspx

Sir, the Sasser Virus doesn't come from websites, nor does it go to your desktop. You get Sasser when another exploited computer that's infected with the virus scans port 445 on your computer and finds it open. Then it installs itself. You don't know you are infected until your computer starts rebooting on it's own. I'd advise you to turn on your auto update in WinXP and *always* have an Anti-Virus program running when you are connected to the internet. I use Norton Anti-Virus and feel it's the best there is. You should also enable the firewall that comes with XP or find one online to install. I like ZoneAlarm. http://www.zonelabs.com/store/content/home.jsp They have both a free version and a pro version you can purchase from their website. If you are on a cable connect to the internet as I am and you don't turn off your computer when you aren't online, ZoneAlarm allows you to stop all internet activity when you don't need an online connection. This will keep you safer. -------- http://spywarewarrior.com/viewtopic.php?t=68 You might want to read thru this forum and check out the list of bad programs that are available online that claim to help you with spyware, adware, viruses, etc. This will help you in the future should you decide to try another program, so you don't get ripped off again. This isn't a full list by any means, but it's a good starting point. -------- Below is a website you can visit to read more on the sasser virus, but I included most of the basic info on it in this rebuttal for you. :-) http://www.f-secure.com/v-descs/sasser.shtml Sasser was written in Visual C++ and it spreads in a single executable which is packed and protected with several envelopes. System Infection When the worm enters the system it creates a copy of itself in the Windows Directory as 'avserve.exe'. This copy is added to the Registry as: [SOFTWARE\Microsoft\Windows\CurrentVersion\Run] "avserve.exe" = "%WinDir%\avserve.exe" To ensure that only one copy of the worm is running it creates a mutex named 'Jobaka3l'. Network Propagation Sasser exploits the the MS04-011 (LSASS) vulnerability to gain access the remote systems. The worm starts 128 scanning threads that try to find vulnerable systems on random IP addresses. Computers are probed on port 445 which is the default port for Windows SMB communication on NT-based systems. The probing might crash unpatched computers. When attacking the worm first determines the version of the remote operating system then uses the appropriate parameters to attack the host. Different parameters are used for - Windows XP (universal exploit) - Windows 2000 (universal exploit) - Windows 2000 Advanced Server (SP4 exploit) Other operating systems, such as Windows Me and NT are not infected by this worm. If the attack is successful a shell is started on port 9996. Through the shell port Sasser instructs the remote computer to download and execute the worm from the attacker computer using FTP. The FTP server listens on port 5554 on all infected computers with the purpose of serving out the worm for other hosts that are being infected. Transactions through the FTP server are logged to 'C:\win.log'. Summary of TCP ports used by the worm: 445/TCP: - The worm attacks through this port 5554/TCP: - FTP server on infected systems 9996/TCP: - Remote shell opened by the exploit on the vulnerable hosts The Vulnerability This vulnerability is caused by a buffer overrun in the Local Security Authority Subsystem Service of Windows NT-based systems. Detailed information on the vulnerability and the available fixes are at http://www.microsoft.com/technet/security/bulletin/MS04-011.mspx

Sir, the Sasser Virus doesn't come from websites, nor does it go to your desktop. You get Sasser when another exploited computer that's infected with the virus scans port 445 on your computer and finds it open. Then it installs itself. You don't know you are infected until your computer starts rebooting on it's own. I'd advise you to turn on your auto update in WinXP and *always* have an Anti-Virus program running when you are connected to the internet. I use Norton Anti-Virus and feel it's the best there is. You should also enable the firewall that comes with XP or find one online to install. I like ZoneAlarm. http://www.zonelabs.com/store/content/home.jsp They have both a free version and a pro version you can purchase from their website. If you are on a cable connect to the internet as I am and you don't turn off your computer when you aren't online, ZoneAlarm allows you to stop all internet activity when you don't need an online connection. This will keep you safer. -------- http://spywarewarrior.com/viewtopic.php?t=68 You might want to read thru this forum and check out the list of bad programs that are available online that claim to help you with spyware, adware, viruses, etc. This will help you in the future should you decide to try another program, so you don't get ripped off again. This isn't a full list by any means, but it's a good starting point. -------- Below is a website you can visit to read more on the sasser virus, but I included most of the basic info on it in this rebuttal for you. :-) http://www.f-secure.com/v-descs/sasser.shtml Sasser was written in Visual C++ and it spreads in a single executable which is packed and protected with several envelopes. System Infection When the worm enters the system it creates a copy of itself in the Windows Directory as 'avserve.exe'. This copy is added to the Registry as: [SOFTWARE\Microsoft\Windows\CurrentVersion\Run] "avserve.exe" = "%WinDir%\avserve.exe" To ensure that only one copy of the worm is running it creates a mutex named 'Jobaka3l'. Network Propagation Sasser exploits the the MS04-011 (LSASS) vulnerability to gain access the remote systems. The worm starts 128 scanning threads that try to find vulnerable systems on random IP addresses. Computers are probed on port 445 which is the default port for Windows SMB communication on NT-based systems. The probing might crash unpatched computers. When attacking the worm first determines the version of the remote operating system then uses the appropriate parameters to attack the host. Different parameters are used for - Windows XP (universal exploit) - Windows 2000 (universal exploit) - Windows 2000 Advanced Server (SP4 exploit) Other operating systems, such as Windows Me and NT are not infected by this worm. If the attack is successful a shell is started on port 9996. Through the shell port Sasser instructs the remote computer to download and execute the worm from the attacker computer using FTP. The FTP server listens on port 5554 on all infected computers with the purpose of serving out the worm for other hosts that are being infected. Transactions through the FTP server are logged to 'C:\win.log'. Summary of TCP ports used by the worm: 445/TCP: - The worm attacks through this port 5554/TCP: - FTP server on infected systems 9996/TCP: - Remote shell opened by the exploit on the vulnerable hosts The Vulnerability This vulnerability is caused by a buffer overrun in the Local Security Authority Subsystem Service of Windows NT-based systems. Detailed information on the vulnerability and the available fixes are at http://www.microsoft.com/technet/security/bulletin/MS04-011.mspx