Telegram widgets are a new execution surface with an unresolved malware warning
Telegram promoted in-message widgets on November 10, 2026 as a way for any message to become an app. Within days, researchers published demonstrations that they described as remote code execution. Kaspersky also warned that it had observed malicious activity it suspected was tied to the new feature. Telegram disputed the broader interpretation of the demonstrations while acknowledging a fix for one scenario. The result is a security story with important unresolved facts, not a settled account of a universal client vulnerability.
According to SecurityWeek, researchers at V12 posted a video described as "Any telegram message can now become RCE" and showed an interaction with a bot opening the Calculator app on an Android phone. Telegram said the Android issue had already been fixed and deployed. V12 then published a second video claiming an exploit against a Windows client. Kaspersky's November 13 warning said visiting certain Telegram channels caused a PowerShell script to run without the user's knowledge, followed by the Rust-based WebRAT malware, also called Salat Stealer.
Kaspersky did not publicly identify the exact flaw, Telegram version, or number of affected users. Telegram CEO Pavel Durov said a user first had to start a third-party service and that the relevant server-side scenario had been patched. Those statements leave a practical uncertainty: the malware warning, the proof-of-concept demonstrations, and the server-side mitigation may describe related but not identical conditions.
Why widget execution changes the trust model
Messaging clients are built to display content received from other people. A widget adds executable behavior to that content. The platform may try to sandbox the widget, restrict network access, or require a bot interaction, but the security property depends on the exact client version, the widget runtime, the operating system, and the path that launches the content. A demonstration that opens a calculator is not automatically equivalent to silent remote code execution, and a server-side block does not repair every client that already has a widget in a chat.
The malware warning is important because it moves the discussion from demonstration to delivery. A message can be the initial content that convinces a user to open a bot, while a compromised channel or a widget endpoint provides the second step. Security teams should record both the initial message and any subsequent bot or service interaction.
Near-term controls
Do not assume that widget content is harmless because it appears inside a trusted messenger. Avoid opening widgets from untrusted channels until the client and server behavior are understood. Keep Telegram clients current, but verify the version and the platform rather than relying on a single statement that a fix has shipped. If the organization permits Telegram on managed devices, apply endpoint controls that block unexpected PowerShell execution and suspicious child processes from chat applications.
Monitor for scripts that fetch a payload from an unfamiliar domain, especially when the parent process is a messaging client or browser. Review new bots, third-party service authorizations, and channels that ask users to interact with a widget before normal text is shown. Do not use one researcher's calculator demonstration as a detection signature for every attack.
What would make this clearer
A useful vendor bulletin would identify the affected client versions, the precise execution primitive, whether user interaction is required, and whether existing widgets remain active after the fix. It would also distinguish a server-side entitlement change from a client sandbox escape. Until those details are public, the responsible conclusion is narrower: there are credible demonstrations and a malware warning, but the scope and exploitability are not fully established.
This is a common pattern for a new platform feature. Functionality ships quickly, researchers test the boundaries, and defenders receive fragments from researchers, malware analysts, and the vendor. The right response is not to dismiss the warning because the vendor disputes one demonstration, nor to treat a proof of concept as proof that every user is compromised. Inventory the feature, reduce exposure to untrusted content, and preserve endpoint evidence.
Top comments (0)