14 DAY TRIAL // The Dutch anti-piracy organization known as Bescherming Rechten Entertainment Industrie Nederland (BREIN) has often been a target of Anonymous and other hacktivists, but the latest court decisions made the hackers really mad, so on April 18 they want to launch a full-force attack against its site.
According to a statement released by the hackers on PasteBay, BREIN plans to force all ISPs from the Netherlands to block The Pirate Bay on April 19, which is why the attack is planned to take place one day before the anti-piracy outfit goes to court.
“In the Netherlands, as you might know, we have an organisation called 'Stichting Brein'. A organisation says they defend copyright of artists, but they are censoring the internet in the Netherlands,” Anonymous writes.
“At january the 11th, 2012, the dutch providers Ziggo and XS4ALL already blocked our lovely piratebay.com because the judge told them to after a case with Stichting Brein. many TPB mirrors have been blocked too!” the hackers explain.
“At the 19th of April, 2012, Brein goes to the judge again, to get The pirate bay blocked for all other dutch providers like tele2. In a week, at the 18th of april, a day before the decision, at 20:00 GMT (21:00 dutch time),we will unleash hell to Stichting Brein, and let them know that they should have expected us!”
The hacktivists also reveal the list of targets made up of “sites that help and sponsor Brein.”
In the past period, Anonymous and their supporters have raised a lot of concerns regarding the blocking of file-sharing sites such as The Pirate Bay.
Now that anti-piracy organizations push hard to make sure that copyright infringing sites are put down, online activists also seem more determined to keep them running.
When Megaupload was shut down, hackers launched what some called the largest DDOS attack ever, taking down numerous important websites. However, the attacks did little to help Megaupload. It remains to be seen if this situation will be any different.
Note. My Twitter account has been erroneously suspended. While this is sorted out, you can contact me via my author profile or follow me at @EduardKovacs1