Malicious Code Injection in pepper-notthedevs Package

pepper-notthedevs Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107022: Malicious code in pepper-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 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 pepper-notthedevs package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been compromised to include malicious scripts that modify package metadata and republish variants, leading to potential security risks.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the pepper-notthedevs package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The continuous republishing of these variants can pollute the npm registry, making it difficult for developers to trust the integrity of packages. The ramifications include potential exposure to further attacks, as well as the degradation of the npm ecosystem's reliability.

How To Fix

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

npm uninstall pepper-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 pepper-notthedevs package altogether and look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The pepper-notthedevs package has been identified as containing malicious code that poses significant risks to developers and the npm ecosystem. It is crucial to remove this package from your projects and monitor for any updates or alternatives. Utilizing tools like Vulert can enhance your ability to detect and respond to such vulnerabilities effectively.

See every vulnerability recorded for pepper-notthedevs →

Share this vulnerability

FAQ

The package contains malicious code that alters package metadata and floods the npm registry with derivative packages.

You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.

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

Yes, consider looking for other npm packages that offer similar functionality but do not have known vulnerabilities.

Vulert uses your package-lock.json file to monitor and alert you in real-time for open-source vulnerabilities without requiring access to your code or installation.

How To Fix

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

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