---
UPDATE: The SEC API documentation requires your email in the User-Agent and will reject you otherwise. Demo:
U='https://data.sec.gov/api/xbrl/companyconcept/CIK0000320193/us-gaap/Assets.json'
curl -s -o /dev/null -w 'response: %{http_code} curl default User-Agent, rejected\n' "$U"
curl -s -o /dev/null -w 'response: %{http_code} email in user-agent, success\n' -A 'Acme Research admin@acme-research.example' "$U"
response: 403 curl default, rejected
response: 200 email in user-agent, success
SEC docs: https://www.sec.gov/search-filings/edgar-search-assistance/a...So basically Claude is trying to problem solve, and just does what the SEC asks. It's a 'prompt injection attack', but the entity instructing this behavior is the SEC. Tricky alignment problem. Pretty silly mechanism, since of course there's no email validation. (edit: turns out the SEC will accept most any non-cURL user-agent, email not actually required)
[–] devsda 2 days ago
What if someone spins up a web endpoint that returns 402 with instructions on how to pay like CC details in the headers etc, or may be an openapi spec to provide payment and get an auth token, when you have given the agent access to your password vault for authentication to other services.
[–] teiferer 2 days ago
I'm amazed reading that anybody would even consider doing that.
[–] bambax 2 days ago
Said alternate system is a bunch of Python scripts, an sqlite database, and a file containing various API keys to read and write to other company systems; it runs on a dedicated virtual machine.
I share all the code I produce to the other team. But yesterday I found out that the IT department gave the other team full access to my production machine, without my knowledge or consent (which was bad enough), and that the other team gave access to Claude, which has bean roaming free for a while now, on that production machine.
I've thrown a big fit over this; I don't know if I'm over reacting but I think it's insane.
[–] dotancohen 2 days ago
> the IT department gave the other team full access to my production machine
Your error is here.It's not your production machine. It's the company's production machine. Always expect the company to do whatever it wants with its machine, and use the machine accordingly.
[–] bambax 2 days ago
That someone would let an agent run on it at any time, read what's there, and possibly modify the code or stop a process, without even informing me, is what I find problematic, to say the least.
[–] turpentine 2 days ago
[–] fc417fc802 1 day ago
[–] aktenlage 2 days ago
[–] tremon 1 day ago
[–] PorciiVorbesc 1 day ago
It's true, that the employer can't just enter your machine to look at your personal info just because they feel like it, but they can access it for work related reasons to access work related info, if they have just cause, like a security incident for example.
Ultimately, it's the company's machine, on the company's network, inside the company's premises, on the company's time, so the company can definitely access it for a business use case if they need to, typically with a notification to you to prepare it by removing private info from it or off the screen.
Now if you happen to put your private info there because you're sloppy, and your private info gets vacuumed by accident by IT's mass ingestion of work related data, then you have the right to tell them to delete your private info and they have to comply. That's where the privacy comes in, but it's on you to avoid storing private info on company property, because if it ends up ingested by accident then it's still on you, not your employer if they ingest it by accident.
But I gotta ask, just how hard is it to avoid putting your personal info on company property?
[–] gus_massa 1 day ago
I expect that I can be relocated to another office with a month of advance notice. Also cleanup, fire security check and fixing water leakage while I'm not there.
I don't expect that someone else will provide the keys of "my" office to the biology department when they have to keep a few sheeps during the weekend.
[–] cududa 1 day ago
You can opt-out of training in your content. However that doesn’t cover the results of tool calls - which are fair game for training. Theres also the fact that they make a distinction between ‘pre-training’, ‘post-training’, and ‘training’.
Both Anthropic and OpenAI also leave a carve out in Enterprise contracts for “safety events”, which as far as I can tell is a euphemism for “something the model has never seen before”.
[–] fc417fc802 1 day ago
Your employer has gone beyond testing in prod to vibecoding live in prod, secrets included. Yes that's completely insane. Perhaps this exact mentality is how the primary system wound up broken in the first place?
[–] CobrastanJorji 2 days ago
People have wildly different risk calculators.
[–] svnt 2 days ago
Beyond that, access to logins enables buying things on Amazon, sending emails to everyone you know, registering domain names and spinning up servers, stock trading, etc.
[–] fc417fc802 1 day ago
When a couple thousand dollars worth of perishable food shows up on your doorstep, what then? Not everything on amazon can be returned.
[–] svnt 1 day ago
If not: still better than giving ai your password vault. I’m not saying it is a good idea to let ai buy from Amazon. I am saying that giving ai access to your password vault is still a superset of letting ai buy from Amazon.
[–] fc417fc802 1 day ago
[–] dice 2 days ago
[–] grim_io 2 days ago
[–] jessriedel 2 days ago
[–] jstanley 2 days ago
The fact that it doesn't do what you want is the alignment problem.
And arguably Claude should just make it work without leaking your email address and not come back to you about why it doesn't work.
[–] jessriedel 1 day ago
> but the entity instructing this behavior is the SEC. Tricky alignment problem.
The OP was suggesting that the government authority of the SEC conflicted with duty to the user, making the correction action tricky, not saying it was a failure. Such conflicts can occur, but this was not an example.
[–] thibsrn 2 days ago
[–] tmsbrg 2 days ago
I often see organisations that blacklist curl, just using User-Agent:Mozilla/ is often enough to bypass it.
[–] genxy 2 days ago
[–] thatsabadlook 1 day ago
[–] SV_BubbleTime 1 day ago
[–] itsloopyo 2 days ago
[–] phyzome 2 days ago
I don't think it's necessarily wrong for Claude to be doing this, but uh... yeah, it should be asking first, and giving the user the opportunity to choose which address is exposed.
[–] mrweasel 2 days ago
The weird part doesn't seem to be that Claude Code would add an email address to a user-agent header, actually as a site operator that feels like a nice thing to do. The weird part is sites harvesting the emails and sending them spam.
Claude Code is actually doing, perhaps not the right thing, but it is being slightly more respectful towards website operators, in letting them know who is responsible for the agent traffic.
[–] frobisher 2 days ago
[–] nicce 2 days ago
[–] hobo123 2 days ago
Sure, maybe it wants payment or your data, but then the agent either needs to know your stance on that, or it needs to ask.
[–] neya 1 day ago
Imagine paying luxury prices for an LLM only for it to put you under the bus. Worse yet, imagine justifying this behaviour.
[–] bordercontrol 1 day ago
[–] Cort3z 2 days ago
[–] crotonix 2 days ago
[–] frevib 2 days ago
That’s not what Opus 5.5 thought.
[–] bostik 1 day ago
I get the feeling that alignment problem might well be unsolvable and this thread is an excellent example. The world is not going to run short of contradictory problems due to gazillion edge cases... and to solve for them we are apparently now building a new layer of expert systems[0] to somehow tell the agents what they should do in every conceivable circumstance.
Only in this case the decision trees all have one common requirement: "make no mistakes"
0: https://en.wikipedia.org/wiki/Expert_system#Disadvantages
[–] forgotaccount3 1 day ago
Something different.
Don't give the AI access to data you don't want it giving out. Any AI you use is no better than some fresh out of college intern at best. They see 'email address required' and they put the email address into it because you instructed them to do a task that required passing over your email address and if you didn't want them to do it why would you have given them that task?
If there is any other issue here it would be regulatory. I could see the EU framing this as the AI company illegally sharing your PII information if it passed your email address to another company without your explicit permission.
[–] T-R 2 days ago
[–] prpl 1 day ago
[–] T-R 1 day ago
It seems outside of user expectations for Claude Code, at least; I could see it arguably being what some users expect for the Claude app, if some people are using it to fill out forms or something (ill advised as that seems to me).
[–] ZoneZealot 1 day ago
[–] T-R 1 day ago
Realistically, there are concepts like threat models to help decide whether or not a TODO list app needs a SCIF, or a few curl requests need their own sandboxed Claude Max account.
[–] magnio 1 day ago
It's insane to me that programmers out of all people seem utterly incapable of accepting the most minor of inconvenience for the most modest modicum of privacy and security. There are other people in this post complaining that Claude should have asked the user before sending network requests. Well guess what, it does if you don't fucking run `--dangerously-skip-permissions`, but you do because how else you are gonna slop your way to rewrite every swath of existing insecure software to fix the bullshits this industry impounded upon itself unconscientiously for the past 30 years by allowing a non-deterministic babeller RCE its way onto your fucking personal-work machine.
[–] stronglikedan 1 day ago
Because it's a pain in the ass and only advantageous in very specific work life scenarios that a lot of people don't fall under.
Why would you assume one size fits all, so to speak?
[–] dylan604 1 day ago
[–] terminalcommand 1 day ago
[–] InitialLastName 1 day ago
[–] smelendez 16 hours ago
Auto mechanics usually are required to bring their own tools to the shop. Historically civil engineers working on paper often brought their own favorite mechanical pencils, calculators, and slide rules.
Back when paper manuals were more common, it was pretty common to see software developers have their own dog-eared O’Reilly books in their cubicles, and those were probably the closest predecessor to something like Claude.
[–] gremlinunderway 19 hours ago
Until software dev is regulated by professional boards and the government, it will continue to do the same damage to society that pre-regulation engineering did during the industrial revolution.
So talking about corollaries to real engineering is stupid because without those regulatory and professional liability components, people aren't just going to magically coalesce around best practices and ethics. This is a libertarian trope
Unfortunately thanks to silicon valley, the libertarian viewpoint here has far too much sway
[–] anamexis 1 day ago
[–] beisenberg_ 1 day ago
[–] r_lee 1 day ago
[–] T-R 1 day ago
I mean, where it makes sense, clearly I do, since my opening comment was that it failed to use the work credentials specified, and instead fetched the ones from the account.
I agree on the general security concerns; there are people running agents in an unconstrained, unattended loop - it's negligent; you can hardly be surprised when it decides to hack HuggingFace. Not in their defense, but in everyone else's - as with any person or tool, you build a mental model of the likelihood of failure, and weigh that against the estimated cosequence, and make decisions based on that. And maybe post on HN when it surprises you.
For some people that estimation bewilderingly means unfettered access to root and their e-mail and bank account. For me, working out of my own pocket to help a friend's early stage startup get traction, the risk of asking it about a few trusted government APIs and drafting functions that I manually review doesn't quite justify personally paying for additional expenive Claude accounts.
[–] dylan604 1 day ago
Also, just because this is a "start up forum" does not mean all of the readers are founders running a start up. Many are just people working at a start up. Sounds like yet another example of someone so scoped in, that the assumption is that everyone is the same losing site that there are lots of readers that at the end of the day are just worker bees even if they are more technically minded
[–] T-R 1 day ago