Comment on Absolute disaster, RAT backdoored through WINE. Assistance with Docker
TropicalDingdong@lemmy.world 3 weeks ago
Jfc.
Comment on Absolute disaster, RAT backdoored through WINE. Assistance with Docker
TropicalDingdong@lemmy.world 3 weeks ago
Jfc.
ushjftye@programming.dev 3 weeks ago
I don’t use paypal, but thank you. Bro I explained this on .ml and their first question was why do you have a computer with 128 terrabytes of storage. like, my god
TropicalDingdong@lemmy.world 3 weeks ago
Yeah. As an aside, including heat you’ve written here, it would be good for you to document what went wrong, how you identified things going wrong, and how you ultimately resolved it, so we can all learn and maybe get something from this other than the pain you are experiencing.
Homelabbing is a command we really only have each other
ushjftye@programming.dev 3 weeks ago
I didn’t own the network, that was the problem. My distro has security updates still, everything comes from repositories. I didn’t containerise everything. That was my fault. WINE had network access and filesystem access and it wasn’t in a container, and the password to the router was plain text. Absolutely chilling, finding the root /run/. 128TB man. I use clamav and it identified winexpiro hidden in a .DLL called .BRM. Supposedly for Windows 6. WINE is just a compatability layer, so you can push any .DLL into it. This is why I NEED to learn commandline docker, because it’s just not fucking safe. I don’t know whose machine it got to first, but once you’re connected to a machine as admin that’s connected to a router as admin. Like Fuck me.
sp3ctr4l@lemmy.dbzer0.com 2 weeks ago
That all sounds like a pretty good diagnosis/evaluation to me.
You got got by somebody.
But do not spend any more time trying to invetigate with the aim of like, determining the culprit.
You need to act defensively.
See my other comment.
Jumuta@sh.itjust.works 3 weeks ago
documenting like this is also really good for future reference