TCP/UDP Port Finder
Search results for "attacker"
Port: 9876/TCP
9876/TCP - Known port assignments (9 records found)
- ServiceDetailsSource
- sdSession DirectorIANA
- EMC2 (Legato) Networker or Sun Solcitice Backup (Official)WIKI
- threat[threat] Cyber AttackerBekkoame
- threat[threat] LolokBekkoame
- threat[threat] RuxBekkoame
- threat[threat] A Norton Commander lookalike for UNIX. The client portion can browse files on the hard disk, in tar files, and across the network with this server component. This protocol is Sun RPC based and registers with portmapper.Bekkoame
- cyberattacker[trojan] Cyber AttackerSANS
- rux[trojan] RuxSANS
- trojan[trojan] Rux. Remote Access / Downloading trojan / FTP server. Works on Windows 95, 98 and NT. Aliases: RNS ToolsSimovits
Port: 10008/TCP
10008/TCP - Known port assignments (7 records found)
- ServiceDetailsSource
- octopusOctopus MultiplexerIANA
- Octopus Multiplexer, primary port for the CROMP protocol, which provides a platform-independent means for communication of objects across a network (Unofficial)WIKI
- threat[threat] cheese worm In early year 2001, many exploit scripts for DNS TSIG name overflow would place a root shell on this port. In mid-2001, a worm was created that enters the system via this port (left behind by some other attacker), then starts scanning other machines from this port.Bekkoame
- cheeseworm[trojan] Cheese wormSANS
- lion[trojan] LionSANS
- lionworm[trojan] Lion Worm (exploits Solaris saadmind)SANS
- trojan[trojan] li0n. Worm / Steals passwords / Rootkit dropper / Hacking tool / Distributed DoS tool. Works on Unix (Linux), together with BIND 8.2. Aliases: The Lion worm, Linux/Lion, 1i0n, LionSimovits
Port: 10008/UDP
10008/UDP - Known port assignments (3 records found)
- ServiceDetailsSource
- octopusOctopus MultiplexerIANA
- Octopus Multiplexer, primary port for the CROMP protocol, which provides a platform-independent means for communication of objects across a network (Unofficial)WIKI
- threat[threat] cheese worm In early year 2001, many exploit scripts for DNS TSIG name overflow would place a root shell on this port. In mid-2001, a worm was created that enters the system via this port (left behind by some other attacker), then starts scanning other machines from this port.Bekkoame
Port: 32771/TCP
32771/TCP - Known port assignments (3 records found)
- ServiceDetailsSource
- filenet-rmiFileNET RMIIANA
- sometimes-rpc5Sometimes an RPC port on my Solaris box (rusersd)SANS
- threat[threat] Ghost Portmapper. Some SunOS machines listen at this port for portmapper. Since firewalls frequently don't filter at high ports, it can allow the attacker access to portmapper even when port 111 is blocked.Bekkoame
Port: 32771/UDP
32771/UDP - Known port assignments (4 records found)
- ServiceDetailsSource
- filenet-rmiFileNet RMIIANA
- filenet-rmiFileNET RMIBekkoame
- sometimes-rpc6Sometimes an RPC port on my Solaris box (rusersd)SANS
- threat[threat] Ghost Portmapper. Some SunOS machines listen at this port for portmapper. Since firewalls frequently don't filter at high ports, it can allow the attacker access to portmapper even when port 111 is blocked.Bekkoame
About TCP/UDP ports
TCP port 9876 uses the Transmission Control Protocol. TCP is one of the main protocols in TCP/IP networks. TCP is a connection-oriented protocol, it requires handshaking to set up end-to-end communications. Only when a connection is set up user's data can be sent bi-directionally over the connection.
Attention! TCP guarantees delivery of data packets on port 9876 in the same order in which they were sent. Guaranteed communication over TCP port 9876 is the main difference between TCP and UDP. UDP port 9876 would not have guaranteed communication as TCP.
UDP on port 9876 provides an unreliable service and datagrams may arrive duplicated, out of order, or missing without notice. UDP on port 9876 thinks that error checking and correction is not necessary or performed in the application, avoiding the overhead of such processing at the network interface level.
UDP (User Datagram Protocol) is a minimal message-oriented Transport Layer protocol (protocol is documented in IETF RFC 768).
Application examples that often use UDP: voice over IP (VoIP), streaming media and real-time multiplayer games. Many web applications use UDP, e.g. the Domain Name System (DNS), the Routing Information Protocol (RIP), the Dynamic Host Configuration Protocol (DHCP), the Simple Network Management Protocol (SNMP).
TCP vs UDP - TCP: reliable, ordered, heavyweight, streaming; UDP - unreliable, not ordered, lightweight, datagrams.
Attention! TCP guarantees delivery of data packets on port 9876 in the same order in which they were sent. Guaranteed communication over TCP port 9876 is the main difference between TCP and UDP. UDP port 9876 would not have guaranteed communication as TCP.
UDP on port 9876 provides an unreliable service and datagrams may arrive duplicated, out of order, or missing without notice. UDP on port 9876 thinks that error checking and correction is not necessary or performed in the application, avoiding the overhead of such processing at the network interface level.
UDP (User Datagram Protocol) is a minimal message-oriented Transport Layer protocol (protocol is documented in IETF RFC 768).
Application examples that often use UDP: voice over IP (VoIP), streaming media and real-time multiplayer games. Many web applications use UDP, e.g. the Domain Name System (DNS), the Routing Information Protocol (RIP), the Dynamic Host Configuration Protocol (DHCP), the Simple Network Management Protocol (SNMP).
TCP vs UDP - TCP: reliable, ordered, heavyweight, streaming; UDP - unreliable, not ordered, lightweight, datagrams.
Your IP address
3.138.200.66