Cybersecurity firm CYFIRMA has reported on the re-emergence of an active and evolving phishing campaign targeting users of the Telegram messaging application. The operation is designed to hijack user accounts by cleverly abusing the platform's own legitimate device authorization feature. Attackers use social engineering to lure victims with fake security alerts, guiding them to a malicious interface that triggers a real login prompt within the victim's app. If the user approves the request, they unwittingly grant the attacker full access to their account session. This allows the threat actor to read messages, access contacts, and impersonate the user, highlighting a significant risk from attacks that exploit user trust in familiar UI elements.
This campaign is particularly insidious because it doesn't rely on stealing a password directly. Instead, it tricks the user into performing the exact action needed to authorize the attacker's session, making it appear as a legitimate security procedure.
The attack unfolds through several social engineering steps:
The Lure: The attack begins when a user receives a phishing message, either within Telegram or via another channel like email or SMS. The message is designed to create a sense of urgency, typically warning of an "unauthorized login attempt" or stating that the user's account needs to be "verified" for security reasons (T1566).
The Malicious Interface: The message contains a link that directs the user to a phishing website or a malicious Telegram bot. This interface is carefully crafted to look like an official Telegram service page.
The Trick: The malicious site/bot, having obtained the user's phone number, initiates a legitimate login attempt for a new device. This action triggers Telegram's standard security procedure: a login confirmation prompt is sent to all of the user's already-active devices (e.g., their phone or desktop app).
User-Assisted Compromise: The phishing site instructs the user to approve the prompt that has just appeared in their app to "secure their account" or "cancel the unauthorized login." The user, believing they are taking a corrective security action, presses 'Approve'.
Session Hijacking: By approving the login, the user has authorized the attacker's device, granting it a valid, active session token. The attacker now has full access to the account (T1539). They can read all non-secret chats, view contacts, send messages, and exfiltrate any accessible data.
Settings > Devices (or Privacy and Security > Active Sessions). Any unrecognized devices or locations should be terminated immediately.Privacy and Security settings. This requires a password in addition to the SMS code for any new login. Even if an attacker tricks a user into approving a session, they will be stopped by the password prompt, which they do not know.The most critical mitigation is training users to recognize social engineering and to never approve a login prompt they did not initiate.
Enabling Telegram's Two-Step Verification (cloud password) acts as a second factor that the attacker cannot bypass, even if they trick the user into approving the initial session.
The most effective technical countermeasure against this Telegram phishing attack is for users to enable Two-Step Verification within the app's settings (Privacy and Security > Two-Step Verification). This feature requires the user to set a permanent password (a 'cloud password') that must be entered for every new login, in addition to the standard code sent via SMS or in-app prompt. This control directly thwarts the described attack. Even if the attacker successfully tricks the user into approving the malicious device's login prompt, they will be immediately challenged for the cloud password, which they do not possess. This second factor prevents the session from being fully established and blocks the account takeover.
While typically applied to enterprise domains, the principle of account monitoring is directly applicable here for user self-auditing. Telegram users must be educated to regularly monitor their own 'accounts' by navigating to Settings > Devices. This screen provides a list of all active sessions, including the device type, location, and last active time. Users should be trained to treat this screen as a critical security dashboard. Any device or location that is not immediately recognizable should be considered suspicious and terminated using the 'Terminate Session' button. This proactive self-auditing allows users to detect and evict an attacker who may have successfully hijacked their session, limiting the window of opportunity for data theft or impersonation.

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.
Help others stay informed about cybersecurity threats