Port 1029 Details
known port assignments and vulnerabilities
threat/application/port search:
Port(s) |
Protocol |
Service |
Details |
Source |
1025-1029 |
tcp,udp |
nfc-iis |
Ports > 1024 are designated for dynamic allocation by Windows. When programs ask for the "next available" socket, they usually get sequential ports starting at 1025.
Ports 1026-1027/udp were historically used for Windows Messenger popup spam |
SG
|
1029 |
tcp |
dcom |
Microsoft DCOM services often uses ports 1026/tcp and 1029/tcp
Trojans that use this port: InCommand (TCP/UDP)
Email-Worm.Win32.Kipis.a / Unauthenticated Remote Code Execution - the malware listens on TCP port 1029 and writes incoming packets to an executable file that is renamed as "winlogins.exe". Third-party attackers who can reach the infected host can use socket utils like netcat to transfer files which get stored in the Windows\SysWOW64 dir, this may result in remote code execution.
References: [MVID-2021-0250]
Backdoor.IRC.Subhuman / Unauthenticated Open Proxy - the malware listens on TCP port 1029. Third-party attackers who can connect to the infected system can relay requests from the original connection to the destination and then back to the origination system. Attackers may then be able to launch attacks, download files or port scan third party systems and it will appear as the attacks originated from that infected host.
References: [MVID-2021-0418] |
SG
|
1029 |
tcp |
|
Often utilized by Microsoft DCOM services (unofficial) |
Wikipedia
|
1029 |
tcp |
trojan |
Clandestine, KWM, Litmus, SubSARI |
Trojans
|
1029 |
udp |
trojan |
SubSARI |
Trojans
|
1029 |
tcp |
ms-lsa |
ms-lsa |
Nmap
|
1029 |
tcp |
ICQNuke98 |
[trojan] ICQ Nuke 98 |
Neophasis
|
1029 |
tcp |
InCommand |
[trojan] InCommand |
Neophasis
|
1029 |
tcp,udp |
threat |
W32.Kipis |
Bekkoame
|
1029 |
tcp,udp |
threat |
W32.Kobot |
Bekkoame
|
1029 |
tcp,udp |
solid-mux |
Solid Mux Server, registered 2004-11 |
IANA
|
|
11 records found
Related ports: 1026
|