FakeCloudAV2012
SummaryUpdated: January 13, 2012 2:23:05 AMType: Misleading ApplicationName: CloudAV2102Risk Impact: MediumSystems Affected: Windows 98, Windows 95, Windows XP, Windows Me, Windows Vista, Windows NT, Windows Server 2003, Windows 2000BehaviorFakeCloudAV2012 is a misleading application that may give exaggerated reports of threats on the computer.
Antivirus Protection Dates- Initial Rapid Release version December 12, 2011 revision 009
- Latest Rapid Release version January 16, 2012 revision 004
- Initial Daily Certified version December 12, 2011 revision 018
- Latest Daily Certified version January 16, 2012 revision 016
- Initial Weekly Certified release date December 14, 2011
Technical DetailsUpdated: January 13, 2012 2:23:05 AMType: Misleading ApplicationName: CloudAV2102Risk Impact: MediumSystems Affected: Windows 98, Windows 95, Windows XP, Windows Me, Windows Vista, Windows NT, Windows Server 2003, Windows 2000Behavior The program reports false or exaggerated system security threats on the computer. The user is then prompted to pay for a full license of the application in order to remove the threats. Installation When the program is executed, it creates the following files: - %UserProfile%\Local Settings\Application Data\[THREE RANDOM LETTERS].exe
- %UserProfile%\Local Settings\Application Data\2e01oq0m46k223
- %UserProfile%\Local Settings\Temp\[RANDOM FILE NAME]
- %UserProfile%\Templates\[RANDOM FILE NAME]
Next, it creates the following registry entries: - HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\SharedAccess\Parameters\FirewallPolicy\DomainProfile\"EnableFirewall" = "0"
- HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\SharedAccess\Parameters\FirewallPolicy\DomainProfile\"DoNotAllowExceptions" = "0"
- HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\SharedAccess\Parameters\FirewallPolicy\DomainProfile\"DisableNotifications" = "1"
- HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\SharedAccess\Parameters\FirewallPolicy\StandardProfile\"EnableFirewall" = "0"
- HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\SharedAccess\Parameters\FirewallPolicy\StandardProfile\"DoNotAllowExceptions" = "0"
- HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\SharedAccess\Parameters\FirewallPolicy\StandardProfile\"DisableNotifications" = "1"
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\DomainProfile\"EnableFirewall" = "0"
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\DomainProfile\"DoNotAllowExceptions" = "0"
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\DomainProfile\"DisableNotifications" = "1"
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\StandardProfile\"EnableFirewall" = "0"
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\StandardProfile\"DoNotAllowExceptions" = "0"
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\StandardProfile\"DisableNotifications" = "1"
It then modifies the following registry entries: - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Security Center\"AntiVirusDisableNotify" = "0"
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Security Center\"FirewallDisableNotify" = "0"
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Security Center\"UpdatesDisableNotify" = "0"
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Security Center\"AntiVirusOverride" = "0"
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Security Center\"FirewallOverride" = "0"
The program then deletes the following registry subkeys: - HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_WUAUSERV
- HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\wuauserv
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_WUAUSERV
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wuauserv
RemovalUpdated: January 13, 2012 2:23:05 AMType: Misleading ApplicationName: CloudAV2102Risk Impact: MediumSystems Affected: Windows 98, Windows 95, Windows XP, Windows Me, Windows Vista, Windows NT, Windows Server 2003, Windows 2000You may have arrived at this page either because you have been alerted by your Symantec product about this risk, or you are concerned that your computer has been affected by this risk. Before proceeding further we recommend that you run a full system scan. If that does not resolve the problem you can try one of the options available below. FOR NORTON USERS If you are a Norton product user, we recommend you try the following resources to remove this risk. Removal Tool If you have an infected Windows system file, you may need to replace them using from the Windows installation CD. How to reduce the risk of infection The following resources provide further information and best practices to help reduce the risk of infection. FOR BUSINESS USERSIf you are a Symantec business product user, we recommend you try the following resources to remove this risk. Identifying and submitting suspect filesSubmitting suspicious files to Symantec allows us to ensure that our protection capabilities keep up with the ever-changing threat landscape. Submitted files are analyzed by Symantec Security Response and, where necessary, updated definitions are immediately distributed through LiveUpdateâ„¢ to all Symantec end points. This ensures that other computers nearby are protected from attack. The following resources may help in identifying suspicious files for submission to Symantec. Removal Tool If you have an infected Windows system file, you may need to replace them using from the Windows installation CD. How to reduce the risk of infectionThe following resource provides further information and best practices to help reduce the risk of infection. Protecting your business networkMANUAL REMOVALThe following instructions pertain to all current Symantec antivirus products. 1. Performing a full system scanHow to run a full system scan using your Symantec product2. Restoring settings in the registryMany risks make modifications to the registry, which could impact the functionality or performance of the compromised computer. While many of these modifications can be restored through various Windows components, it may be necessary to edit the registry. See in the Technical Details of this writeup for information about which registry keys were created or modified. Delete registry subkeys and entries created by the risk and return all modified registry entries to their previous values. |
|




 |
|
|
|