I knew that idea was ringing a bell! Someone totally did that a bit more than a year back. No idea how well it actually worked, but there is prior art!A white-hat robo-caller?The most important thing to remember when encountering one of these windows is not to panic and to never call the phone numbers displayed in the warnings.
... unless you're bored and feel like wasting a scammers time for the lulz.
What we need is an automated system which wastes their time without wasting yours.
The "bad" domain is msf-help.info. All the rest of that blarf is subdomain or host name.In a better world, domain registration services would not let random criminals register domain names containing trademarked names like .microsoft. and would flag suspicious ones like .windows. for human review.
They would still allow registering free-speech and complaint sites like micsofts-a-naughty-puffin.com where it was not easily mistaken for an official company site, while protecting a few users from microsoft.ransomware.scam
Normally, Chrome also does this on Windows... however it seems that the specifics of the attack allowed the researchers to cause Chrome on Windows to lock up in a way that prevents it from showing.It does on Linux too, unless you're a developer that gets annoyed with it when you're trying to debug performance issues and manually turn it off...(yes, I fit in that category).Chrome doesn't do the "browser tab is unresponsive, do you want to close?" thing on Windows, just Mac? That's weird, as I know I've seen it on other browsers in Windows (doesn't happen often, so can't remember for sure if it was IE11, Edge, or Firefox).
Also, second the question as to whether this is Chrome exclusive. I generally run a mix of Firefox and Edge at home.
Still a pretty serious flaw, but not the "why the heck is this functionality only available on some platforms" oversight it appears to be at first glance.
In an e-..... what? Don't leave me hangin'!As the right side of the image shows, the CPU resources of Windows machines are exhausted, a condition that's sure to contribute to the worry that something with the computer isn't right. In an e-
I dunno, it might end up spamming you with file-save dialogs instead. Depends if Chrome is smart enough to not do that.Wouldn't enabling the "Ask where to save each file before downloading" option stop this on the first attempted download?By combining the API with other functions, the scammers force the browser to save a file to disk, over and over, at intervals so fast it's impossible to see what's happening.
Chrome is getting to big for its own good.
or anyone's good, for that matter.
Windows being pegged and brought to its knees by apps. What a clusterf*ck of an OS.
Does Ctrl+F4 work to close the tab? I find it can end up closing things that a mouse didn't work on when popups are involved.Normally, Chrome also does this on Windows... however it seems that the specifics of the attack allowed the researchers to cause Chrome on Windows to lock up in a way that prevents it from showing.It does on Linux too, unless you're a developer that gets annoyed with it when you're trying to debug performance issues and manually turn it off...(yes, I fit in that category).Chrome doesn't do the "browser tab is unresponsive, do you want to close?" thing on Windows, just Mac? That's weird, as I know I've seen it on other browsers in Windows (doesn't happen often, so can't remember for sure if it was IE11, Edge, or Firefox).
Also, second the question as to whether this is Chrome exclusive. I generally run a mix of Firefox and Edge at home.
Still a pretty serious flaw, but not the "why the heck is this functionality only available on some platforms" oversight it appears to be at first glance.
I just updated the story to add:
1) The researchers have been unable to get the technique to work on any browser other than Chome, so yes, this is a Chrome-only issue.
2) The Chrome dialog box about an unresponsive page is displayed to Windows users, but the box is of no help because the attackers have somehow figured out a way to prevent the "exit page" button from showing on Windows. This doesn't happen to Chrome users on a Mac.
The updated information starts in paragraph six.
Ctrl-F4 kills the current task in windows, which in most modern browsers is the current tab.Can you use Chrome's task manager (shift+esc in Windows) to eventually kill the offending tab?
Once it opened, at least, since I assume it would take a while to start with all the resources being taken up.
The scams are often transmitted through malicious advertisements or legitimate sites that have been hacked
? Did you even take a moment to think before you posted? You do realize that the world doesn't simply revolve around you .... right?"Stealing Pictures"? I mean I get it, they're just creating fear, but if some jerk wants to look through the 200GB of movies and pictures of my kids, more power to them. Maybe they'd like to come over for a slide show presentation?
That can't be true. Chrome doesn't support that interface, only Internet Explorer does. Hence the 'ms' prefix. Instead, the script creates a download-link to a blob and programmatically clicks that link in a loop.the article":33f8unc2 said:A new technique [...] works against Chrome by abusing the programming interface known as the window.navigator.msSaveOrOpenBlob.
I used to work in a Microsoft Store taking care of the crap that happens like this. I still remember the most evil thing these scammers would do.
At some point during the phone call they would setup a syskey password. Which prevents Windows from booting, has no 'forgot password' like feature or anyway to be permanently disabled.
The only thing that could be done was to restore to an earlier point, but they started deleting restore points as well.
They'd use this to hold the computer ransom for payment, threatening never to give over the password until some high sum was forked over. Sometimes they even gave the wrong password when money was paid.
So glad this was remove in the Fall Creators Update.
Manually shutting down the entire browser risks losing any unsaved work contained in any open windows.
Unless you are in Google Docs or something, there isn't really much "unsaved work" that people have open in a browser. Just give Chrome the three finger salute, then blacklist the site that crashed you in your HOSTS file. Then go back to surfing.
In an e-..... what? Don't leave me hangin'!![]()
In a better world, domain registration services would not let random criminals register domain names containing trademarked names like .microsoft. and would flag suspicious ones like .windows. for human review.
They would still allow registering free-speech and complaint sites like micsofts-a-naughty-puffin.com where it was not easily mistaken for an official company site, while protecting a few users from microsoft.ransomware.scam
Yeah, because I want my 3D rendering software to be forced to only user 50% of available CPU because... why? And if the 3D program is allowed to do it why can't other programs?
Also, I've used Linux and Mac and both have the same problem if a program has gone rogue. At least on Windows the GUI display framework doesn't crash and burn when a program goes out of control like it can on Linux. (Windows will get unresponsive, but I've had the Linux GUI backend flat out crash and not recover on me.)
Yeah, because I want my 3D rendering software to be forced to only user 50% of available CPU because... why? And if the 3D program is allowed to do it why can't other programs?
Also, I've used Linux and Mac and both have the same problem if a program has gone rogue. At least on Windows the GUI display framework doesn't crash and burn when a program goes out of control like it can on Linux. (Windows will get unresponsive, but I've had the Linux GUI backend flat out crash and not recover on me.)
No OS should allow any app to peg the CPU at 100% and make the system UI unresponsive. I've never experienced that on a Mac, but on Windows it's very common. As for that 50% you pulled out of your ass, the system should dedicate as much CPU resources as it can without sacrificing the responsiveness of the system UI so the user can gracefully recover from any app that's pegging the system.
Browser dialog windows aren't "power user options". UWP doesn't allow any rendering engine besides what Edge uses, which defeats the entire purpose (unless your market share is just that big).Considering that Chrome at this point is basically an OS, not too surprising. I'm not a computer scientist, but I'd perhaps recommend Google to have a slimmed down version of the browser (Perhaps without power user options) that can't take over the CPU (this alone could help with mining and exploits like this), and that way leave the full blown browser for power users.
Or conversely, have the full blown app through UWP which would probably not have this behavior, due to how the platform works.
An OS that runs on arbitrary hardware that people actually want to do work on might actually need to peg CPUs at 100% even at the sacrifice of UI responsiveness. I used the 3D rendering example because for what I do it's the most common reason I personally have for an unresponsive UI. It's rare that I have anything but that kind of specialty software that is able to saturate all my cores at 100% and things like games and more mundane programs like browser and office suites don't do that.
I'd imagine if you told someone using a Mac for scientific or compute-intensive graphics rendering purposes an OS should not be allowed to peg the CPU at 100% even if that means sacrificing UI responsiveness they'd just laugh at you. Macs aren't magical boxes running on fairy dust and unicorn farts and they actually do have problems like every other computer.
I'd imagine if you told someone using a Mac for scientific or compute-intensive graphics rendering purposes an OS should not be allowed to peg the CPU at 100% even if that means sacrificing UI responsiveness they'd just laugh at you. Macs aren't magical boxes running on fairy dust and unicorn farts and they actually do have problems like every other computer.
Browser dialog windows aren't "power user options". UWP doesn't allow any rendering engine besides what Edge uses, which defeats the entire purpose (unless your market share is just that big).Considering that Chrome at this point is basically an OS, not too surprising. I'm not a computer scientist, but I'd perhaps recommend Google to have a slimmed down version of the browser (Perhaps without power user options) that can't take over the CPU (this alone could help with mining and exploits like this), and that way leave the full blown browser for power users.
Or conversely, have the full blown app through UWP which would probably not have this behavior, due to how the platform works.
Dialog windows don't require the HTML5 tag, Javascript dialog windows have been around forever. Safari and Opera both support the tag as well.Browser dialog windows aren't "power user options". UWP doesn't allow any rendering engine besides what Edge uses, which defeats the entire purpose (unless your market share is just that big).Considering that Chrome at this point is basically an OS, not too surprising. I'm not a computer scientist, but I'd perhaps recommend Google to have a slimmed down version of the browser (Perhaps without power user options) that can't take over the CPU (this alone could help with mining and exploits like this), and that way leave the full blown browser for power users.
Or conversely, have the full blown app through UWP which would probably not have this behavior, due to how the platform works.
The dialog is an advance feature of HTML, it’s not evenly implemented by browsers, especially the dialog tag, which is only supported by Chrome’s engine.
Yeah, because I want my 3D rendering software to be forced to only user 50% of available CPU because... why? And if the 3D program is allowed to do it why can't other programs?
Also, I've used Linux and Mac and both have the same problem if a program has gone rogue. At least on Windows the GUI display framework doesn't crash and burn when a program goes out of control like it can on Linux. (Windows will get unresponsive, but I've had the Linux GUI backend flat out crash and not recover on me.)
No OS should allow any app to peg the CPU at 100% and make the system UI unresponsive. I've never experienced that on a Mac, but on Windows it's very common. As for that 50% you pulled out of your ass, the system should dedicate as much CPU resources as it can without sacrificing the responsiveness of the system UI so the user can gracefully recover from any app that's pegging the system.
An OS that runs on arbitrary hardware that people actually want to do work on might actually need to peg CPUs at 100% even at the sacrifice of UI responsiveness. I used the 3D rendering example because for what I do it's the most common reason I personally have for an unresponsive UI. It's rare that I have anything but that kind of specialty software that is able to saturate all my cores at 100% and things like games and more mundane programs like browser and office suites don't do that.
I'd imagine if you told someone using a Mac for scientific or compute-intensive graphics rendering purposes an OS should not be allowed to peg the CPU at 100% even if that means sacrificing UI responsiveness they'd just laugh at you. Macs aren't magical boxes running on fairy dust and unicorn farts and they actually do have problems like every other computer.
The most important thing to remember when encountering one of these windows is not to panic and to never call the phone numbers displayed in the warnings.
... unless you're bored and feel like wasting a scammers time for the lulz.
Chrome doesn't do the "browser tab is unresponsive, do you want to close?" thing on Windows, just Mac? That's weird, as I know I've seen it on other browsers in Windows (doesn't happen often, so can't remember for sure if it was IE11, Edge, or Firefox).
Also, second the question as to whether this is Chrome exclusive. I generally run a mix of Firefox and Edge at home.
By combining the API with other functions, the scammers force the browser to save a file to disk, over and over, at intervals so fast it's impossible to see what's happening.
Wouldn't enabling the "Ask where to save each file before downloading" option stop this on the first attempted download?
Might just be saving a relatively small temporary file or something. Mega for example, can download the whole file before even showing you a popup.
Chrome is getting to big for its own good.
or anyone's good, for that matter.
Windows being pegged and brought to its knees by apps. What a clusterf*ck of an OS.
Yeah, because I want my 3D rendering software to be forced to only user 50% of available CPU because... why? And if the 3D program is allowed to do it why can't other programs?
Also, I've used Linux and Mac and both have the same problem if a program has gone rogue. At least on Windows the GUI display framework doesn't crash and burn when a program goes out of control like it can on Linux. (Windows will get unresponsive, but I've had the Linux GUI backend flat out crash and not recover on me.)
Manually shutting down the entire browser risks losing any unsaved work contained in any open windows.
Unless you are in Google Docs or something, there isn't really much "unsaved work" that people have open in a browser. Just give Chrome the three finger salute, then blacklist the site that crashed you in your HOSTS file. Then go back to surfing.