A password lands in the wrong chat or becomes visible during screen sharing. Even if the message is removed quickly, you cannot reliably establish who already saw or saved it. Treat the credential as exposed. Respond methodically: secure the affected account, check other possible uses, and change the surrounding process so the same mistake is less likely to recur.
Secure the affected account directly
Open the known official website or app and change the password in account settings. Use a new unique credential rather than a minor variation of the old one. Save it in the intended password manager and verify successful sign-in. For a managed work account, follow the internal process.
If exposure involved a suspicious file, remote-control session, or imitation website, the device may also be affected. Make important changes from another trustworthy device and use the designated security contact. Replacing the password inside a possibly compromised environment does not address every cause.
Review reuse and existing access
If the password was reused elsewhere, those accounts need their own new credentials too. Prioritize important accounts such as email and password management because they may influence other recovery routes. Track which accounts have actually been addressed without putting new secrets into an exposed task list.
Review active sessions, connected applications, and recovery details for the affected account. Changing a password does not automatically end every session or integration at every service. Use the intended sign-out or revocation controls and investigate unfamiliar changes. Google includes this review in its process for securing a potentially compromised account.
Limit exposure without assuming recall
Remove the message or file where you control it, and notify the responsible person if a shared or work account is involved. Do not expose the password again in a lengthy explanation. Identify the account and incident without repeating the secret.
A recipient's confirmation of deletion may help, but it does not replace changing the credential. Copies, notification previews, or screenshots cannot be reliably recalled. End the exposed credential's validity rather than waiting for proof that every possible copy has disappeared.
Change the process that caused the mistake
For shared tasks, limited roles or file permissions are usually easier to control than distributing a primary password. If a secret genuinely needs to pass between authorized people, use an appropriate protected method with limited scope. Also consider whether future screen sharing can be restricted to one window.
Enable or review additional sign-in factors and an independent recovery route. These do not retroactively make the exposure harmless, but they can strengthen subsequent access. Briefly record the incident and review relevant security alerts afterward. The goal is an account brought into a verifiably safer state, not merely removal of the visible mistake.