Bkdr_hupigon.oth


 
Thread Tools Search this Thread
Special Forums Cybersecurity Malware Advisories (RSS) Bkdr_hupigon.oth
# 1  
Old 12-30-2007
Bkdr_hupigon.oth

This backdoor may be dropped by other malware. It may be downloaded unknowingly by a user when visiting malicious Web sites.
It drops a copy of itself.
It registers itself as a system service to ensure its automatic execution at every system startup. It does this by creating a registry entry.
This backdoor opens random ports. It listens for a connection from another remote system. Once connected, it enables a remote malicious user to issue commands on the affected system. These commands include hooking keyboard inputs, downloading further malicious files, launching denial of service (DoS) attacks, executing files, and stealing system information. As a result, system security may be compromised.


More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
sprayd(1M)																sprayd(1M)

NAME
rpc.sprayd, sprayd - spray server SYNOPSIS
log_file] DESCRIPTION
is an RPC server that records the packets sent by from another system (see spray(1M)). daemon may be started by or through the command line. The service provided by is not useful as a networking benchmark as it uses unreli- able connectionless transports, UDP, for example. It can report a large number of packets dropped when the drops were caused by the pro- gram sending packets faster than they can be buffered locally, that is, before the packets get to the network medium. Options recognizes the following options and command-line arguments: Log any errors to the named log file, log_file. Errors are not logged if the option is not specified. Information logged to the file includes date and time of the error, host name, process id and name of the function gen- erating the error, and the error message. Note that different services can share a single log file since enough infor- mation is included to uniquely identify each error. Exit after serving each RPC request. Using the option, the security file can control access to RPC services. Exit only if o dies (see rpcbind(1M)), o Another registers with or o becomes unregistered with The option is more efficient because a new process is not launched for each RPC request. is the default. AUTHOR
was developed by Sun Microsystems, Inc. SEE ALSO
inetd(1M), rpcbind(1M), spray(1M), inetd.conf(4), inetd.sec(4), services(4). sprayd(1M)