iFrame Injection Attack Followed us to New Server

人盡茶涼 提交于 2019-12-03 08:50:38

Check it...the miscreant author of the program that jacked up your server is known as "Left4Dead" -- his iframe injection doo-hicky is called "BlackLeech." You can find this gent and his advert on Damagelab .org (CRIMINAL FORUM!!).

Every time root logs in, the malware ceases all activity, or if you SSH into your server. It also monitors system monitoring tools :|

Screen shot of Damagelab .org advert:

http://imgur.com/NRQQl

Text of malware advert by the author:

http://pastebin.com/u7AcYSNi

notice how your thread is listed as a reference :))

if you need help with translation, hit me up!

I would roughly classify the source of initial infection in two groups: (1) your site was compromised using some vulnerability (if you're using an open source engine like Wordpress or Joomla you should check the current vulnerabilities, you can start with exploit-db.com) (2) your site's CMS was accessed using weak credentials (as it is already noted in the comments to your question)

Reappearing of the code indicates, that the source of infection is still there. Usually it is a PHP script, that receives a string as an argument (likely encoded in base64 or otherwise), decodes and executes it using eval. I guess you did not change the domain name, so the bad guy have some script on his machine that regularly requests his "backdor" and re-infects your system.

How do you find this script? Your options:

  • See the access log. Look for suspicious strings like something.php?e=asSdfdSsafas== or POST request to the the script that is not part of your site.

  • Scan all the files using string search, look for "eval($_POST['" or "eval($_GET['" or just "eval" and then find the files that are not likely to be the part of your site engine.

Hope this will help Bests

JLight

A few days ago I had an incident with some banners populating a site I manage. Finally I could get rid of it. You can check the full answer here.

The problem was that a javascript code was being appended to textareas. Probably, the browser was infected and appending the undesired extra code that caused the iframe load.

Your situation is different, but maybe it can help: if you are using a WYSIWYG editor to handle your content in the backend, or someone else is doing that, there is a chance that the iframe is being created by a javascript appended to textareas or inputs.

A different approach. Hope it helps!

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!