Surge in portscanning for tcp/32709
Since Saturday, my firewall logs show a tremendous surge (>1000x normal volume) in portscans for TCP port 32709. The scans all originate from Asia Pacific IP-ranges. If any reader has a suggestion as to what might be the cause of it, please drop me a line!
Traffic patterns looks like this:
60.0.228.175: 3526 -> 32709 [TCP]
60.0.228.175: 4459 -> 32709 [TCP]
60.0.228.175: 3435 -> 32709 [TCP]
60.0.228.175: 4871 -> 32709 [TCP]
60.0.228.175: 3667 -> 32709 [TCP]
60.0.228.175: 4459 -> 32709 [TCP]
60.0.228.175: 3603 -> 32709 [TCP]
60.0.228.175: 3435 -> 32709 [TCP]
60.0.228.175: 3721 -> 32709 [TCP]
60.0.228.175: 4459 -> 32709 [TCP]
60.0.228.175: 3721 -> 32709 [TCP]
60.0.228.175: 3667 -> 32709 [TCP]
60.0.228.175: 3526 -> 32709 [TCP]
60.0.228.175: 3435 -> 32709 [TCP]
60.0.228.175: 3526 -> 32709 [TCP]
60.0.228.175: 3603 -> 32709 [TCP]
60.0.228.175: 3667 -> 32709 [TCP]
60.0.228.175: 4871 -> 32709 [TCP]
60.0.228.175: 3603 -> 32709 [TCP]
The dshield port report also seems to depict an upwards trend in scans for this port.