Troj_agent.nmb


 
Thread Tools Search this Thread
Special Forums Cybersecurity Malware Advisories (RSS) Troj_agent.nmb
# 1  
Old 04-09-2008
Troj_agent.nmb

This Trojan may be downloaded from remote sites by the following malware, specifically TROJ_AGENT.LJY. It may also be downloaded from a certain remote site.
Upon execution, this Trojan drops a component file, which Trend Micro detects as TROJ_ROOTKIT.EZ.
This Trojan drops a batch file to delete itself after execution. The said batch file also deletes itself after deleting the malware file.
However, due to some errors in its code, this Trojan could not perform its malicious routine properly.


More...
Login or Register to Ask a Question

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Smb & nmb not starting at boot - CentOS7

I would like the smb and nmb to start on boot. In the terminal (as root) I did: /sbin/chkconfig smb --addor chkconfig --add sambaor chkconfig --add /sbin/smbdresault is message like below : error reading information on service smb: No such file or directory Please use CODE tags as... (2 Replies)
Discussion started by: momed131
2 Replies
Login or Register to Ask a Question
USERFILE(5)							File Formats Manual						       USERFILE(5)

Name
       USERFILE - defines uucp security

Syntax
       /usr/lib/uucp/USERFILE

Description
       The  utility  uses the USERFILE to establish what access a remote system can have to the local system.  An entry should exist for each sys-
       tem.  If no entries exist for a particular system, the default entries are used.  The entries for particular  systems  have  the  following
       format:

       login-name , node-name X # path-name

       login-name
		 The name with which the remote system logs in.

       node-name The name of the remote node.

       X#	 The  execution  level	for  the remote system.  The remote system can execute commands defined in the file that have an execution
		 level less than or equal to the number #.

       path-name The remote system can access anything at the local system with this prefix.

       Two entries must also be provided for systems not otherwise listed:

	    remote, X# path-name ...
	    local, X# path-name ...

       These entries define the execution level and access pathnames for the local system and all remote systems not defined by specific entries.

Examples
       remote, X1 /usr/spool/uucppublic
       local, X9 /
       max,systemY /usr/sources /usr/src/share
       max,systemZ X3 /usr
       In the above example, the node named systemY with the login name max has access to anything with the pathname prefixes and The  node  named
       systemZ	with  the  login  name max can execute commands defined in with an execution level of 3 or lower.  It can access anything with the
       pathname prefix

       Any other remote systems can execute commands defined in with an execution level of 1 or 0.  They can access  anything  with  the  pathname
       prefix of

       Users on the local system can execute any of the commands defined in and access anything on the system.

See Also
       Guide to the uucp Utility

																       USERFILE(5)