3 ms·
Further info for those interested: My developer machine was infected with the Kryptik trojan. Using WireShark I could see that I had become the proud member of
by gridspy 17y ago
Further info for those interested: My developer machine was infected with the Kryptik trojan. Using WireShark I could see that I had become the proud member of a botnet, it probably found a saved password for FTP on my machine and compromised my server that way. Makes me feel all dirty inside watching my computer send viagra emails and receive "sorry, you are blacklisted" responses.
All the passwords have been changed and the relevant computer quarantined. I'm still working on removing the virus, seems to be using drivers to mask its presence from the virus checkers I am using. I've got some ideas based on using a scanner on a live-cd.
What is really fun is that the virus definition for the trojan was added to NOD32 after I was infected, so I don't know how much help a virus checker would have been, if it was installed.
That will learn me for leaving saved passwords on an otherwise secure machine.
- netcan 17y agoThanks for coming back with that.
- gridspy 17y agoI used an external hard disk drive caddy to mount the infected HDD on another machine. I then used Malware bytes to scan the HDD. It found Trojan.Agent on the hdd (in a dll inside windows/system), which it hadn't found when malwarebytes was run directly on the infected system. The infected computer has ceased sending suspicious packets. I don't know how I am going to trust this machine again.