Live data from Hacker News

Malicious Use of the HTML5 Vibrate API

shkspr.mobi

51–60 of 67 posts

Re: Malicious Use of the HTML5 Vibrate API

#51
These are interesting hacks and there should probably be some ways to help users avoid being deceived in this way.

However they don't have much to do with the introduction of the vibrate API. What this assumes is that the phone vibration is something the user should or could generally rely on to distinguish between genuine system functions and fakes. That's just not true for many reasons.

Re: Malicious Use of the HTML5 Vibrate API

#52
"No one cares about Windows Phone or BlackBerry - so I didn't test them."

Often these forgotten platforms have the most issues with attackers/exploiters. There was just an article on here the other day about the wave of Windows XP exploits we are bound to see now that it no longer gets patched.

Re: Malicious Use of the HTML5 Vibrate API

#53
post #49

Earlier quoted context omitted.

How do you know if the woman on the other end is pretty? :) There's a great app for Android (in Sweden, I suppose there are similar apps for other countries) that searches digital phone registries on an incoming call and after about a second displays whatever data it has found on the incoming call screen (such as Telemarketing Company, Salesperson, etc) It also uses some form of rating system so if enough users have…

Which app, if you don't mind me asking?

It's called "Vem ringde" ("Who called" in swedish). I believe the iOS does not grant enough permissions during an incoming call so when using the app on an iPhone one can only do the lookup after the call has finished (answered or missed) which explains the name (past tense). This is of course inferior to the Android functionality, but this might have changed since last time I checked.

Re: Malicious Use of the HTML5 Vibrate API

#54
post #11

I can't wait to see this being exploited by advertisements. I'm already seeing this really bad trend of ads redirecting to the app store which makes the page that did it completely unreadable (going back to safari shows an empty page) and now there's the prospect of the phone vibrating to the blinking of the various ads wanting my attention? If this goes on like this, I'll really need an adblocker on my phone.

Firefox on Android has plugin support, and Adblock Plus is one of those supported. I'd definitely recommend it, makes mobile browsing suck so much less.

Re: Malicious Use of the HTML5 Vibrate API

#55
post #40

> It is not impossible to conceive of malicious code being able to exploit an unpatched browser flaw and overdrive the motor to destruction. Are there not restrictions at the OS or hardware level to prevent this?

In the Dark Ages phone I saw, the processor got to turn on a transistor that passed current to the vibrator. Normal operation was either off or full on; there wasn't a way to write a bit greater than 1 to the port pin that controlled the vibrator.

Re: Malicious Use of the HTML5 Vibrate API

#56
post #20
post #17

Earlier quoted context omitted.

And, on mobile Firefox, there's no way to see the permissions of a page. Certainly no that I can see of FF for Android.

Firefox for Android developer here, you can long-tap on the location bar while on the page and select 'Edit Site Settings'. Is that what you're looking for?

That is only used if the API requires user confirmation. So things like geolocation, camera, and microphone access will be shown. Adding the feature from desktop should be a bug already. If not then we should file one.

Re: Malicious Use of the HTML5 Vibrate API

#58
Most use of the vibrate API will obviously be malicious if it's implemented without spam prevention; otherwise I won't be able to disable the feature fast enough.

The only way this could be workable is if there were something like an HTML meta tag for requesting vibrate support for scripts running from your domain, and that would prompt a one-time dialog to white-list that domain for vibrate support in JS.

Re: Malicious Use of the HTML5 Vibrate API

#59
post #49

Earlier quoted context omitted.

Which app, if you don't mind me asking?

It's called "Vem ringde" ("Who called" in swedish). I believe the iOS does not grant enough permissions during an incoming call so when using the app on an iPhone one can only do the lookup after the call has finished (answered or missed) which explains the name (past tense). This is of course inferior to the Android functionality, but this might have changed since last time I checked.

iOS version: https://itunes.apple.com/us/app/cia/id580455042?mt=8

Re: Malicious Use of the HTML5 Vibrate API

#60
post #9
post #6

Since HTML pages cannot open up by themselves, and user can navigate away, the risk is lower compared to a native app which can do far more damage. Never the less, permission mechanism should have been enabled.

What about ads? The ones that now e.g. pretend to be Skype pop-ups.

HTML Popups have always been a problem and with re targeting the Ads are a menace. And some clever spoofing is definitely possible. A proper ad/popup blocker for native browsers would help.
Post reply on HN