Port Details - Port 1026

Aug 03 52 Aug 04 44 Aug 05 150 Aug 06 107 Aug 07 40 Aug 08 64 Aug 09 137 Aug 10 61 Aug 11 45 Aug 12 58 Aug 13 43 Aug 14 55 Aug 15 47 Aug 16 34 Aug 17 39 Aug 18 49 Aug 19 62 Aug 20 43 Aug 21 40 Aug 22 42 Aug 23 48 Aug 24 62 Aug 25 41 Aug 26 42 Aug 27 51 Aug 28 38 Aug 29 52 Aug 30 96 Aug 31 1,342 Sep 01 2,822 Sep 02 25 Aug 03 77 Aug 04 386 Aug 05 80 Aug 06 91 Aug 07 117 Aug 08 84 Aug 09 79 Aug 10 58 Aug 11 247 Aug 12 1,840 Aug 13 91 Aug 14 100 Aug 15 79 Aug 16 73 Aug 17 63 Aug 18 80 Aug 19 80 Aug 20 63 Aug 21 82 Aug 22 36 Aug 23 62 Aug 24 90 Aug 25 75 Aug 26 66 Aug 27 86 Aug 28 103 Aug 29 62 Aug 30 87 Aug 31 75 Sep 01 81 Sep 02 47
[show ascii data]
  • Start Date:
  • End Date:
  • Port:
  • Left Graph:
  • Right Graph:
  • Show Range:Yes No

Port Information

ProtocolServiceName
udpwin-rpcWindows RPC
[get complete service list]

User Comment

Submitted ByDate
Comment
alerter2009-10-04 18:45:22
  The vast majority of these probes on UDP 1026, post-MS-RPC-DCOM exploit ("MS Blaster"), are Windows Messaging Service using alternate ports (UDP 1025-1027) to transmit/blast WMS Desktop Pop-up SPAM. This is because several ISP-s have blocked and/or continue to block UDP 135 post-MS-Blaster. A few offensive and ongoing UDP 1026 WMS SPAMmer source IP-s are: 203.197.199.183 (VSNL-IN), 61.143.182.138 (CHINANET-GD), 200.210.170.10 (LACNIC-ARIN BR), 202.131.221.61 (EAGLE-CN), whose respective ISP-s have been entirely unresponsive and unreactive to ongoing net abuse complaints (check incidents logged with DeepSight Security Analyzer and DShield).
2009-10-04 18:45:22
I wonder if it is related to "new attack vectors for rpc vulnerabilities" http://www2.corest.com/common/showdoc.php?idx=393&;;idxseccion=10
Ken Hollis2004-01-30 19:53:56
UDP Port 1026 (And as AFAIK ports 1027, 1028 and 1029) are the ports for Windows Messenger Popup Spam. See: http://www.lurhq.com/popup_spam.html
Ken Hollis2003-12-23 21:09:04
Greetings and Salutations: Since this is UDP, the spammers forge the source IP address to some unsuspecting party. Do not trust the source address, the packets would have to be traced hop by hop to actually find the perpetrator. Ken
Add a comment

CVE Links

CVE #Description