Stupid me, I thought they somehow had hacked my company database or so... (considering all the cves, attacks happening on a daily basis...).
[–] crazygringo 2 days ago
[–] throwup238 2 days ago
[–] jchook 2 days ago
It is not.
[–] mk89 2 days ago
And to be honest, I don't even know which are they!
If I can find out I might be able to share them.
[–] weird-eye-issue 2 days ago
[–] j45 2 days ago
This is an awfully leaky issue.
[–] 00deadbeef 2 days ago
[–] baxtr 2 days ago
[–] y1n0 2 days ago
[–] skinfaxi 2 days ago
[–] post-it 2 days ago
[–] skinfaxi 2 days ago
[–] grey-area 2 days ago
[–] mk89 2 days ago
I burnt a few tokens to get some clarity on this (giving HN as source as well, so there is a reference to this thread):
> This doesn't appear to be Claude Code automatically attaching your email address to every outgoing request. The issue is that Claude has access to your account email in its context and can sometimes include it when generating HTTP requests (e.g. "curl" commands).
> Wikipedia and the SEC were mentioned because they explicitly ask automated clients to identify themselves through the "User-Agent" header, often with contact information. Claude may try to comply with those requirements by inserting your personal email address.
> That's why the leak is probably concentrated on sites with these policies, rather than happening on every website. But Wikipedia and the SEC aren't an exhaustive list (the EVE Online API was also mentioned), and there's no technical guarantee that Claude couldn't include the email in requests to other domains.
> The important distinction is that this appears to be model-generated behavior, not a networking layer automatically adding your email to all requests.
> So "most likely Wikipedia and SEC" is a reasonable hypothesis about where the leak is more likely to occur, not a confirmed limit on where your email could have been exposed.
I do see a lot of times curl being used (in Claude). I don't check all the websites being fetched (shame on me!), but your answer doesn't convince me.
My coincidence is clearly not proof. I am just a random online guy so why trust me. I just shared my recent experience. I used extensively copilot until roughly 3 weeks ago (I went all in on Claude, to try it out properly), and that's when I started to see a lot of spam on my work account. Coincidence? Yes. Correlation? Yes. Causation? No. And I personally don't care because I assume my work email account is somewhere to be harvested, but when I then see such a but report, it kind of rang a bell like WTF. I am as careful as possible about the requests I send, but I cannot remove the UA or know everything the harness is doing behind the scenes.
This type of bugs kind of kills the trust in the tooling. On the other hand, we're being told to use more and more such black boxes.
[–] weird-eye-issue 2 days ago
Usually this is from LinkedIn, GitHub, etc scraping... There are databases where they just guess and verify emails too
[–] gerdesj 2 days ago
The medical world uses the terms indications and contraindications. I think we in IT could do with a similar process/procedure.
[–] ruszki 2 days ago
For example, my only used by Claude email address doesn't get any spam at all.
[–] weird-eye-issue 2 days ago
It can take a while for spammers to get your address on their list. Generally the amount of spam over time only goes up. Just because there's a correlation doesn't mean there is a causation. Anyone with an email address, including on a custom work domain, has experienced this and Claude wasn't responsible for all email spam lol
[–] jntun 1 day ago
[–] soraminazuki 1 day ago
[–] weird-eye-issue 1 day ago
Sites aren't scraping their logs for email address in request headers and selling that to spammers. Getting emails to spam is already easy.
I have email addresses I literally don't use to sign up for anything and they still get spam because you can easily guess the address based on first name on LinkedIn plus the company domain. Spam has been a thing since email was invented.
[–] soraminazuki 1 day ago
There are numerous confirmed instances of websites asking to put personal information in the user agent string. And people here are downplaying, downvoting, or even denying that this issue exists. I am sick and tired of the relentless grifting that's overtaking the software industry.
[–] weird-eye-issue 1 day ago
I am a heavy user and I checked my logs and never once did it include my email in any sort of web requests. The chance that it actually included that person's email and then that led to them getting spammed is just incredibly low.
[–] paulddraper 2 days ago
98% I look at a LinkedIn profile, my $SALES_LEAD Chrome extension shows me their email + phone.
(To be clear, not from LinkedIn, but given their name/city/company.)
Claude Code is not sending your email address to websites as a default, or regularly. It is not some automatic header or anything.
Rather, if you are performing certain kinds of research on sites that involves downloading certain kinds of information, like on Wikipedia or the SEC, it supplies your e-mail address when the sites request it as part of their download policy. As part of anti-bot policy. Obviously Claude should have asked for approval first, but Claude isn't out there just spamming your e-mail address in every external request it makes or anything.
Wikipedia and the SEC are not selling your e-mail address to spammers. And these are the two main sites where it has come up.