Anti-hack

[paydot]

Attack detail : 4K scans
dateTime srcIp:srcPort dstIp:dstPort protocol flags bytes reason
2014.06.07 19:28:12 CEST 192.99.*.*:64070 190.39.133.34:8080 TCP SYN 52 SCAN:SYN
2014.06.07 19:28:12 CEST 192.99.*.*:64106 190.198.93.34:8080 TCP SYN 52 SCAN:SYN
2014.06.07 19:28:12 CEST 192.99.*.*:64549 190.79.43.43:8080 TCP SYN 52 SCAN:SYN
2014.06.07 19:28:12 CEST 192.99.*.*:64113 201.243.164.46:8080 TCP SYN 52 SCAN:SYN
2014.06.07 19:28:12 CEST 192.99.*.*:64424 186.93.25.55:8080 TCP SYN 52 SCAN:SYN
2014.06.07 19:28:12 CEST 192.99.*.*:64106 190.198.93.34:8080 TCP SYN 48 SCAN:SYN
2014.06.07 19:28:12 CEST 192.99.*.*:64070 190.39.133.34:8080 TCP SYN 48 SCAN:SYN
2014.06.07 19:28:12 CEST 192.99.*.*:64277 190.77.241.47:8080 TCP SYN 48 SCAN:SYN
2014.06.07 19:28:12 CEST 192.99.*.*:64710 201.211.137.239:8080 TCP SYN 52 SCAN:SYN
2014.06.07 19:28:12 CEST 192.99.*.*:64964 186.91.63.225:8080 TCP SYN 52 SCAN:SYN
2014.06.07 19:28:12 CEST 192.99.*.*:65393 201.242.42.56:8080 TCP SYN 52 SCAN:SYN
2014.06.07 19:28:12 CEST 192.99.*.*:65186 200.8.69.233:8080 TCP SYN 52 SCAN:SYN
2014.06.07 19:28:12 CEST 192.99.*.*:65407 186.94.88.141:8080 TCP SYN 52 SCAN:SYN
2014.06.07 19:28:12 CEST 192.99.*.*:64855 186.93.16.226:8080 TCP SYN 48 SCAN:SYN
2014.06.07 19:28:12 CEST 192.99.*.*:65343 190.204.101.55:8080 TCP SYN 52 SCAN:SYN
2014.06.07 19:28:12 CEST 192.99.*.*:65102 190.206.243.225:8080 TCP SYN 48 SCAN:SYN
2014.06.07 19:28:12 CEST 192.99.*.*:65307 41.46.208.53:8080 TCP SYN 52 SCAN:SYN
2014.06.07 19:28:12 CEST 192.99.*.*:65407 186.94.88.141:8080 TCP SYN 48 SCAN:SYN
2014.06.07 19:28:12 CEST 192.99.*.*:63861 190.37.238.39:8080 TCP SYN 52 SCAN:SYN
2014.06.07 19:28:12 CEST 192.99.*.*:63866 190.77.178.43:8080 TCP SYN 52 SCAN:SYN

I would like to ask these ports are ZP port, or my computer was hacked,thanks

 

[rostonix]

Is it hetzner's report?

 

[paydot]

this is [email protected] report
Dear Customer,

We have detected unusual activity on your server ks4010484.ip-192-99-9.net.

Please do not hesitate to contact our technical support so that this
situation does not become critical.

You can find the logs brought up by our system below which led to this alert.

- START OF ADDITIONAL INFORMATION -

Attack detail : 4K scans
dateTime srcIp:srcPort dstIp:dstPort protocol flags bytes reason
2014.06.06 23:23:10 CEST 192.99.*.*:58187 201.248.20.126:8080 TCP SYN 52 SCAN:SYN
2014.06.06 23:23:10 CEST 192.99.*.*:58188 186.91.159.85:8080 TCP SYN 52 SCAN:SYN
2014.06.06 23:23:10 CEST 192.99.*.*:57216 203.171.221.246:8080 TCP SYN 48 SCAN:SYN
2014.06.06 23:23:10 CEST 192.99.*.*:58184 201.242.106.86:8080 TCP SYN 52 SCAN:SYN
2014.06.06 23:23:10 CEST 192.99.*.*:58185 186.91.172.126:8080 TCP SYN 52 SCAN:SYN
2014.06.06 23:23:10 CEST 192.99.*.*:58186 190.74.210.85:8080 TCP SYN 52 SCAN:SYN
2014.06.06 23:23:10 CEST 192.99.*.*:58194 190.73.108.124:8080 TCP SYN 52 SCAN:SYN
2014.06.06 23:23:10 CEST 192.99.*.*:58197 190.205.239.96:8080 TCP SYN 52 SCAN:SYN
2014.06.06 23:23:10 CEST 192.99.*.*:58195 190.37.105.137:8080 TCP SYN 52 SCAN:SYN
2014.06.06 23:23:10 CEST 192.99.*.*:58196 200.8.2.124:8080 TCP SYN 52 SCAN:SYN
2014.06.06 23:23:10 CEST 192.99.*.*:58190 186.95.32.125:8080 TCP SYN 52 SCAN:SYN
2014.06.06 23:23:10 CEST 192.99.*.*:58192 201.210.235.124:8080 TCP SYN 52 SCAN:SYN
2014.06.06 23:23:10 CEST 192.99.*.*:58199 190.198.35.107:8080 TCP SYN 52 SCAN:SYN
2014.06.06 23:23:10 CEST 192.99.*.*:58206 190.207.0.200:8080 TCP SYN 52 SCAN:SYN
2014.06.06 23:23:10 CEST 192.99.*.*:58203 190.78.42.197:8080 TCP SYN 52 SCAN:SYN
2014.06.06 23:23:10 CEST 192.99.*.*:58207 186.92.97.197:8080 TCP SYN 52 SCAN:SYN
2014.06.06 23:23:10 CEST 192.99.*.*:58208 186.88.130.197:8080 TCP SYN 52 SCAN:SYN
2014.06.06 23:23:10 CEST 192.99.*.*:58209 186.93.131.197:8080 TCP SYN 52 SCAN:SYN
2014.06.06 23:23:10 CEST 192.99.*.*:58211 190.72.140.197:8080 TCP SYN 52 SCAN:SYN
2014.06.06 23:23:10 CEST 192.99.*.*:58200 186.95.20.137:8080 TCP SYN 52 SCAN:SYN



- END OF ADDITIONAL INFORMATION -

Kind regards,

OVH Customer Support
Regards,

Support OVH
Phone: 1-855-OVH-LINE (684-5463)
Email: [email protected]

 

[rostonix]

That's seems like usual thing when it comes to proxychecking with many threads.