Critical Malicious Code Vulnerability in @jayeshsadhwani/telemetry-sdk

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191238: Malicious code in @jayeshsadhwani/telemetry-sdk (npm). Affects @jayeshsadhwani/telemetry-sdk versions 1.0.14. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The @jayeshsadhwani/telemetry-sdk is an npm package designed for telemetry data collection and analysis. It provides developers with tools to monitor application performance and user interactions. However, this package has been compromised, leading to severe security risks for users who have it installed.

Vulnerability Detail

The vulnerability stems from a malicious code injection attributed to the Sha1-Hulud: The Second Coming NPM worm. This worm is capable of stealing tokens and credentials, publishing them to GitHub, and propagating itself to other npm packages owned by the user. Additionally, it can establish persistence through GitHub actions and may even destroy the user's home directory. Any system with this package installed is considered fully compromised, necessitating immediate action to secure sensitive information.

How To Fix

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

npm uninstall @jayeshsadhwani/telemetry-sdk

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 measure, you can isolate the affected environment and prevent it from accessing the internet to limit the spread of the malicious code. Additionally, consider using the following command to uninstall the package: npm uninstall @jayeshsadhwani/telemetry-sdk.

Conclusion

The @jayeshsadhwani/telemetry-sdk package has been compromised, posing serious security risks to users. Immediate action is required to remove the package and secure any sensitive information. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for @jayeshsadhwani/telemetry-sdk →

Share this vulnerability

FAQ

Immediately uninstall the package and rotate any sensitive credentials stored on the affected system.

The malicious code can steal sensitive tokens and credentials, potentially leading to unauthorized access to your accounts and data.

Yes, you can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.

While the npm ecosystem is generally secure, incidents like this highlight the importance of vigilance and using tools like Vulert to monitor for vulnerabilities.

If not addressed, the vulnerability could lead to significant data breaches, loss of sensitive information, and potential damage to your reputation.

How To Fix

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

npm uninstall @jayeshsadhwani/telemetry-sdk

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