Earlier quoted context omitted.
> from which you can do some forensic work to find out how you were owned It's worth noting that if you are really serious about doing forensics and investigating the attack, then shutting down can be pretty destructive. > what data is recoverable. Another point I'd make is that try to recover as little as possible from the infected system and prefer using clean backups instead. I agree on the overall sentiment thoug…
I may be wrong, but these days doesn't malware have a loader (which has a hook in the boot cycle at some point) and a payload (which usually poses as an innocent file tucked away on your system somewhere). Even if you wholesale recover your data and include the payload, there is no loader hooked into your newly-installed system, rendering the payload a digital bullet without a corresponding gun. As far as I'm aware,…
Linux ransomware in the wild
51–60 of 112 posts
Re: Linux ransomware in the wild
#52Nice read but nothing particularly special here and it happened months ago. The title is alarmist. TL;DR: The user ran firefox as root and the attack happened through adobe-flash. Hardly a sophisticated attack.
While possible, this sounds so spectacularly unlikely that I can’t help but think that you’re just speculating.
Re: Linux ransomware in the wild
#53Earlier quoted context omitted.
Why does it matter if Firefox ran as root or not? I agree it's terrible practice in principle. But most people will run Firefox as their ordinary user, which normally has full access to the files in their home directory. If someone gets arbitrary code execution under your user, they can erase/encrypt your files. Who cares if the OS files are safe. All the data you really care about will be gone.
agree. ordinary user is absolutely sufficient. I'll now present a sophisticated privilege escalation method that most of us won't notice (me included, sarcasm off): alias sudo='/usr/bin/sudo echo something evil && /usr/bin/sudo' I don't think it matters that he used his root account. Edit: Maybe I'm wrong with my opinion, you can disable ASLR using your root rights... https://askubuntu.com/a/318476 Edit: Last exploit…
Re: Linux ransomware in the wild
#54Earlier quoted context omitted.
agree. ordinary user is absolutely sufficient. I'll now present a sophisticated privilege escalation method that most of us won't notice (me included, sarcasm off): alias sudo='/usr/bin/sudo echo something evil && /usr/bin/sudo' I don't think it matters that he used his root account. Edit: Maybe I'm wrong with my opinion, you can disable ASLR using your root rights... https://askubuntu.com/a/318476 Edit: Last exploit…
I use /usr/bin/sudo
Re: Linux ransomware in the wild
#55Friends don't let friends run Flash. Does Gentoo have Firejail readily available? That would have prevented this, I'm pretty sure.
Re: Linux ransomware in the wild
#56Earlier quoted context omitted.
> from which you can do some forensic work to find out how you were owned It's worth noting that if you are really serious about doing forensics and investigating the attack, then shutting down can be pretty destructive. > what data is recoverable. Another point I'd make is that try to recover as little as possible from the infected system and prefer using clean backups instead. I agree on the overall sentiment thoug…
I may be wrong, but these days doesn't malware have a loader (which has a hook in the boot cycle at some point) and a payload (which usually poses as an innocent file tucked away on your system somewhere). Even if you wholesale recover your data and include the payload, there is no loader hooked into your newly-installed system, rendering the payload a digital bullet without a corresponding gun. As far as I'm aware,…
So you shouldn’t trust that this doesn’t happen again.
Re: Linux ransomware in the wild
#57I don't understand from this post why run Firefox as root and why have in addition flash enabled on Linux. But it's still interest that they bother with making ransomware the first place for Linux.
Lots of servers run Linux. Lots of data to hold ransom on lots of servers running Linux.
Re: Linux ransomware in the wild
#58Earlier quoted context omitted.
Why does it matter if Firefox ran as root or not? I agree it's terrible practice in principle. But most people will run Firefox as their ordinary user, which normally has full access to the files in their home directory. If someone gets arbitrary code execution under your user, they can erase/encrypt your files. Who cares if the OS files are safe. All the data you really care about will be gone.
Firefox has some sandboxing on Linux, though it's quite recent.
Re: Linux ransomware in the wild
#59Re: Linux ransomware in the wild
#60Earlier quoted context omitted.
Why does it matter if Firefox ran as root or not? I agree it's terrible practice in principle. But most people will run Firefox as their ordinary user, which normally has full access to the files in their home directory. If someone gets arbitrary code execution under your user, they can erase/encrypt your files. Who cares if the OS files are safe. All the data you really care about will be gone.
agree. ordinary user is absolutely sufficient. I'll now present a sophisticated privilege escalation method that most of us won't notice (me included, sarcasm off): alias sudo='/usr/bin/sudo echo something evil && /usr/bin/sudo' I don't think it matters that he used his root account. Edit: Maybe I'm wrong with my opinion, you can disable ASLR using your root rights... https://askubuntu.com/a/318476 Edit: Last exploit…