Malicious Code Vulnerability in telegram-api-test Package

telegram-api-test Updated 02 Dec 2025

Summary

01/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191596: Malicious code in telegram-api-test (npm). Affects telegram-api-test versions 1.0.1. 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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The telegram-api-test package is a Node.js library designed for testing Telegram API functionalities. It allows developers to simulate interactions with the Telegram platform, making it easier to develop and test applications that integrate with Telegram. However, this package has been identified as containing malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the telegram-api-test package, specifically in version 1.0.1. This code can potentially compromise the security of applications that depend on this package, leading to unauthorized access, data breaches, or other malicious activities. The origin of this vulnerability is linked to the package being flagged by security researchers from ReversingLabs, highlighting the importance of scrutinizing third-party packages for security threats.

How To Fix

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

npm uninstall telegram-api-test

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 temporary workaround, you can avoid using the telegram-api-test package altogether and implement your own testing methods for the Telegram API. This may involve using direct API calls or other libraries that are known to be secure.

Conclusion

The telegram-api-test package has been flagged for containing malicious code, which poses significant security risks to applications that utilize it. It is crucial for developers to remove this package and consider alternatives to safeguard their applications.

See every vulnerability recorded for telegram-api-test →

Share this vulnerability

FAQ

The telegram-api-test package is a Node.js library used for testing Telegram API functionalities.

The specific nature of the malicious code has not been disclosed, but it poses risks such as unauthorized access and data breaches.

You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities, to check if your application is affected. Visit Vulert Scanner to use the Vulert playground without signup.

It is advised to remove the telegram-api-test package from your project and consider using a secure alternative.

The vulnerability was identified by security researchers from ReversingLabs.

How To Fix

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

npm uninstall telegram-api-test

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