Malicious Code Injection in deepeshkhanna Package: npm Vulnerability Overview

deepeshkhanna Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-171099: Malicious code in deepeshkhanna (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 deepeshkhanna package is part of the npm ecosystem, which is widely used for managing JavaScript packages. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores for token rewards, making them a significant threat to developers and users alike.

Vulnerability Detail

The vulnerability in the deepeshkhanna package originates from its association with malicious scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants that pollute the npm registry. This not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly install these malicious packages, potentially leading to further exploitation.

How To Fix

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

npm uninstall deepeshkhanna

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, avoid using the deepeshkhanna package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, regularly monitor your project's dependencies for vulnerabilities using tools like Vulert, which can alert you to any open-source vulnerabilities in real-time.

Conclusion

The deepeshkhanna package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package from their projects and utilize tools like Vulert for ongoing monitoring of vulnerabilities in their dependencies.

See every vulnerability recorded for deepeshkhanna →

Share this vulnerability

FAQ

The deepeshkhanna package is an npm package that has been identified as part of a malicious campaign to manipulate package metadata and inflate developer reputation scores.

If you have the deepeshkhanna package installed, it can compromise your project's integrity by introducing malicious code that modifies your package.json and republishing variants to the npm registry.

You should uninstall the deepeshkhanna package immediately using the command 'npm uninstall deepeshkhanna' and monitor your project for any further vulnerabilities.

Yes, tools like Vulert can help monitor your project for open-source vulnerabilities in real-time. You can check your application against known vulnerabilities without needing to install any software.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup required.

How To Fix

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

npm uninstall deepeshkhanna

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