- COOCOO2015-06-27金牌会员13774
原因是其中一个网站转向到某个钓鱼链接,估计是被黑了,第一次遇到这样的安全问题根本不知道怎么搞,无从下手啊,这里有人有这方面的经验吗,希望能指导一下。
然后停了网络:
At this time we have filtered your Linode's network connection and you will no longer be able to connect via SSH. In order to connect to your Linode and investigate this issue you will need to use LISH following the guide at https://www.linode.com/docs/networking/using-the-linode-shell-lish.
Please update this ticket as soon as possible to regain normal connectivity.
应该是要求这么做:
We have received a report regarding a phishing website that is hosted on your Linode. The page appears to be an attempt to solicit sensitive account information from users. We ask that you investigate this matter as soon as you are able. Once you have completed your investigation, kindly reply to this ticket with the answers to the following questions:
- What was the source of the issue?
- What steps did you take to resolve this issue?
- What steps did you take to prevent this from occurring again?
We take reports of phishing activity extremely seriously, as phishing has the potential to cause real harm to others. If we do not hear from you within 4 hours about this issue, your Linode will be powered down to stop further phishing content from spreading.
I think my Linode is compromised. How can I tell?
If you believe that your Linode has been compromised, you can start troubleshooting by auditing the following log files and writable directories:
- /var/log/auth.log : Check this log file for signs of unauthorized access and brute-force attempts. Use the ‘last’ command to cross reference recent account logins with this file.
- /tmp : This directory is often used by malicious parties to store files
- Web server logs: There may be a vulnerable script or web application. The location of these log files depends on your web server (apache, nginx, etc.) configuration.
- ps aux : Use this command to audit running processes for foreign processes
My Linode is compromised. What do I do now?
If you discover that your Linode is compromised, we strongly suggest that you redeploy. It is often very difficult to determine the full scope of a vulnerable system. We have a guide that can assist you with redeploying your server that you can find linked below:
https://www.linode.com/docs/security/recovering-from-a-system-compromise/
During this process, please continue to keep us updated, and let us know if you have any questions.