Details at a glance
These points distinguish the subject before the fuller explanation below.
| Aspect | Meaning |
|---|---|
| Secrets | Passwords, PINs and OTPs |
| Warning | A request you did not initiate |
| Device | Lock and updates |
| Response | Verify through a known route |
Warning signs and responses
Reusing a password across services can widen the effect of a breach. Keep passwords separate and change them when exposure is suspected. A password manager can reduce accidental reuse.
Match unfamiliar access or recovery messages to your own requests. Open your known route rather than a link inside the message. Record time and device details.
OTPs and PINs are confidential even when temporary. Do not give them to someone claiming to provide support. Urgency around a code is a reason to pause.
Responsibility for devices
Lock the phone screen and update its software. Do not leave saved credentials on a shared device.
If access is lost, inspect the contact account too. Changing one password may not be enough when the email account is compromised.
A practical sequence
Stop the interaction
Do not respond to a suspicious request.
Protect access
Change the password through your own route.
Preserve evidence
Keep the time and message wording.
Questions about Account security
Is a familiar link always safe?
A message using a familiar name can still be forged.
Should I give an OTP to support?
No, use the code yourself.
What if my phone is lost?
Secure access to the device and associated accounts.
What if activity looks unusual?
Record the time and seek security help.