Malicious Code Injection in klred-notthedevs Package - npm Vulnerability

klred-notthedevs Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104835: Malicious code in klred-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 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 klred-notthedevs package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores for token rewards.

Vulnerability Detail

The klred-notthedevs package contains malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to pollute the npm registry by continuously republishing variants, which can lead to security risks for developers who unknowingly use these compromised packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has been associated with various malicious npm packages.

How To Fix

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

npm uninstall klred-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 measure, you can avoid using the klred-notthedevs package and any other packages associated with the tea.xyz campaign. Additionally, consider using a package-lock.json file to lock your dependencies to specific versions, minimizing the risk of inadvertently installing malicious packages.

Conclusion

The klred-notthedevs package poses a significant security risk due to its malicious code designed to manipulate npm registry data. It is essential for developers to be vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities in their projects.

See every vulnerability recorded for klred-notthedevs →

Share this vulnerability

FAQ

klred-notthedevs is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

The malicious code modifies your package.json file, potentially leading to security vulnerabilities and pollution of the npm registry.

You can use Vulert to monitor your project for vulnerabilities. Visit Vulert Scanner to check if your application is affected without needing to sign up.

If you have installed klred-notthedevs, you should uninstall it immediately using the command npm uninstall klred-notthedevs.

Regularly update your dependencies, use tools like Vulert for monitoring, and review your package-lock.json file to ensure no malicious packages are included.

How To Fix

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

npm uninstall klred-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