Harvesting credit card numbers and passwords from websites

Re:Harvesting credit card numbers and passwords from websites by gcornut on Monday January 08, 2018 @11:27AM (#16097795)

I'm sometimes frustrated by uMatrix blocking every requests to third party website and forcing me to accept each of them when needed. But when I see exploits like this I'm happy that I haven't uninstalled it :D. You still have to be vigilant when whitelisting requests in the uMatrix panel though.

[ Parent | on HN ]

Re:Harvesting credit card numbers and passwords from websites by moreless on Tuesday January 09, 2018 @04:19AM (#16104713)

Note that uMatrix doesn't protect you (by default) from sending data out.

It also depends on the page you are visiting. If it's just some random post on net I actually don't care much if they do manage to post data elsewhere (the risk in that case is actually higher if I allow ajax.googleapis.com than some random non-google page), but with banking sites and credit card forms you need to be careful.

[ Parent | on HN ]

Re:Harvesting credit card numbers and passwords from websites by pmlnr on Thursday January 11, 2018 @05:44AM (#16122796)

The trouble with the approach in the article is that by adding a npm dependency, it may as well be the script served by 1st party, buried in their react monster.

[ Parent | on HN ]