Help for owners
A password or API key was sent in a chat or an email
Short answer
Treat any key or password that was typed into chat or email as known to everyone who can read that history, now and later. Deleting the message does not undo it. Replace the key at the service that issued it, then agree one safer way to hand secrets over.
Does this sound like your situation?
- A developer asked for the login and it was pasted into a chat or emailed.
- A search in the shared inbox or channel shows passwords or keys.
- A contractor still has access to a channel that contains old keys.
- I cannot say who has seen a key, or who is using it right now.
- The same key is used by the app, the developer and a test setup.
Why does this happen?
Chat and email feel private, but they are archives
Messages are kept, searched, forwarded, backed up and visible to every present and future member of the channel or mailbox. A secret pasted once is stored in many places.
It is the fastest way to unblock someone
When a deadline is close, the quickest path is to paste the key. Nobody sets up a proper hand-over because nothing forces it.
One key serves everything
A full-access key shared by several people and apps cannot be traced back to the person who leaked it, and it is hard to replace because many things break at once.
Good practice is to limit who can read secrets
OWASP's secrets guidance says secrets should be given only the minimum privileges needed, access to read them should be restricted and monitored, and exposed secrets should be revoked and rotated right away.
Confirmed by cheatsheetseries.owasp.org
What can I do about it today?
- List which secrets were sharedSearch the chat and the mailbox for words like key, password, token and secret. Write down what each one opens, but do not copy the values into a new message.
- Replace the most powerful ones firstPayment, database, cloud and email-sending keys come before low-risk ones. Replace them at the service that issued them and give the new one only to the person who needs it. Ask whoever runs your systems to update the app, so nothing breaks.
- Do not just delete the messagesDeleting does not take the key back. Replace first. Afterwards you may remove the messages.
- Review who is in the channel or can read the mailboxRemove people who no longer work with you. Do this after the keys are replaced, not before.
- Agree one place for secretsA password manager or the hosting service's secrets store, where each person has their own login. Tell everyone that keys are not to be sent by chat or email from now on.
- Check the billing and usage pagesLook for unexpected charges or activity at the services whose keys were shared.
When should I bring someone in?
- You do not know what a key opens or what will stop working when it is replaced.
- Billing or usage shows activity that nobody on your team can explain.
- A key for payments, customer data or cloud servers was shared.
How do I handle it?
- Inventory the secretsI find every key and password that was shared and note what each one opens and who uses it.
- Replace in the right orderHigh-impact secrets first. Each replacement is done with the app and its deploy updated in the same step, so the product keeps running.
- Check the old key's useWhere the service shows key usage, I look for calls from places that should not be using it and report what I find.
- Give each person and system their own accessSeparate keys with the smallest rights they need, so that one leak is one key to replace and it can be traced.
- Set up the hand-over habitA simple written rule and a place for secrets, so that the next new developer gets access without a chat message.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
If I delete the Slack or email message, is it safe?
No. Copies may exist in search indexes, exports, backups and other people's inboxes. The only safe answer is to replace the key.
Do I have to replace every password?
Replace first what could cause real harm: money, customer data, servers and email sending. Lower-risk ones can follow in a planned order.
Is sending a password in a separate message safe?
It is better than nothing but still leaves the secret in the history. A password manager with a shared vault is the cleaner way.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.