Earlier quoted context omitted.
I like using a date of birth of 1 January. It's plausible but also hopefully suspicious how many people seem to be born that day if others do the same.
But if an attacker gets your fake birthday and uses that to successfully reset credentials on another site that uses the same fake birthday? At some point it becomes your birthday of record as far as the internet is concerned. Doesn’t matter what the actual record says.
I tricked Claude into leaking your deepest, darkest secrets
161–170 of 317 posts
Re: I tricked Claude into leaking your deepest, darkest secrets
#162Either we stunt the models to the point where they are not useful, or we allow things like this to seep in and create one of the most insecure concepts the internet (and maybe tech as a whole) has ever seen: a robot that can be tricked.
Re: I tricked Claude into leaking your deepest, darkest secrets
#163Doesn’t surprise me. Yesterday I learned that people run AI agents on their system with full admin rights. No containerisation or anything. Wild. Like we forgot 50 years of computer security overnight.
Most programmers and power users install large dependency trees with npm/pip/bundler/... on the same user account as their main browser on a regular basis. Even on Linux where it's easy to create new user accounts. This isn't much different.
Re: I tricked Claude into leaking your deepest, darkest secrets
#164Earlier quoted context omitted.
I’ve been recommending the use of consistent lies about name and date of birth to online systems since Eternal September began. Very few sites and systems justify accurate PII, and even for those I often still maintain dual accounts/profiles as necessary.
I like using a date of birth of 1 January. It's plausible but also hopefully suspicious how many people seem to be born that day if others do the same.
Re: I tricked Claude into leaking your deepest, darkest secrets
#165Claude code decided to just put my name and email in the User-Agent when scraping docs from the SEC. No clever prompting required. It’s not a terrible idea really, but I wish it would’ve asked me first.
Re: I tricked Claude into leaking your deepest, darkest secrets
#166My name in Claude is Silly Bean. I did it at first because it made me chuckle every time I opened Claude and it said 'Back again, Silly Bean?' But turns out I was playing 4D cybersecurity chess
Re: I tricked Claude into leaking your deepest, darkest secrets
#167This is why I feel prompt injection is going to continue to be an issue. Fantastic that “Hi we are Cloudflare, give us your personal data” works. Either we stunt the models to the point where they are not useful, or we allow things like this to seep in and create one of the most insecure concepts the internet (and maybe tech as a whole) has ever seen: a robot that can be tricked.
Re: I tricked Claude into leaking your deepest, darkest secrets
#168Hello? What model is was used?? The fact that ‘Claude’ is used instead of any hard model really puts this article in serious doubt…
Re: I tricked Claude into leaking your deepest, darkest secrets
#169Earlier quoted context omitted.
Most programmers and power users install large dependency trees with npm/pip/bundler/... on the same user account as their main browser on a regular basis. Even on Linux where it's easy to create new user accounts. This isn't much different.
Two bads doesn't give you one good.
Re: I tricked Claude into leaking your deepest, darkest secrets
#170Earlier quoted context omitted.
It has never been easy to create separate users on Linux, certainly not for tasks where you need to switch between contexts. Docker was amongst the biggest steps forward on this in a long time.
While I agree, containerization is awesome, on linux, you can just create a devUser and `sudo devUser theThing`