366
Spyware maker LetMeSpy shuts down after hacker deletes server data
(techcrunch.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 05 Aug 2023
366 points (98.4% liked)
Technology
59259 readers
1753 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
As someone who deals with this sort of thing, for ransomware and other destructive intrusions, the first thing they go for is the backups themselves.
Companies that have an second backup copy that is seperate somehow so non-lateral movement isn't possible are the ones that survive this level of breach.
Or they could just be stupid (cheap) and didn't have any lol
well they dealt in malware, perhaps they wanted the evidence to be easy to delete in case law enforcement decided to visit
oh_shit_burn_it_all.sh
Often the server needs access to make backups, so when you get in and get root, you sometimes also have access to delete the backups.
It depends on how it's set up. If the server pushes the backups somewhere else and has write access, then the hacker can delete them. But if another account logs in to the server and makes a backup and downloads it, it's impossible for the hacker to access the backup.
Depends on if you planned for the scenario or not.
Part of a good backup solution involves ensuring that it's literally impossible for the "root" / "administrator" whatever user on the production system to delete the backups. For instance, were this AWS, it would be done by creating a separate AWS account and use IAM roles to provide access to a S3 bucket with the "DeleteObject" permission explicitly denied. Perhaps, even deny everything except something like PutObject, and ensure the target S3 bucket is versioned, so even overwriting the contents with garbage is recovered by restoring a previous version.
But most businesses don't think like that.
Yup. I work as a devops guy with aws and that's what I do. But I've seen a lot of enterprises having no clue about these things.
I go for stupid &cheap, most people think backups is when onedrive and Microsoft reinforces that insane idea with popups).