With a minor tweak on Haselton’s old trick, I was able to Google Credit Card numbers, Social Security numbers, and any other sensitive information of interest. After a month without a response, I notified them again to no avail. Not terribly alarming, but certainly alarming-so I notified Google, and waited. Soon-after, I discovered something alarming.
When you tried to Google a range like that, Google would serve up a page that said something along the lines of “You’re a bad person”.Ībout six months ago, while reminiscing with an old friend, this credit card number hack came to mind again.
#Visa credit card hack full#
By the way: here’s a full list of Issuer ID numbers.Īt the time, I didn’t think much of it, as Google immediately began to filter the types of queries that Bennett was using. For example, he could use “4060000000000000.4060999999999999” to find all the 16 digit Primary Account Numbers (PANs) from CHASE (whose cards all begin with 4060). In short, Haselton was able to find Credit Card numbers through Google, firstly by searching for a card’s first eight digits in “nnnn nnnn” format, and later using some advanced queries built on number ranges.
You could imagine my surprise when I saw Bennett Haselton’s 2007 article on Slashdot: Why Are CC Numbers Still So Easy to Find?. After all, our job was to protect our users’ data, to prevent it from being hacked, stolen or misused. At this point, I’m pretty intimate with Credit Cards (CCs), Credit Card hacking and web security in general. It’s safe to say that this wasn’t a job for the faint of heart. Part of my job was to make our provider PCI-DSS compliant-that is, compliant with the Payment Card Industry – Data Security Standard. At this company, our payment provider processed transactions in the neighborhood of $500k per day. If you know me, or have read my previous post, you know that I worked for a very interesting company before joining Toptal.
0 kommentar(er)
