- Feb 4, 2016
- 2,520
Google Chrome engineers are considering adding a special browser permission that will thwart the rising trend of in-browser cryptocurrency miners.
Discussions on the topic of in-browser miners have been going on the Chromium project's bug tracker since mid-September when Coinhive, the first such service, launched.
A permission to block JS code that ramps up CPU usage
To Bleeping Computer's knowledge, there have been at least two complaints (bug reports) from concerned Chrome users that did not like having their resources hijacked by in-browser miners.
"Here's my current thinking," Ojan Vafai, a Chrome engineering working on the Chromium project, wrote in one of the recent bug reports.
If a site is using more than XX% CPU for more than YY seconds, then we put the page into "battery saver mode" where we aggressively throttle tasks and show a toast [notification popup] allowing the user to opt-out of battery saver mode. When a battery saver mode tab is backgrounded, we stop running tasks entirely.
I think we'll want measurement to figure out what values to use for XX and YY, but we can start with really egregious things like 100% and 60 seconds.
I'm effectively suggesting we add a permission here, but it would have unusual triggering conditions [...]. It only triggers when the page is doing a likely bad thing.
Discussions on this bug report are still ongoing, and Vafai's suggestion has not been formally approved, even if another engineer thought it a good idea.
Google can't block in-browser miners via a blacklist
The potential of having a browser permission to block JavaScript tasks that cause high-usage CPU operations for extended periods is a step forward.
EDIT:
here is a thread/article on MT that explains what crypto miners are. MT-members are writing about the risks of miners:
The Internet Is Ripe With In-Browser Miners and It's Getting Worse Each Day
Last edited: