AI-powered
podcast player
Listen to all your favourite podcasts with AI-powered features
Detecting Malicious DLL Files in a Compromise Server
There are two directions you move from here. One figure out what happened after that, what other systems have been effected and the other track is how they got in the first place. The call was to allow the investigation to continue a little while longer without wiping this compromise server down and disinfecting it. They looked through the logs and pretty easily discovered that someone simply logged into this computer, normally through a remote dust hop, and put it there. Which is not an exploit or a hack at all. It means someone had to use ther name a password to get into this server. So they know how it got on, and they know what files it left on the system,. But they're curious