Trojan.Packed.NsAnti

ドキュメントを印刷する

発見日: May 30, 2007
更新日: May 31, 2007 7:57:22 AM
別名: Bloodhound.NsAnti [Symantec]
種別: Trojan
影響を受けるシステム: Windows

Trojan.Packed.NsAnti は、アンチウイルスソフトウェアからファイルを隠すために、難読化または暗号化されている可能性があるファイルに対する、ヒューリスティック手法による検出名です。

2007 年 5 月 30 日以前の定義では、この脅威を Bloodhound.NsAnti として検出する場合があります。

ウイルス対策日

  • Rapid Release 初回バージョン May 30, 2007
  • Rapid Release 最新バージョン July 20, 2018 リビジョン 016
  • Daily Certified 初回バージョン May 31, 2007 リビジョン 002
  • Daily Certified 最新バージョン July 20, 2018 リビジョン 002
  • Weekly Certified 初回リリース日 May 30, 2007

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

発見日: May 30, 2007
更新日: May 31, 2007 7:57:22 AM
別名: Bloodhound.NsAnti [Symantec]
種別: Trojan
影響を受けるシステム: Windows

パッカーは、Windows PE ファイルを圧縮、暗号化、または難読化するツールです。マルウェアの作成者は、アンチウイルスソフトウェアによる検出から脅威を隠すために、しばしばパッカーを使います。Trojan.Packed.NsAnti は、正規の目的のために使用されることが知られていないパッカーを検出します。

Trojan.Packed.NsAnti として検出されたファイルは、有害である可能性があります。お使いのコンピュータ上で Trojan.Packed.NsAnti として検出されるファイルを発見した場合、そのファイルを Symantec Security Response へ提出してください。スキャンと配信機能を使用してファイルを提出する方法については、「スキャンと配信ウィザードを使用して Symantec Security Response に疑わしいファイルを提出する方法 」をご覧ください。

推奨する感染予防策

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.