0x417265d44172…417265d7

ConfirmedSecurity578 vB116 sat/vB3 min decode

Telegram Restricts New In-Chat Widgets After No-Tap Hack Reports

Telegram restricted new in-chat widgets after researchers showed code can run without a tap on older builds; Durov says the issue is patched server-side with no theft demonstrated.

Telegram curbs new in-chat apps amid a no-tap hacking scare
WitnessTelegram curbs new in-chat apps amid a no-tap hacking scaregeralt / pixabay

Outputs

  1. Telegram restricted new in-chat widgets after researchers reported no-tap code execution on older clients.

  2. Research archive dated November 14 lists affected builds including Telegram for iOS 13.2, Desktop 7.4.0 and macOS 13.1.

  3. Widget design includes documented TON wallet card queries, wallet-signed data and transaction notifications.

  4. Pavel Durov said the issue was fully patched server-side and required users to first start a third-party service.

  5. No restoration timetable or policy for previously delivered widgets has been published.

Telegram has curbed new in-chat widget apps after researchers published findings showing widget code can execute during chat layout without a user tap. The restrictions affect widgets, which — unlike Mini Apps that open a web page on demand — run inside the message itself on the user's device.

Telegram's own widget documentation describes an isolated environment: widget code runs locally without direct internet access, and requests to the bot pass through Telegram's infrastructure rather than the device. The design carries a direct wallet connection. Telegram's changelog documents widget queries involving a user's TON wallet card, wallet-signed data, or notification of a wallet transaction.

Those documented wallet capabilities explain why crypto users watched the security reports closely, but they do not by themselves demonstrate unauthorized signing or stolen assets.

Which clients were affected?

The research archive, published under the name tg-widget-rce, states as of November 14 that its published vulnerabilities affected older clients and are fixed in current Telegram builds. The archive lists:

  • specific Android builds
  • Telegram for iOS 13.2
  • Telegram Desktop 7.4.0
  • Telegram for macOS 13.1

Findings differ across versions, and the archive does not establish a definitive minimum safe version for every client.

The researchers say widget code can execute during chat layout without a tap. Delivery, however, requires a bot already permitted to send widgets, and the severity of any result depends on the client build.

Their technical index separates two classes of outcome. On selected older Android builds, they report app-level code execution. On other builds, results stay contained within an isolated widget process — a containment that does not amount to control of the whole device. The distinction matters: a widget-process result is a far narrower failure than full app compromise, roughly the difference between a sandbox escape and a sandbox warning.

What did Pavel Durov say?

Telegram founder Pavel Durov denied that merely receiving a message could compromise users. He said users first had to start a third-party service, and asserted the issue was fully patched server-side.

Durov's account and the researchers' findings describe separate steps. Starting a third-party service and tapping a delivered widget are distinct actions, and the researchers' demonstrations — which cover execution without a tap — do not establish stolen crypto assets or widespread malicious exploitation in the wild.

Durov's assurance remains Telegram's stated position. No on-chain evidence of theft tied to the widget vulnerabilities has surfaced in the published material.

What happens to widgets now?

Levlam, the Telegram-linked developer account that confirmed the change, gave no restoration timetable. The confirmation also lacks three specifics:

  • an explanation for why access was narrowed
  • a policy for how previously delivered widgets render going forward
  • any statement tying the change to the security reports

The reply, in other words, does not establish that the vulnerability disclosures caused the restriction.

For bot developers and crypto teams building on Telegram's widget stack, the operational consequence is immediate: new widget submissions face a closed or narrowed gate with no published timeline for reopening. Teams shipping wallet-card queries or transaction notifications through widgets now face an indefinite freeze on new deployments.

The open questions are concrete. Whether Telegram publishes a minimum safe version per client, whether previously delivered widgets keep rendering, and when new widget approvals resume will determine how quickly the in-chat app ecosystem — and its TON wallet integrations — returns to normal function.

via cryptonews.net (Source)

More from Tom Whitfield

Tom Whitfield

Show full bio

News editor covering technology and product news in crypto and web3 industry at Mempool Brief.

1,084 articles