9 ms·
New Linux userland rootkit with anti-debugging, new backdoors and pcap hiding
- TempleOSV2 13y agoNiggers fighting God. <Sigh> How's this gonna end, ya tink? God says... energy I_could_be_wrong not WooHoo poor husband baffling crash_and_burn how_could_you guppy youre_welcome charged I_veto_that employee hobnob sex what_have_you_done_for_me_lately wazz_up_with_that Ramsay astounding What_are_you_doing_dave basket_case slumin humongous pet I_didn't_see_that repeat_after_me
- Cacti 13y agoI don't even want to click on this.
- esac 13y agoit's a wiki
- Cacti 13y agowas a joke
- IsTom 13y agoIt's a wiki with a link to github repo. You need to compile it first.
- Cacti 13y agowas a joke
- pavs 13y agoI might be wrong, but I don't think there exists and flyby worm/virus/rootkit for Linux where clicking a link will automatically get you infected, without any user input.
- zurn 13y agoThey're about as easy to make as for Windows. It's just that Windows targeting is more profitable for mass malware, and the technical user base leads to shorter half life.
- ufmace 13y agoAny links/info on people making them? I was just looking for some, and didn't find any reports of such things in a few minutes of looking. Seems like the overall field is light, partly because there isn't any large company to pay out rewards for exploits, the huge variety of distros in the installed base, and the weak ecosystem as a result of the previous two. There probably are plenty of holes, but they might be only found by big-money efforts aimed at compromising particular computers, meaning essentially government spying.
- smtddr 13y agoNope. The major difference between your common Windows user and Linux user is that Windows users are often logged in as Administrator. So if arbitrary-code-execution happens that code owns the whole system - checkmate. The typical Linux user is not running their Windows Manager or browser as root. The worse that can happen is stuff to your home dir(which can be very bad too). Even this article title calling this a "userland rootkit" is kinda odd, since "/etc/ld.so.preload"(and the whole /etc dir) is a root-only writable. No matter how secure your OS is, if you're tricked into running an evil program as root/admin... it's game over. The usage-pattern for this happening on Windows is much, much higher than Linux since Windows users are already admin to start off with. Also, from my observation of Windows users over my 10+ year career, they always click "Ok" on every pop-up dialog box without even reading it. I think that UAC thing from Windows Vista enforced that behavior even more.
- nitrogen 13y agoThe nice thing about sudo is that it asks for a password, thereby mitigating the involuntary click OK reflex that affects Windows.
- esac 13y agosomeone from blackhatlibrary.net here?
- bha_mutiny 13y agoPing. edit: Just created this account to answer this question. Otherwise I'm only on HN to lurk.
- adamnemecek 13y agoThe site seems to be getting hammered by HN so here's the google cache http://webcache.googleusercontent.com/search?q=cache:8o5FkN6LOuYJ:blackhatlibrary.net/Azazel+&cd=1&hl=en&ct=clnk&gl=us http://webcache.googleusercontent.com/search?q=cache:8o5FkN6...
- e12e 13y agoAnd link to source on github: https://github.com/chokepoint/azazel https://github.com/chokepoint/azazel
- voltagex_ 13y ago> Running "make install" will inject the live kit into your system. While removal is not impossible, it's an unnecessary and painful procedure, not to mention you may forget to remove it. Why even have an install step for this? Actually, why does it exist?
- awestroke 13y agoYou're supposed to install it on a VM to study it, and then throw away the VM
- voltagex_ 13y agoI think I may do this at some stage.
- userbinator 13y agoInterestingly, there's a "removal" section in the article, with only the instructions to delete ld_preload.so. Was that meant as a joke?
- voltagex_ 13y ago>Azazel hooks ptrace() and returns -1, hence denying any debugging from occuring. The message displayed to the sysadmin is really more of a joke than anything and will definitely set off alarms that something is wrong. Okay, that's interesting - how would you remove this hook?
- girvo 13y agoLD_PRELOAD perhaps? I wonder if that would run last, rather than the rootkit?
- caf 13y agoUse statically-linked utilities compiled elsewhere.
- jet1 13y agoCan you explain in a more newbie friendly language? How do you detect this? Then how do you remove this? This type of high level tools becoming more mainstream as time passes. Today there is not much generic anti-tools for this or the upcoming ones!
- Tuna-Fish 13y agoFirstly, this is not some virus or worm that works it's way onto your machine. It's a payload that someone puts there possibly among other things. This means that if you have this on your machine, or if you have reason to think you have this on your machine, simple removal is not an acceptable solution. Whoever put the rootkit on the machine could have done almost anything else while he did it, and you are not guaranteed to find it all. If you find this on your machine, you need to produce a data-only backup of the machine, kill the partitions, and set it up again. As these rootkits are designed by rather smart people to overcome all existing tools, there simply cannot be generic tools that catch them all. If you get hit by a bunch of script kiddies using outdated tools, things like rkhunter and chkrootkit can help. Modern rootkits are almost by definition undetectable by them. If it's actually new, the way you find out about it is typically either a separate NID box between the machine and the wall that alerts, or the behaviour of the box changing.
- doomwad 13y agoWhat are some applications for this?
- yoha 13y agoSecurity research, malware analysis, etc
- slashdotaccount 13y agoKeeping a hacked server pwned?
- hiphopyo 13y agoWill this work on OpenBSD?
- 4ad 13y agoNo?
- weland 13y agoNo, this is very much Linux-only.
- hiphopyo 13y agoBut in theory could something similar have been developed for OpenBSD?
- kryptiskt 13y agoThere is even a book about designing FreeBSD rootkits: http://www.amazon.com/Designing-BSD-Rootkits-Introduction-Hacking-ebook/dp/B002MZAR6I/ http://www.amazon.com/Designing-BSD-Rootkits-Introduction-Ha...
- marios 13y agoOpenBSD does not have loadable kernel modules, so the techniques described for FreeBSD most likely do not apply. As for the Azazel rootkit, it uses LD_PRELOAD. According to the ld.so manpage[1] it is ignored for setuid/setgid executables. This looks like the behaviour is not exactly that of the Linux ld.so so perhaps this limits the rootkit's impact. [1] http://www.openbsd.org/cgi-bin/man.cgi?query=ld.so§ion=1 http://www.openbsd.org/cgi-bin/man.cgi?query=ld.so§ion=1
- throwaway2048 13y agoopenbsd does have loadable kernel modules http://www.openbsd.org/cgi-bin/man.cgi?query=lkm http://www.openbsd.org/cgi-bin/man.cgi?query=lkm LD_PRELOAD and friends are also ignored on linux for setuid/setgid binaries, otherwise privilege escalation would be trivial, just start any dynamicly linked setuid binary with LD_PRELOAD and go to town.
- 4ad 13y ago> Website is offline No cached version of this page is available. ...and we broke it. This is, for all intended purposes, a static page. When will people learn to put a caching nginx in the front... that's all it takes, really.
- StavrosK 13y agoThe phrase is "for all intents and purposes", although your variation also fits, very interesting!
- fzltrp 13y agoCuriously, I use that variation as well. I tried to look it up to find out where I could have picked it up, but couldn't get any interesting results. Does anyone else uses that?
- DougBTX 13y agoSimilar: http://eggcorns.lascribe.net/english/32/intensive-purposes/ http://eggcorns.lascribe.net/english/32/intensive-purposes/
- drjesusphd 13y agoBut "intended purposes" actually makes sense in context.
- pessimizer 13y agoIt does imply the existence of unintended purposes.
- DougBTX 13y agoYes, that's one of the defining features of an "eggcorn", that it does make sense. Or even more sense than the original. Here's a more thurough definition: http://eggcorns.lascribe.net/about/ http://eggcorns.lascribe.net/about/
- guard-of-terra 13y agoI thought that Vernor Vinge greatly exaggerated hackability when he wrote Fire in the Deep, but now I see he was right and I was wrong. Go read it now. Scary.
- sillysaurus2 13y agohttp://www.amazon.com/Fire-Upon-Deep-Zones-Thought/dp/0812515285 http://www.amazon.com/Fire-Upon-Deep-Zones-Thought/dp/081251...
- lucb1e 13y agoThe title suggests there is a new virus for Linux, but I see a wiki listing features from the malware and even linking to source code on Github. Was this thing engineered as some sort of demonstration? Or how else did they get the source code?
- Sanddancer 13y agoYeah, it's a demonstration of various techniques used in more modern rootkits. As such, certain bits and pieces, like its masking of ptrace() is set to an obvious message. The blog post regarding the release -- http://www.chokepoint.net/2014/02/detecting-userland-preload-rootkits.html http://www.chokepoint.net/2014/02/detecting-userland-preload... -- is much more useful than this wiki page in discussing how certain things are accomplished.
- martius 13y agoI think it was mentioned on a comment, but just to make it clear: A rootkit is not a virus nor a way to obtain privileges on a Linux box, but a set of tools providing various features to keep hidden a root access to the hacked box. This rootkit provides various backdoors allowing to get root ssh access and advanced anti-detection features, but as far as I know, this package won't hurt you badly as far as you don't manipulate it with a privileged user.
- ubershmekel 13y agoMaybe I misunderstood the grammar somehow, but did you just say: > This rootkit provides various backdoors allowing to get root ssh access followed by: > this package won't hurt you badly Allowing root ssh is the ultimate death of your machine's security. Having this installed hurts you badly.
- StavrosK 13y ago> Allowing root ssh is [...] your machine's security. Taking stuff out of context is fun! He said it won't hurt you badly as long as you don't run it as root. From that, I understand that it can't install itself unless it's run as a privileged user.
- ubershmekel 13y agoThanks for that, I guess I misread a bit. So what he's saying is that there's no privilege escalation exploit packaged with this rootkit. Gotcha. Still I wouldn't mention "this package won't hurt you" along with such a tool. Many userland exploits exist.
- mwcampbell 13y agoI wonder if all-statically-linked Linux distros will become popular on the server as a defense against userland rootkits like this.
- saljam 13y agoThat would be cool. Are there any? I'm aware of sta.li, but it doesn't seem to be there yet. As a matter of fact, is it possible to get stuff like nsswitch working without dynamic linking on Linux?
- lawnchair_larry 13y agoThey won't.
- m00dy 13y agolol , is ptrace() hooking only technique that backdoor has as a anti-debugging feature? If so , i will shit to my pants.
- jden 13y agoJust a quick test with LTTng (lttngtrace part of lttngtop) : http://pastebin.com/rvebt7rp http://pastebin.com/rvebt7rp I know kernel tracing is cheating for this kind of backdoor, but it can be easy ;-)