Friday, June 22, 2012

WinMX is currently protected from NOTHING!

Have you noticed that the WinMXWorld website is down right now? Well if you haven't you should probably know what it means to you, and why they're such an irresponsible and clueless organization.

Cache Servers Have NO Blocklist?

Since every WinMX peer cache server relies on a text file hosted on the WinMXWorld website for their blocklist ip ranges to give to actual WinMX users (www.winmxworld.com/block/cache_list.txt), they are currently being fed a generic 301 "Moved Permanently" error code message. These redirect codes (301/302) and used to tell your web browser that the website or web page you are trying to visit has been moved temporarily (302) or permanently (301). As it seems the admins at WinMXWorld have no clue what they are doing, they have set a 301 code. Indicating that the website will never return. I sure hope Google has discovered this so our relevent blog posts can move up a few spots to the top of the search results for "winmx world".

 Check for yourself here: http://www.winmxgroup.com/index.php?id=cache-checker  (just click any of the "Online" spots under the blocklist column)

Because of this severe oversight of the WinMXWorld admins and their "coders". All WinMX users are currently being bombarded with fake files in their search results, as well as being completely unprotected from any of the cartel organizations connecting directly to them.

Below is an example of thousands of fake files, along with whois' of maxed out secondary users as we remember seeing from years ago when the fake files first started:


Why this shouldn't have happened:

Due to the way the cache server and the patch that they and every WinMX user is using, there are no integrity checks built in to prevent this kind of thing from happening. You would think someone would make sure that the cache servers would not replace a list of actual ip ranges with a block of html garbage... and you would think the patch would be designed to not forget all of the previous ip ranges from the REAL block list before it adds in a block of html... but I guess no one was smart enough to think of that.



When can we expect a fix? Who knows... we still haven't received a fix for these network attacks. I would say an estimate of 2015 is a good guess. But I can assure you, this group of people running WinMXWorld really has no fucking clue what they are doing, and if this doesn't convince you, I don't know what will.