Critical Malicious Code Vulnerability in node-telegram-sockets Package

node-telegram-sockets Updated 12 Oct 2026

Summary

12/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17845: Malicious code in node-telegram-sockets (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The node-telegram-sockets package is an npm library designed for building Telegram bots using WebSocket connections. It provides developers with a straightforward way to interact with the Telegram Bot API. However, this package has been identified as containing malicious code, which poses significant security risks to any system utilizing it.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the node-telegram-sockets package. This code can compromise any computer that has the package installed or running, potentially allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of this code means that simply removing the package may not eliminate all traces of the compromise, as full control of the affected system may have been handed over to an external entity.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall node-telegram-sockets

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a workaround, if you are currently using node-telegram-sockets, consider switching to an alternative library for Telegram bot development until the issue is resolved. Ensure that you thoroughly review the security of any new packages before installation.

Conclusion

The node-telegram-sockets package has been identified as containing malicious code that poses a severe security risk. Immediate action is required to remove the package and secure any affected systems. Regular monitoring for vulnerabilities is essential to maintain the security of your applications.

See every vulnerability recorded for node-telegram-sockets →

Share this vulnerability

FAQ

Immediately remove the package and rotate any sensitive information stored on the affected system.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

Currently, there is no patch available. The best course of action is to remove the package and monitor for updates.

Failing to address this vulnerability can lead to unauthorized access to sensitive data and complete compromise of your system.

While many npm packages are safe, it's essential to conduct thorough security reviews and use tools like Vulert to monitor for vulnerabilities.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall node-telegram-sockets

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback