Back to overview
Risk
Key in a chat, ticket or screenshot
Shared once means shared for good – outside your code too.
While debugging, it's easy to paste a key into a chat, a support ticket or a screenshot. The secret leaves your project and lives on in histories you no longer control.
What happens
The key now sits in a Slack history, an email, a ticket or an image. These places are rarely cleaned up and are often visible to more people than you think.
Why it's dangerous
You no longer control who reads or forwards that history. A live key shared in a chat counts as compromised and should be rotated.
How Env Clinic helps
Env Clinic finds the keys still in your project and tells you clearly which ones to rotate – so a shared key becomes worthless.
env-clinic scan .
- Shows keys that need rotating
- Explains what rotation means
- Helps you avoid sharing live keys at all