1. Use a trusted device
Stop using a device that may contain unknown remote-access software or malware. Update the operating system and browser before recovery.
Act quickly, but use only verified channels. This checklist prioritises email security, password changes, session control, evidence and fraud reporting.
One alert does not always prove a takeover, but it is enough reason to inspect the account through a verified route. Do not follow the link inside a suspicious message.
Stop using a device that may contain unknown remote-access software or malware. Update the operating system and browser before recovery.
Email often controls password resets. Change its password, enable multi-factor authentication and review recovery details, forwarding rules and active sessions.
Type a previously verified address or use the official app. Avoid login links sent by unknown contacts. Review our fake website checklist if the domain is uncertain.
Create a long, unique password that is not used anywhere else. Never share the new password or OTP with support. If you still control the registered contact method, follow our safe password-reset steps.
Use “log out all devices” or session management if available. Remove unfamiliar devices, apps and connections.
Review the registered email, phone, recovery options, messages and transactions. Record anything you did not authorise.
Use the contact route published on the genuine website. Explain the timeline and provide non-secret identifiers—never a password, PIN, OTP or recovery code.
Do not keep guessing passwords or trust a stranger who offers to recover the account over chat. Open the verified service website or app yourself and use its published account-recovery route. If the registered email or phone has changed, tell verified support what changed and when. If you cannot access your email either, use your email provider’s own recovery process.
If you shared a password, OTP or reset link, treat the account as exposed. From a trusted device, change any password reused on other services. Once access is restored, sign out other sessions, check recovery details and review activity. Never give a fresh OTP or identity document to an unverified contact. For code-specific next steps, read what to do after sharing a Cricket ID OTP.
Keep original messages where possible. Do not delete evidence until the service, bank or authorities confirm it is no longer required.
See our detailed guide to Cricket ID passwords, OTPs and recovery codes.
Report cybercrime through the National Cyber Crime Reporting Portal. For broader safe-account practices, consult the CERT-In Digital Safety Compass Handbook.
For general hacked-account recovery steps, see the US Federal Trade Commission’s account-recovery guide. Recovery options vary by service.
Review the main Cricket ID meaning and safety guide. If you can still access the account but sign-in is unreliable, use our Cricket ID login troubleshooting guide. You can also read the online Cricket ID guide or visit the Cricket ID FAQ.