ACTS.LFM.926

Printer Friendly Page

Discovered: January 08, 2002
Updated: February 13, 2007 11:58:51 AM
Also Known As: SWF.LFM.926
Type: Virus


ACTS.LFM.926 is a virus that is capable of infecting Shockwave Flash (.swf) files. The virus uses the ActionScript scripting language (which is supported by Shockwave Flash) to create a DOS executable named V.COM in the same folder as the one from which the already infected Flash movie is being executed. This file is then executed by the virus, and it infects other Shockwave Flash files that are in the same folder.

NOTE: Definitions dated prior to January 9, 2002 may detect this virus as SWF.LFM.926.



If you are an Enterprise customer, you can add the .swf extension to the default file scanning list.

Antivirus Protection Dates

  • Initial Rapid Release version January 09, 2002
  • Latest Rapid Release version September 28, 2010 revision 054
  • Initial Daily Certified version January 09, 2002
  • Latest Daily Certified version September 28, 2010 revision 036

Click here for a more detailed description of Rapid Release and Daily Certified virus definitions.

Writeup By: Neal Hindocha

Discovered: January 08, 2002
Updated: February 13, 2007 11:58:51 AM
Also Known As: SWF.LFM.926
Type: Virus


ACTS.LFM.926 is a 926-byte virus that infects Shockwave Flash (.swf) files.

The infection routine is a very simple FindFirst/FindNext loop. The infection routine stops if no .swf files are found or if it encounters a file that is marked read-only.

Recommendations

Symantec Security Response encourages all users and administrators to adhere to the following basic security "best practices":

  • Use a firewall to block all incoming connections from the Internet to services that should not be publicly available. By default, you should deny all incoming connections and only allow services you explicitly want to offer to the outside world.
  • Enforce a password policy. Complex passwords make it difficult to crack password files on compromised computers. This helps to prevent or limit damage when a computer is compromised.
  • Ensure that programs and users of the computer use the lowest level of privileges necessary to complete a task. When prompted for a root or UAC password, ensure that the program asking for administration-level access is a legitimate application.
  • Disable AutoPlay to prevent the automatic launching of executable files on network and removable drives, and disconnect the drives when not required. If write access is not required, enable read-only mode if the option is available.
  • Turn off file sharing if not needed. If file sharing is required, use ACLs and password protection to limit access. Disable anonymous access to shared folders. Grant access only to user accounts with strong passwords to folders that must be shared.
  • Turn off and remove unnecessary services. By default, many operating systems install auxiliary services that are not critical. These services are avenues of attack. If they are removed, threats have less avenues of attack.
  • If a threat exploits one or more network services, disable, or block access to, those services until a patch is applied.
  • Always keep your patch levels up-to-date, especially on computers that host public services and are accessible through the firewall, such as HTTP, FTP, mail, and DNS services.
  • Configure your email server to block or remove email that contains file attachments that are commonly used to spread threats, such as .vbs, .bat, .exe, .pif and .scr files.
  • Isolate compromised computers quickly to prevent threats from spreading further. Perform a forensic analysis and restore the computers using trusted media.
  • Train employees not to open attachments unless they are expecting them. Also, do not execute software that is downloaded from the Internet unless it has been scanned for viruses. Simply visiting a compromised Web site can cause infection if certain browser vulnerabilities are not patched.
  • If Bluetooth is not required for mobile devices, it should be turned off. If you require its use, ensure that the device's visibility is set to "Hidden" so that it cannot be scanned by other Bluetooth devices. If device pairing must be used, ensure that all devices are set to "Unauthorized", requiring authorization for each connection request. Do not accept applications that are unsigned or sent from unknown sources.
  • For further information on the terms used in this document, please refer to the Security Response glossary.

Writeup By: Neal Hindocha

Discovered: January 08, 2002
Updated: February 13, 2007 11:58:51 AM
Also Known As: SWF.LFM.926
Type: Virus


NOTE: Virus definitions that can detect and remove ACTS.LFM.926 will be included in LiveUpdate on January 9, 2002. The instructions that follow assume that you are performing this removal on or after the date that these definitions have been released via LiveUpdate. In some cases, virus writeups are published before the actual definitions are released to the public.

If you suspect that the computer is infected with ACTS.LFM.926, but it has not been detected by Norton AntiVirus, submit the suspect file or files to Symantec using Scan and Deliver. See the document How to submit a file to Symantec Security Response using Scan and Deliver . If Symantec Security Response determines that the file is infected by a threat for which definitions have not yet been released, you may receive by return email a file which contains "Beta" definitions for the threat. Detach and execute the file to install the updated definitions, and then continue with the instructions in this document.

  1. Run LiveUpdate to make sure that you have the most recent virus definitions.
  2. Start Norton AntiVirus (NAV), and make sure that NAV is configured to scan all files. For instructions on how to do this, read the document How to configure Norton AntiVirus to scan all files.
  3. Run a full system scan.
  4. Delete all files that are detected as ACTS.LFM.926. Deleted files will have to be replaced from a clean backup or reinstalled.


Writeup By: Neal Hindocha