Re:Tell HN: GitHub leaked names of private repos with pages
by edsrzf on Tuesday February 15, 2022 @12:32PM
(#30349694)
I find it bizarre that urlscan.io displays recent scans from paying customers. I assume GitHub is large enough that they have to pay, anyway. If they're not, who is?
[ Parent
| on HN ]
Re:Tell HN: GitHub leaked names of private repos with pages
by Shank on Tuesday February 15, 2022 @01:26PM
(#30350559)
From the URLscan pricing page [0], it looks like each plan has a tier of "private", "unlisted", and "public" scans. It looks like you're somewhat incentivized to just publicize all scans because that's the most economical. Based on what GitHub's email said, they've opted to scan things in public, probably assuming that the repos are public anyways. It looks like this assumption was a poor one to make, in this case.
Re:Tell HN: GitHub leaked names of private repos with pages
by jkingsman on Tuesday February 15, 2022 @12:36PM
(#30349761)
Oh man I thought this was gonna be just showing the TLD or something. There is a scrolling list of scans, down to the exact HTTP transactions. Just watched an OAuth grant roll by in plaintext. Yikes.
Re:Tell HN: GitHub leaked names of private repos with pages
by warp on Tuesday February 15, 2022 @01:13PM
(#30350369)
I saw an authenticated (!) zoom invitation, yikes indeed.
Re:Tell HN: GitHub leaked names of private repos with pages
by eproxus on Tuesday February 15, 2022 @01:27PM
(#30350577)
There are also screenshots on every scan page, for example unsubscribe links where the email is visible.
This site must be a treasure trove for spam harvesters.
Re:Tell HN: GitHub leaked names of private repos with pages
by wrs on Tuesday February 15, 2022 @01:00PM
(#30350190)
When you run a scan you specify whether it’s public, unlisted, or private. Can someone here explain the utility of non-private scans? (The urlscan.io folks apparently think it’s too obvious to explain.)