We run an automated system that monitors malicious and unwanted traffic, including traffic generated by network port or network scanning, TCP floods, etc. (outgoing network attacks). If such traffic is detected, a ticket with the details is created in the customer's client area and network access to the VDS is blocked.
Why was my server blocked?
We block such a server to keep the network stable and to protect the owners of the affected servers. For example, by blocking the server we prevent unnecessary parasitic traffic. Moreover, there is a risk that a compromised server will be used for illegal activities, which may lead to compensation claims. Blocking the server helps protect our customers from such threats. To help you analyze the reasons for the block, a log file with detailed information is included in the notification email.
There are three different types of logs:
Port information / Netscan
################################################################### # Netscan detected from host x.x.x.x # ################################################################### time src_ip dest_ip:dest_port ------------------------------------------------------------------- Thu Nov 13 18:14:27 2008: x.x.x.x => 65.98.236.0: 22 Thu Nov 13 18:14:27 2008: x.x.x.x => 65.98.236.1: 22 Thu Nov 13 18:14:27 2008: x.x.x.x => 65.98.236.2: 22 Thu Nov 13 18:14:27 2008: x.x.x.x => 65.98.236.3: 22 .....
This log shows only outgoing connections. It lists the destination IP addresses or the ports used on the destination IP addresses. This will help you find the problem easily.
Packet threshold summary report.
Direction OUT Internal x.x.x.x Sum 62.790 packets/s , 14 MBit/s External 125.162.12.67, 62.770 packets/s , 13 MBit/s External 72.14.220.136, 3 packets/s , 0 MBit/s External 66.249.72.235 3 packets/s , 0 MBit/s
This log does not list every connection, but it contains a traffic report for each IP address. It shows the traffic that occurred, the number of connections and the total rate. This reveals the target of the attack and helps you figure out which application may have been involved. In this case, too, you see only outgoing connections.
Detailed traffic statistics
21:44:53.145756 IP x.x.x.x.55008 > 76.9.23.182.29615: UDP, length 9216 21:44:53.145883 IP x.x.x.x.55030 > 76.9.23.182.45527: UDP, length 9216 21:44:53.146007 IP x.x.x.x.55046 > 76.9.23.182.1826: UDP, length 9216 21:44:53.146126 IP x.x.x.x.55064 > 76.9.23.182.34940: UDP, length 9216 21:44:53.146249 IP x.x.x.x.55080 > 76.9.23.182.20559: UDP, length 9216 21:44:53.146371 IP x.x.x.x.55093 > 76.9.23.182.31488: UDP, length 9216 21:44:53.146493 IP x.x.x.x.55112 > 76.9.23.182.56406: UDP, length 9216 21:44:53.146616 IP x.x.x.x.55132 > 76.9.23.182.43714: UDP, length 9216 21:44:53.146741 IP x.x.x.x.55147 > 76.9.23.182.64613: UDP, length 9216
This log shows detailed traffic statistics for incoming and outgoing connections. Here you can see the following information: destination IP address and port, packet size and type. Statistics for every single packet would be a huge amount of information, so only a small portion of the traffic is shown. This data will help you recognize patterns and use them for further analysis.
When will my server be back online?
First, the problem has to be fixed. Your server will be back online only after the problem has been resolved. You must provide us with an explanation describing how you fixed the problem and what you have done to make sure it does not happen again.
These measures are taken in the following cases:
- An attack was launched from the server
- Network scanning was performed from the server
- Other abuse
To eliminate the cause of the block, you will be given access to the VNC console of the VDS. We can unblock the server only if you are absolutely sure that the problem has been fixed. Otherwise the server may continue, for example, the attack, and we will have to block it again.
If we regularly detect such activity from your server or receive complaints, we will have to terminate our service to you without a refund!
I did not run any scans and do not know what this is. What should I do?
This means your server has been hacked (compromised) or infected with some kind of malware. As the server administrator, you are responsible for any possible consequences. We strongly recommend that you:
- Install all available security updates regularly
- Keep track of discovered vulnerabilities in the software used on the server and update it promptly
- Do not use simple (insecure) passwords or the same password in different places
- Do not visit any websites in a browser on the server, except trusted ones
- Do not download or run any potentially dangerous programs from dubious sources on the server
- Do not give anyone access to the server without a good reason
- If you still have to visit third-party websites or download files on the server, use antivirus protection with regular updates
- Read the full list of security recommendations
Once the source of the problem has been found, the question is what to do next. The safest option is to reinstall the operating system. Continuing to use a compromised system is very dangerous: you can never be completely sure there is no malware left on the server. Reinstalling the OS only makes sense once you have found the exact cause of the block. Otherwise the reinstall is pointless, since the system can be compromised again through the same hole. After reinstalling the OS, you can restore your data from your backups. Please be careful: malware may also be present in your backups.
- 133 Users Found This Useful