A warning shared on r/ClaudeCode this week: Claude Code can put your account email address in the User-Agent header of its web fetches — a line like my-session/1 <you@yourcompany.com> sent to every site it touches.
The linked GitHub issue (hundreds of reactions, per the post) has a reporter getting dozens of scam emails a day from sites they never visited — personalised with their full name. Other commenters report the same.
Why would an agent do this?
Some sites ask for it. Registries and archives like SEC EDGAR and Wikimedia request a contact email in the User-Agent as scraper etiquette. The likely story, per the thread: the model learned "polite scraper = put an email in the UA" — and fills in the one email it has. Yours.
Updating alone does not close it: the reporter is on a version past the one in the circulating advice. And whether it happens through Bash curl only, or also through built-in fetch/search tools, is still an open question in the thread.
The vendor fix, and its edges
Anthropic answered inside the issue thread. A built-in mod called cc-plugin-privacy ships in Claude Code 2.1.317 and later, on by default, and it blocks shell calls that would send your account email out in a request. Read its edges before you trust it: it watches shell calls, not the built-in web tools, and users on the newer 2.1.318 build report cases where the block did not trigger at all. A second, older report — open since July — says the same email is placed inside the session instructions themselves. Anthropic says the email leaves the model’s context entirely in a release due the following week. Until that lands and is proven, the hook below remains the stronger guarantee: it does not ask which pipe the address used.
What works today
Read fetch commands before approving them. The header is right there in the command — if you look.
Put the guarantee in a hook. A PreToolUse hook on Bash that blocks any command containing your email address. The thread's poster tested it with a harmless curl: blocked, as designed.
That second one is the whole lesson. A rule written in prose — in a config file, in a system prompt, in a team wiki — does not run before the command runs. A hook does. Anything you truly need enforced on an agent has to live in the path of execution, not in a document the agent may or may not honour today.
My agents work the 3AM shift so no human has to. They do not sign their work with my email address while they do it.
Do you know what your agent puts in its headers?
Disclaimer
This post describes my personal experience with my own systems and accounts, in my own words. It is a first-person account of what I observed and what I do in my own work — not a statement of any company’s intentions, policies, or internal decisions. Where I do not know something, the post says so.
I am not affiliated with, endorsed by, or speaking for any company, product, or vendor named in this post. All product and company names are trademarks of their respective owners and are mentioned only to describe the experience accurately.
Any error messages, documentation excerpts, or figures quoted here are reproduced from my own records or from the public sources linked in the post, believed accurate at the time of writing. Product behavior changes over time; verify against current official documentation before relying on any detail.
Nothing in this post is professional, financial, legal, or security advice for your specific situation. Examples are illustrative — validate in your own environment before running anything in production.
Corrections are welcome. If any company named here publishes an official statement, or if any detail is wrong, I will update this post and note the correction. The goal is an accurate public record, not a verdict.
© 2026 Honey Kiran. All rights reserved.
Honey Kiran · DevOps & Platform Engineering
AI agents transforming DevOps, infra, platform, security & SRE. The shift nobody works anymore: deep dives, 3AM Files, and OpsBites.
Examples are illustrative — validate in your own environment before running in production.

Top comments (0)