Malicious Code Injection in indove-notthedevs Package: A Threat to npm Ecosystem

indove-notthedevs Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104167: Malicious code in indove-notthedevs (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The indove-notthedevs package is part of a broader trend of malicious packages that have infiltrated the npm ecosystem, often linked to token reward schemes. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior compromises the integrity of the npm registry and poses a risk to developers who may unknowingly install these malicious packages.

Vulnerability Detail

The vulnerability originates from the indove-notthedevs package, which is associated with the tea.xyz token reward campaign. It contains scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This results in the continuous republishing of variants, polluting the npm registry and potentially leading to the installation of malicious code by unsuspecting developers. The ramifications include compromised systems, unauthorized access, and the potential for further exploitation.

How To Fix

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

npm uninstall indove-notthedevs

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 indove-notthedevs package and monitor your dependencies for any signs of malicious activity. You can also use tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time. For example, you can check your application against the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The indove-notthedevs package poses a significant threat to the npm ecosystem due to its malicious behavior. Developers are urged to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities. Staying informed and proactive is essential to maintaining the security of your applications.

See every vulnerability recorded for indove-notthedevs →

Share this vulnerability

FAQ

The indove-notthedevs package is a malicious npm package designed to inflate developer reputation scores through automated publishing of derivative packages.

If you have this package installed, it can modify your project files and lead to the installation of other malicious packages, compromising your project's security.

You should uninstall the indove-notthedevs package immediately using the command: npm uninstall indove-notthedevs.

You can use Vulert to monitor your package-lock.json for vulnerabilities in real-time. Visit Vulert Scanner to check your application.

Currently, there are no patched versions available for the indove-notthedevs package, so it is recommended to remove it entirely.

How To Fix

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

npm uninstall indove-notthedevs

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