Dataset for sale: [redacted]<p>Similar data structure: <a href="https://stackblitz.com/edit/angular-soswe4?file=src%2Fapp%2Fapp.component.ts" rel="nofollow">https://stackblitz.com/edit/angular-soswe4?file=src%2Fapp%2F...</a><p>Owner works for: <a href="https://covve.com" rel="nofollow">https://covve.com</a><p>Covve: This simple yet state-of-the-art app will revolutionise your business relations like you've never seen.<p>Edit:
Response: <a href="https://twitter.com/covve/status/1261287954967941120" rel="nofollow">https://twitter.com/covve/status/1261287954967941120</a>
Hi all, Alex here, CTO at Covve. Just got alerted of incident db8151dd in . We’re investigating as top priority with our security experts what relation this may have with Covve. We are monitoring the feedback in this blog and would really appreciate any additional information you may have on this as we investigate (alex@covve.com).
Troy's fighting the good fight, but it's so freaking depressing. If he has hundreds of millions of records worth of personal data from just the breaches that have been shared with him, what _else_ is out there in the hands of criminals and corporations, neither of which have the public interest at heart—only naked self interest in exploiting members of the public for as much money as they can get?
For the people that use unique per-merchant e-mail addresses (like someone+amazon@...), could you try some of those aliases on HaveIBeenPwned and see which ones come up in this breach? That might shed some light onto its origin.
> Why load it at all? Because every single time I ask about whether I should add data from an unattributable source, the answer is an overwhelming "yes"<p>To be fair, you’re asking your followers on twitter. That’s as biased as you can have, I would be really surprised if the majority would say no.
Could it be Google+? 3 of 3 my Gmail addresses associated with their profile in some way were on it. Two of it I might have used to register a domain, but the last one I used for G+ and one other website only and none of any friends know this. Also I'm not in US or have US background, can't be from American friends' phones or retailer CRM.
> Recommended by Andie [redacted last name]. Arranged for carpenter apprentice Devon [redacted last name] to replace bathroom vanity top at [redacted street address], Vancouver, on 02 October 2007.<p>Given that, surely Troy can contact those people and ask "who knew this info?". Not many people would know who replaced my bathroom vanity top...
I use a unique email on my personal domain for everything I sign up for.<p>The email contained in this breach is the one I provided to Facebook. It was probably hacked or sold from one of the handful of apps I've connected with FB over the years.
One of my emails is currently on:<p>"Pwned on 19 breached sites and found 5 pastes.<p>If this is public breaches, I would guess in reality I can probably assume it's on double/triple that for sites that have been breached but the data hasn't been posted online.
I don't really get the utility of HIBP. The answer to the "have I been pawned?" question is, of course, yes, multiple times. I think about the only way to keep your email out of the hands of the bad guys is to not use it or give it to anyone ever, at which point you don't need an email address.<p>What am I supposed to do whenever I'm involved in a new breach? Burn all my accounts and start again?
Is this dump online anywhere? I got the notification from HIBP but it only tells me my email address appeared and I'm curious how accurate the rest of the data is.
> <i>Email addresses, Job titles, Names, Phone numbers, Physical addresses, Social media profiles</i><p>I just got the email notification from HIBP (Have I Been Pwned) a few minutes ago [1], but I am not worried about the compromised data because 1) my personal email address, job title and phone number are all visible in my resume which is publicly available in my website, I actually encourage people <i>—mostly tech recruiters—</i> to download the PDF and contact me via email or phone all the time and 2) my physical address is irrelevant because I have been moving houses every year for the last seven (7) years (even across countries a couple of times. All the social media accounts I have are completely empty, I just keep them around to get a hold on to my nickname.<p>I recently found, in my website’s HTTP logs, several requests from a web crawler controlled by ZoomInfo [3] an American subscription-based software as a service (SaaS) company that sells access to its database of information about business people and companies to sales, marketing and recruiting professionals. I was going to configure my firewall to block these requests but then I remembered <i>—hey! my website only has information I am comfortable sharing, so it doesn’t matter—</i> but I’ve been thinking it is just a matter of time before someone hacks one of their systems and leaks their database.<p>In my previous-previous job I found a fairly simple (persistent) XSS vulnerability in BambooHR that allowed non-authorized users to access data from all employees registered in the website including Social Security Numbers (SSN). I told my boss and we immediately edited everything before migrating to a different system. We never knew if BambooHR fixed the vulnerabilities and I wouldn’t be surprised if the data was leaked before or after I found the security hole.<p>Software security is such a Whac-A-Mole game, even if you get the budget to conduct security audits on your code, there is always going to be a weak link somewhere in the chain and that will be your doom. This is one of the many reasons why I left that job as a Security Engineer, the other reasons were Meltdown [3] and Spectre [4] they both made me realize I was fighting for a lost cause.<p>[1] <a href="https://haveibeenpwned.com/NotifyMe" rel="nofollow">https://haveibeenpwned.com/NotifyMe</a><p>[2] <a href="https://en.wikipedia.org/wiki/ZoomInfo" rel="nofollow">https://en.wikipedia.org/wiki/ZoomInfo</a><p>[3] <a href="https://en.wikipedia.org/wiki/Meltdown_%28security_vulnerability%29" rel="nofollow">https://en.wikipedia.org/wiki/Meltdown_%28security_vulnerabi...</a><p>[4] <a href="https://en.wikipedia.org/wiki/Spectre_%28security_vulnerability%29" rel="nofollow">https://en.wikipedia.org/wiki/Spectre_%28security_vulnerabil...</a>
Based on a large (over 50 results) domain search for a company I work for, the data I found was very old, circa 2014.<p>I know this because almost everyone in the domain search stopped working for the company on or after 2014. Everyone else has worked at the company since 2013 or earlier.
I did some quick searching for the dataformat included in the snippets from the article. Lots of repos with stored secrets that match:<p><a href="https://github.com/acalvoa/SRID_CHANGER/blob/da367e68433b3fd8a3a04e679e3d74b45bc051e3/src/de/micromata/opengis/kml/v_2_2_0/xal/AdministrativeArea.java" rel="nofollow">https://github.com/acalvoa/SRID_CHANGER/blob/da367e68433b3fd...</a><p>Stored secret:<p><a href="https://github.com/acalvoa/SRID_CHANGER/blob/master/config.properties" rel="nofollow">https://github.com/acalvoa/SRID_CHANGER/blob/master/config.p...</a><p>Will look more into this later
Some emails that turned up on my end: Dr. Dobbs and New Relic, although the leaks occurred from parties to whom these sites had provided my data, including at least unique email addresses.
Question: It was my understanding that a lawyer could sue the cloud provider for customer details of the cloud service in detail? It would be relevant information in determining liability for leaking this PII.
Firefox Monitor includes the db8151dd data: <a href="https://monitor.firefox.com/?breach=db8151dd" rel="nofollow">https://monitor.firefox.com/?breach=db8151dd</a>
what I can't understand is that I never heard of this covve app neither most of the affected users in the comment section on reddit or troy website or even here as no one thought of it , and my email does exist on the breach, also the data seem to be huge (103,150,616 rows/90GB)for an app that have about 100k install, need some explanations here.