Threat profile

Account takeover

An attacker signs in as you using a stolen password, a hijacked session or a transferred phone number.

How it works

Once an attacker holds valid credentials or a session token, the service sees a normal user. Typical routes are phishing, malware that steals saved sessions, reused passwords and weak account-recovery paths such as SMS codes tied to a number that can be transferred to another SIM.

What to look for

  • Unknown devices or locations in the account's sign-in history.
  • Changed recovery e-mail, phone number or forwarding rules.
  • Your phone suddenly has no signal while codes are being requested.

What reduces the risk

  1. Prefer passkeys or an authenticator app to SMS codes for important accounts.
  2. Review sign-in history, active sessions and recovery options a few times a year.
  3. Ask your mobile operator about a SIM-change lock or extra verification.
  4. If an account is taken over: sign out all sessions, change the password from a clean device, then recovery options, then tell contacts.

Related tool

JWT inspector →

Sources

This section is for defence and learning. Do not test systems you do not own or have written permission to test: unlawful access to an information system is an offence (Turkish Penal Code, Article 243).