Pirates Bay using visitors CPU power to mine bitcoins, needs ads alternate

Posted September 19, 2017

However, reportedly, The Pirate Bay said nothing to users, many simply started to notice a spike in CPU usage when visiting the website. TorrentFreak inspected these claims and found that they appeared in search results and category listings but not on the homepage nor on torrent listings. Pirate Bay has confirmed that they have been testing this method of generating income for a day now and that if this goes on then it could replace ads entirely. The miner runs automatically for visitors of the site, using up users' CPU power in order to mine for a type of cryptocurrency called Monero.

Torrent Freak said they were told the miner was being tested for 24 hours as a possible replacement for traditional banner ads. So far, comments on the post are leaning more towards the positive side, so this may end up becoming a permanent change. The users first noticed it when the CPU usage of their respective laptops or desktop computers registered on a high level.

The get around is to use NoScript to block the miner or just block Javascript on the site He added that this could cause some performance compromises.

The JavaScript code, Coinhive, is supposed to throttle the rate at which it mines coins so as not to completely take over a PC's CPU resources, making it ideal for "borrowing" a certain amount of a user's CPU without preventing them from downloading content. But we also need enough money to keep the site running.

Supermoderator Sid issued a statement to TorrentFreak saying, "That really is serious, so hopefully, we can get some action on it quickly". Do you want ads or do you want to give away a few of your CPU cycles every time you visit the site? Upon closer examination, it was discovered that an embedded digital coin miner was to blame. Users reported that the miner could be blocked via browser settings, script blocker add-ons or ad blockers.

Note: Initially there was a small typo so all CPU for a client was used.

This bug had now been fixed, the administrators said, which should limit how much it used to 30% at most. Also it is restricted to run in one tab only so even if you have 10 tabs oven it will only be running in 1.