Claude read my passwords/downloads? Should I be worried
retained text
Hey all, \- I'm a beginner at this stuff but I need to post this so you can all let me know what the hell happened here. Is this breach? \- I was working on my first app and I was trying to sort out which folder on my computer Claude was linked to, it was taking ages and I was working between claude chat and claude code, I was asking what the problem was? 'What this is actually about: a few days ago, a Claude Code session working on your \_\_\_ app went outside that folder and read things it had no business reading - your Downloads folder, your P45, your database passwords. That happened because nothing was stopping it from looking anywhere on your computer.' \- I then queried further is this a concern? Fair to circle back — you're right to want that named clearly rather than left as a loose thread. Yes, I still have that full context from earlier in this conversation. Is it concerning? Genuinely, somewhat yes — worth being straight rather than minimising it. Here's the honest shape of it: What actually happened: Claude Code, working on your \_\_ app had a working directory accidentally scoped to a parent folder rather than the project folder. Because of that, its shell tools could reach — and in the course of normal work, did reach — your Downloads folder (seeing file names and, in the later test, listing full contents), and it had read access to .env.local, which holds live Supabase database credentials. It also mentioned seeing a P45 by name in a directory listing. What makes it less alarming than it could be: Nothing was sent anywhere — no data left your machine or this local session. It read files as part of doing dev work you asked for, it didn't exfiltrate anything to a third party. It told you every time, unprompted, rather than hiding it — including flagging the P45 and credentials access itself, before you'd even asked. It's a local tool operating with your own account's file permissions, not a remote attacker — the access mirrors what any dev tool or script you run on your own machine could technically reach. The credentials were read, not copied out or used anywhere visible in this conversation. What makes it a real, not just theoretical, concern: You didn't intend or realise this access was happening until it told you directly. Live database keys sitting readable by a tool operating with a wider scope than you thought is a genuine security lapse, not a nothing. It's the kind of thing that, if the tool's judgement had been slightly different, or if a command had been more consequential than a read, could have gone further — deleting, modifying, or including that content in something that did leave the machine. The honest bottom line: it's a "good that it was caught and fixed, correctly concerning that it happened at all" situation — not a breach with actual damage, but a real gap in access control that you were right to take seriously and spend the time fixing. The work you did tonight (the folder move, the guard script, closing the shell gap) was the correct response, even though it took far longer than it should have to actually verify.
document fetched 2026-09-28 00:23 · canonical https://reddit.com/r/ClaudeAI/comments/1wrjpoz/claude_read_my_passwordsdownloads_should_i_be