Medium 3 Hunt LeadsIOCsWebRATForkLog

Telegram’s New Widgets Are Suspected of Delivering the WebRAT Trojan

Kaspersky saw attempts on Nov. 13 to infect PCs with the WebRAT trojan from Telegram channels and suspects Telegram's new HTML widgets; Telegram has switched the feature off and denies one-message hacks.

Telegram’s brand-new interactive message widgets lasted four days before security firms started seeing them linked to malware. ForkLog reports that Kaspersky detected attempts on the night of Nov. 13 to infect computers with the WebRAT trojan, also called Salat Stealer, when people visited certain Telegram channels, and suspects a flaw in the HTML widgets Telegram added on Nov. 9. Telegram’s founder Pavel Durov says no one could be hacked just by receiving a message, and Telegram switched the feature off server-side the same day.

For defenders

What Kaspersky saw: per ForkLog, the activity silently ran a PowerShell script that downloaded and launched WebRAT, which is written in Rust: T1059.001 (Command and Scripting Interpreter: PowerShell), T1105 (Ingress Tool Transfer). Kaspersky didn’t publish how the infection started, indicators or hashes for this wave. Exploitation of the widgets is a suspicion, not confirmed: T1203 (Exploitation for Client Execution).

The widget background: Telegram’s Bot API 10.4 (Nov. 9) let bots send HTML widgets whose JavaScript runs in a sandboxed QuickJS engine. Researchers at V12 showed code execution on Android on Nov. 11 and on the then-current Telegram Desktop 7.4.3 for Windows on Nov. 13, publishing only a SHA-256 commitment of their exploit (not a malware hash; don’t hunt for it). Telegram says it fixed the Android bug on Nov. 10, and the widget sandbox’s changelog records a QuickJS fix for handling of await using. Durov says an attack needed the user to start a third-party bot first. Bots can no longer send new widgets, but ones already received still work, and how this would happen from a channel, where widgets weren’t supposed to appear, is unexplained.

WebRAT itself: a backdoor that steals crypto wallets and Telegram, Discord and Steam accounts and records the screen, keystrokes, webcam and microphone. In late 2025 Kaspersky found it posing as exploits on GitHub, where a dropper elevated itself, turned off Defender and fetched WebRAT: T1685 (Disable or Modify Tools). Those older indicators are below. No CVE has been assigned.

Network
ezc5510min[.]temp[.]swtest[.]ru, shopsleta[.]ru (WebRAT C2, 2025 GitHub campaign)

Host
rasmanesc.exe, start_exp.bat, payload.dll (2025 fake-exploit archive)
MD5 61b1fc6ab327e6d3ff5fd3e82b430315 (rasmanesc.exe dropper)

What it means for you

Update Telegram on your phone and computer now, and don’t open interactive widgets from bots or channels you don’t know until Kaspersky and Telegram say the problem is fully fixed. Even Telegram’s own account of this says you had to start a bot first, so the safest habit is simple: don’t tap “Start” on random bots. If your PC runs a surprise PowerShell window, treat it as infected.

Do this now

  1. Update Telegram on every device, and keep it on automatic updates.
  2. Don’t start unfamiliar bots or open widgets in chats from people or channels you don’t trust.
  3. Turn on Telegram’s two-step verification password so a stolen session is harder to reuse.
  4. IT teams: alert when Telegram Desktop launches PowerShell or cmd, which it should never need to do.

Source article: Kaspersky Lab Reports WebRAT Trojan Attacks via Telegram
Publisher: ForkLog
Published: Nov. 14, 2026
URL: https://forklog.com/en/kaspersky-lab-reports-webrat-trojan-attacks-via-telegram/

Executive Summary

Kaspersky reported, via its Telegram channel and as relayed by ForkLog, attempts on the night of Nov. 13, 2026 to infect computers with WebRAT, a Rust-written backdoor that Kaspersky also refers to as Salat Stealer, when users visited certain Telegram channels. The observed chain was a hidden PowerShell script that downloaded and executed the WebRAT payload; Kaspersky did not disclose how the script was triggered, and suspects abuse of the interactive HTML widgets Telegram introduced with Bot API 10.4 on Nov. 9, whose JavaScript runs in a QuickJS sandbox. Independent researchers at V12 demonstrated code execution through crafted widgets on Telegram for Android (Nov. 11) and Telegram Desktop 7.4.3 for Windows (Nov. 13) without releasing details; Telegram says it fixed the Android issue on Nov. 10, its founder says exploitation required the user to start a third-party bot, and Telegram disabled server-side widget delivery on Nov. 13 while previously received widgets keep working. No actor is named. WebRAT has been tracked since early 2025 as a lure inside game cheats and cracked software and, from September 2025, inside fake exploit repositories on GitHub aimed at students and junior security staff, where a dropper elevated itself, disabled Microsoft Defender and pulled WebRAT from its C2. Its objectives are remote control and theft of crypto wallets and Telegram, Discord and Steam accounts, plus screen, keystroke, webcam and microphone capture. Kaspersky published no indicators for the Telegram wave, so the indicators below come from its 2025 GitHub report and are marked as such; hunt leads, false positive expectations and indicators are detailed below, and no published YARA or Sigma rules exist in the sources.

ATT&CK chain: Initial Access → Execution → Privilege Escalation → Defense Evasion → Collection → Command and Control

Hunt Lead Grid

Hunt Lead Level Hunt Lead Name ATT&CK Risk of False Positives
1 (Junior) WebRAT C2 and Fake-Exploit Artifact Sweep T1105 (Ingress Tool Transfer), T1608.001 (Stage Capabilities: Upload Malware) Low. The domains, repositories and dropper hash are attacker-controlled per Kaspersky; the lead anchors on exact hosts, repository paths and file names, though the indicators date from the 2025 campaign and may not match the Telegram wave.
2 (Pro) Telegram Client Spawning PowerShell T1203 (Exploitation for Client Execution), T1059.001 (Command and Scripting Interpreter: PowerShell) Low. Telegram Desktop has no legitimate reason to launch a script interpreter; the lead anchors on Telegram.exe as the direct parent, so only users who deliberately open scripts from Telegram downloads will match.
2 (Pro) Unsigned Binary Disabling Defender After Elevation T1685 (Disable or Modify Tools), T1134.002 (Access Token Manipulation: Create Process with Token) Medium. Management agents and some admin tools change Defender settings; the lead anchors on unsigned executables from download or archive-extraction folders making the change.

WebRAT C2 and Fake-Exploit Artifact Sweep

In the campaign Kaspersky documented in late 2025, fake proof-of-concept repositories for CVE-2025-59295, CVE-2025-10294, CVE-2025-59230 and other headline CVEs hosted a password-protected ZIP whose password was hidden in the name of an empty file inside it (“pass – 8511”). The archive held a corrupted decoy payload.dll, a start_exp.bat containing only “start rasmanesc.exe”, and the dropper rasmanesc.exe (MD5 61b1fc6ab327e6d3ff5fd3e82b430315; other names are possible), which downloaded WebRAT from ezc5510min[.]temp[.]swtest[.]ru; Kaspersky also lists shopsleta[.]ru as WebRAT C2. The listed repositories include github[.]com/RedFoxNxploits/CVE-2025-10294-Poc, github[.]com/FixingPhantom/CVE-2025-10294, github[.]com/h4xnz/CVE-2025-10294-POC, github[.]com/usjnx72726w/CVE-2025-59295, github[.]com/stalker110119/CVE-2025-59230, github[.]com/moegameka/CVE-2025-59230, github[.]com/DebugFrag/CVE-2025-12596-Exploit and github[.]com/lagerhaker539/CVE-2025-12595-POC, among 15. The detection logic is a retrospective search of DNS, proxy and EDR network logs for the two C2 domains, proxy logs for clones or downloads from those repository paths, and file telemetry for rasmanesc.exe, start_exp.bat beside payload.dll, and the three MD5 values in the appendix.

Use DNS resolver logs, proxy logs with full URLs, EDR file-creation and hash telemetry, and git or download logs on analyst and student machines. Sweep back to September 2025, when the GitHub campaign began, and pay most attention to security team, student lab and developer endpoints, which were the intended targets. Match the repositories only as exact owner/repository paths; blocking github.com itself would be the wrong control. Kaspersky published no indicators for the Nov. 13 Telegram activity, so a clean result here does not clear a host of that wave; pair it with the Telegram process lead. Any hit on the C2 domains or dropper hash should be treated as a confirmed infection, with credential and wallet resets from a clean device.

Hunt Lead Level: 1 (Junior Analyst)

ATT&CK: Resource Development → T1608.001 (Stage Capabilities: Upload Malware) (mapping per Kaspersky’s report); Execution → T1204.002 (User Execution: Malicious File); Command and Control → T1105 (Ingress Tool Transfer)

Sources: “Webrat распространяется через GitHub под видом эксплойтов” (Webrat distributed via GitHub disguised as exploits), Securelist (Kaspersky, Maxim Starodubov), Dec. 23, 2025, https://securelist.ru/webrat-distributed-via-github/114486/ (additional source, same malware family)

Telegram Client Spawning PowerShell

On the night of Nov. 13, 2026, Kaspersky recorded infection attempts in which visiting certain Telegram channels led to the hidden execution of a PowerShell script that downloaded and ran the Rust-written WebRAT payload. Kaspersky suspects the HTML widgets introduced on Nov. 9, whose JavaScript is executed by an embedded QuickJS engine in the Telegram client; V12 separately demonstrated code execution through a crafted widget on Telegram Desktop 7.4.3 for Windows the same night, and Telegram disabled delivery of new widgets on Nov. 13, though widgets already in chats remain active. The detection logic is to alert on any process-creation event where Telegram.exe (or the Telegram Desktop updater) is the parent, or grandparent through cmd.exe, of powershell.exe, pwsh.exe, cmd.exe, mshta.exe, wscript.exe or curl.exe, with highest priority for hidden windows, encoded commands, web download cmdlets, or a new executable written and launched within the following minute.

Use EDR or Sysmon process-creation telemetry with parent and command line (Sysmon event 1 or Security 4688), PowerShell script block logging (event 4104), and file-creation events in %TEMP% and %APPDATA%. Sweep from Nov. 9, 2026, when widgets went live, and keep the rule permanently, since previously received widgets still execute. Telegram Desktop is often installed per user under %APPDATA%\Telegram Desktop, so match on the signed Telegram image rather than a fixed path. Blocking Telegram entirely is a heavy-handed response that breaks legitimate use; the anchor is the child process. Any hit should be escalated as a likely client-side compromise, with the user’s Telegram sessions terminated from Settings and other active sessions reviewed, and the pattern generalizes to future exploits against any messaging client.

Hunt Lead Level: 2 (Pro)

ATT&CK: Execution → T1203 (Exploitation for Client Execution) (suspected, not confirmed), T1059.001 (Command and Scripting Interpreter: PowerShell); Command and Control → T1105 (Ingress Tool Transfer)

Sources: “Kaspersky Lab Reports WebRAT Trojan Attacks via Telegram”, ForkLog, Nov. 14, 2026, https://forklog.com/en/kaspersky-lab-reports-webrat-trojan-attacks-via-telegram/ (source article)

Unsigned Binary Disabling Defender After Elevation

Kaspersky’s analysis of the 2025 WebRAT dropper describes a fixed sequence: rasmanesc.exe elevates itself to administrator, disables Microsoft Defender to avoid detection, then downloads and runs WebRAT from a hard-coded URL. The sources do not say whether the Telegram-delivered PowerShell stage does the same, but the payload family is unchanged per Kaspersky. The detection logic is to alert when an unsigned executable launched from a user download folder, an archive-extraction folder or %TEMP% obtains an elevated token and, within minutes, changes Defender configuration (real-time protection off, tamper attempts, exclusions added) and then makes an outbound connection to a domain not seen before in the environment.

Use Defender operational events (5001 real-time protection disabled, 5007 configuration change), EDR process, token and network telemetry, and UAC consent logs where available. Sweep 90 days on workstations and analyst machines. Intune, Group Policy and EDR consoles change Defender legitimately, so allowlist by the writing process and its signer rather than by user. Hash-blocking the dropper alone is the wrong control, because Kaspersky notes the file name varies and the family is repackaged per campaign. A match is a confirmed infection: isolate, restore Defender, and treat all browser, Telegram, Discord, Steam and wallet credentials on the host as stolen.

Hunt Lead Level: 2 (Pro)

ATT&CK: Privilege Escalation → T1134.002 (Access Token Manipulation: Create Process with Token) (mapping per Kaspersky’s report); Defense Evasion → T1685 (Disable or Modify Tools) (Kaspersky’s report cites the retired T1562.001; T1685 is its current ATT&CK equivalent)

Sources: Securelist (above), additional source, same malware family

Hash Appendix

WebRAT fake-exploit campaign (2025)

MD5 values come from Kaspersky’s 2025 Securelist report on the same malware family, not from the source article, which published no hashes. Kaspersky labels only 61b1fc6ab327e6d3ff5fd3e82b430315 by file name; the other two are listed without names. SHA1 and SHA256 were not published, and OTX AlienVault and VirusTotal were not queried for this report. The SHA-256 posted by V12 on Nov. 11 is a commitment hash for an undisclosed exploit demonstration, not a malware sample, and is deliberately excluded.

MD5s

61b1fc6ab327e6d3ff5fd3e82b430315  # rasmanesc.exe -> WebRAT dropper from fake-exploit ZIP (elevates, disables Defender, downloads WebRAT)
28a741e9fcd57bd607255d3a4690c82f  # unnamed sample -> listed in Kaspersky's WebRAT campaign IOCs
a13c3d863e8e2bd7596bac5d41581f6a  # unnamed sample -> listed in Kaspersky's WebRAT campaign IOCs

SHA1s

(not available)  # rasmanesc.exe -> WebRAT dropper from fake-exploit ZIP (elevates, disables Defender, downloads WebRAT)
(not available)  # unnamed sample -> listed in Kaspersky's WebRAT campaign IOCs
(not available)  # unnamed sample -> listed in Kaspersky's WebRAT campaign IOCs

SHA256s

(not available)  # rasmanesc.exe -> WebRAT dropper from fake-exploit ZIP (elevates, disables Defender, downloads WebRAT)
(not available)  # unnamed sample -> listed in Kaspersky's WebRAT campaign IOCs
(not available)  # unnamed sample -> listed in Kaspersky's WebRAT campaign IOCs

References Appendix

  • “Kaspersky Lab Reports WebRAT Trojan Attacks via Telegram”, ForkLog, Nov. 14, 2026, https://forklog.com/en/kaspersky-lab-reports-webrat-trojan-attacks-via-telegram/ (source article)
  • “Webrat распространяется через GitHub под видом эксплойтов”, Securelist (Kaspersky, Maxim Starodubov), Dec. 23, 2025, https://securelist.ru/webrat-distributed-via-github/114486/ (additional source; distribution chain, ATT&CK mapping, C2, repositories and MD5s)
  • “Bot API changelog”, Telegram, https://core.telegram.org/bots/api-changelog
  • “Widgets”, Telegram Bot documentation, https://core.telegram.org/bots/widgets
  • MITRE ATT&CK Enterprise technique pages linked above, MITRE, https://attack.mitre.org/

More from the Roundup