Home / Bug Bounty & Vulnerabilities / Kaspersky Warns of WebRAT Malware Exploiting New Telegram Widget Vulnerability

Kaspersky Warns of WebRAT Malware Exploiting New Telegram Widget Vulnerability

Cybersecurity researchers at Kaspersky have issued a stark warning regarding a critical security vulnerability discovered within Telegram’s recently launched "widgets" feature. According to the security firm, this flaw has been actively exploited in the wild to facilitate the delivery of WebRAT, a sophisticated piece of malware. The disclosure comes amid a flurry of public scrutiny regarding the security architecture of the platform’s latest feature, which was designed to allow any message to function as a standalone application.

In a formal advisory published on November 13 via its Russian-language Telegram channel, Kaspersky detailed its observations of malicious activity that it believes is directly linked to this widget vulnerability. The firm noted that the exploitation mechanism appears to be triggered when unsuspecting users interact with specific Telegram channels. Once a user visits these compromised channels, the malicious widget initiates a background process that executes a PowerShell script without the user’s explicit knowledge or consent.

This script acts as a delivery vehicle, fetching and subsequently launching WebRAT—a malicious program also identified by security analysts as "Salat Stealer." WebRAT is a Rust-based trojan designed to grant threat actors comprehensive, remote control over an infected system. Beyond merely compromising the device’s integrity, the malware is capable of exfiltrating sensitive information, including data from cryptocurrency wallets and private Telegram account credentials.

While Kaspersky has confirmed the existence of this threat, it has remained cautious regarding the technical specifics of the exploit, as well as the scope of the campaign. The firm has not disclosed the precise number of users targeted or affected by the malware. Consequently, Kaspersky’s primary recommendation to the Telegram user base remains unequivocal: users should refrain from launching or interacting with any widgets within the Telegram platform until an official security patch has been released and verified.

The controversy surrounding these widgets began shortly after Telegram CEO Pavel Durov touted the feature on X (formerly Twitter) on November 10. In his post, Durov emphasized the versatility of the new functionality, stating that "any message on the platform can now become an app," a claim that drew immediate attention from the cybersecurity community.

The potential for abuse was highlighted just one day later, on November 11, when security researchers at V12 published a video on X demonstrating a remote code execution (RCE) exploit. The video provided a stark visual of the vulnerability in action: by interacting with a specially crafted bot, the researchers were able to trigger the Calculator application on an Android device, a classic proof-of-concept for demonstrating that a remote party can force a device to execute arbitrary commands.

Telegram responded to the initial reports with relative speed, asserting on the same day that the Android-specific issue had been addressed. The company claimed that the vulnerability was fixed and the update had been deployed to the entire user base within hours of the discovery. However, the situation escalated further when the V12 researchers released a follow-up video. This second demonstration showcased a different RCE exploit that remained effective against the supposedly patched version of the Telegram client for Windows.

The core of the researchers’ concern lies in the architecture of the platform’s new feature. They argue that by allowing QuickJS—a lightweight, embeddable JavaScript engine—to run directly within messages without a robust, isolated sandbox, Telegram has inadvertently created a massive and highly dangerous attack surface. In their view, the design choice to prioritize functionality and seamless app integration over rigorous security isolation is what allows these RCE exploits to thrive.

The public debate reached a zenith on November 13, when Pavel Durov directly addressed the mounting criticism on X. In a dismissive tone, Durov rejected the characterization that the platform was inherently vulnerable to such attacks. "No one could be hacked just by receiving a message," he wrote, attempting to clarify the nature of the exploit. According to Durov, the malicious activity identified by researchers and security firms required the user to take the affirmative step of starting a third-party service. He maintained that the scenario described by critics had already been fully patched on the server side, effectively nullifying the threat for the average user.

Durov’s response went a step further, as he challenged skeptics and researchers to attempt to hack his own account, signaling a high level of confidence in the platform’s current security posture despite the ongoing warnings from firms like Kaspersky.

The tension between Telegram’s rapid innovation cycle and the demands of platform security is a recurring theme in the tech industry. As Telegram continues to expand its ecosystem into a multifunctional "super-app," the complexity of its codebase increases, potentially introducing new vulnerabilities that are difficult to anticipate during the development phase. The current situation involving WebRAT serves as a reminder of the risks associated with features that blur the lines between content delivery and executable code.

The incident is part of a broader landscape of cyber threats, where attackers frequently leverage new, unrefined features in popular software to bypass traditional security controls. Other recent examples of such exploits include the ongoing exploitation of the UnrealIRCd vulnerability, critical flaws found in Xen Orchestra, and a high-profile zero-day exploit targeting Microsoft Outlook. Each of these instances, much like the Telegram widget situation, underscores the critical importance of secure development practices and the necessity of rapid response protocols when vulnerabilities are discovered in widely used software.

As of the time of this report, the cybersecurity community remains vigilant, monitoring for further indicators of compromise related to the WebRAT malware. While Telegram maintains that the server-side fixes are sufficient, the discrepancy between the platform’s claims and the findings of independent researchers like those at V12 suggests that the debate over the safety of the widget feature is far from settled.

SecurityWeek has reached out to Telegram for a detailed comment regarding the specific claims made by Kaspersky and the ongoing concerns regarding the QuickJS implementation. At this stage, the company has not provided additional technical details or a comprehensive response to the claims regarding the Windows client vulnerability. The situation remains fluid, and security analysts continue to advise users to exercise extreme caution when interacting with new or unverified widgets on the platform, as the threat of malware delivery remains a tangible concern for those who frequently utilize the service’s evolving feature set. As more information becomes available, the industry will likely look toward further updates from both the platform developers and independent security firms to confirm that the integrity of the application has been fully restored and that the risks associated with the new widget architecture have been mitigated to an acceptable standard.

Tagged: