P2P File Sharing and Limewire

In another “duh!” moment, it was discussed that government workers and contractors probably should not be sharing their drive contents using P2P software. In a recent hearing, U.S. lawmakers discussed sensitive content like “FBI files, medical records, Social Security numbers and even a file containing information about a safe house location for [the U.S.] President” that was accessed over LimeWire.

While this post does not present a stance on the policymaking or even the level of intelligence it takes to accidentally share drive contents over LimeWire, the ThreatFire continues to trigger and protect our community against a number of malware executables accessed over the LimeWire sharing network. Always be careful of the shared content on these networks — too often, things are too good to be true, as posted previously. Today, ThreatFire protected user information from more crackz bundled with malware, like another “Age of Mythology[ENGLISHVERSION] Crack Keygen” with a malicious setup file.

When the unsuspecting P2P user runs the setup file, this trojan downloader contacts a server at www.diespamdie. com, where adware and additional bot malware are served up. One of the served files includes a nasty bot sometimes identified by its packer, its circa 1999 injection technique, and its string references, Tdss.

This entry was posted in The Law. Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *


You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>