Remember, that’s not a bug, that’s not a vulnerability, that’s an intentional feature. Stealing data it’s what lets the slop machines survive.
The fact that people give Claude access to their secrets is a big liability in the first place.
Even Claude itself warns you about it. I did shared a snippet of code with API keys in it by mistake, I got a huge warning telling me that I should consider these compromise and change them immediately.
Oh Claude, why you do me this way?
We’re trully entering a new Golden Age for hacking!
Why they’re blaming the tool instead of the user?
It’s the vibe coder’s fault if they don’t even watch the files edited in a commit.
Not only they approve a commit without reading the code, but they approve without watching the list of edited files in a commit? They don’t use vs code or something that shows a diff? Just type in a box and let the algorithm have full control on the commits, blindly?
But I was told we don’t need developers anymore because Claude can do everything.
Because the tool it’s inherently built to steal data.
So this is a pretty bad headline; it isn’t Claude Code sharing the secrets, it’s the user syncing their command history.
I’m sad we can’t get claude to share what it’s seen.
When a user chooses the “Yes, and don’t ask again” option to approve running a command, that choice gets stored as part of a rule in the local “.claude/settings.local.json” file on the user’s computer.
Saving privileged credentials in the clear in a config file? I think I can take credit for Claude doing that as this. Claude was clearly trained on my StackOverflow posts from 15 years ago.
Thank you for your critically important contribution.
Share no secrets, make no mistake
who are you, who are so wise in the ways of science?
Im gay
Checks out
That’s Doug
Mystery Science Doug? Daaaaamn. We got a celebrity here!
The irony is spectacular: a coding assistant designed to automate development also automates the creation of security liabilities. And Anthropic’s response seems to be more automation. Perhaps the next AI agent can monitor the first AI agent while a third one explains to management why the database credentials are now public.
Your comment instantly made my brain jump to https://downdetectorsdowndetector.com/
How do I know if they are both down or if it’s my internet?
Got you covered fam. https://downdetectorsdowndetectorsdowndetector.com/
Great news, there’s a down detector for the down detector’s down detector. They even have a down detector for the down detector’s down detector down detector
This is my point with AI. The risk is not that it will become something new, it’s that it will become like us.
I detected the sarcasm but I have to say it anyways : this won’t work as long all of them are built on the same technology which is inherently vulnerable for prompt injections
One is ultimately responsible for one’s output.
That happens with all AI tools! That’s why many people hate vibecoding apps. A developer that uses AI must strictly know about all these things.
It took me a little while to realise they just mean the tickbox you select to remember your password, rather than some special prompt being fed into Claude, along the lines of “make no mistakes” or “don’t hallucinate”.
