Malicious Code Injection in paella-notthedevs Package: A Threat to npm Users

paella-notthedevs Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106878: Malicious code in paella-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 paella-notthedevs package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been linked to the proliferation of malicious packages on npm. Its functionality is compromised due to the presence of malicious scripts that manipulate package metadata and publish unauthorized derivatives, posing a significant risk to developers and users alike.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the paella-notthedevs package. This payload is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. It continuously republishes these variants to the npm registry, which can lead to pollution of the registry and potential exploitation of developers who unknowingly use these compromised packages. The ramifications include loss of reputation for developers, potential data breaches, and the introduction of further vulnerabilities into dependent projects.

How To Fix

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

npm uninstall paella-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, you can avoid using the paella-notthedevs package altogether. If it is already in use, consider removing it from your project and replacing it with a trusted alternative. Additionally, you can use the following command to uninstall the package: npm uninstall paella-notthedevs.

Conclusion

The paella-notthedevs package has been identified as a malicious entity within the npm ecosystem, capable of compromising projects and polluting the npm registry. It is crucial for developers to take immediate action by removing this package and utilizing tools like Vulert to monitor for vulnerabilities in their projects. Staying informed and vigilant is key to maintaining secure software development practices.

See every vulnerability recorded for paella-notthedevs →

Share this vulnerability

FAQ

The paella-notthedevs package is a JavaScript package available on npm, which has been identified as containing malicious code that can compromise projects.

You can use Vulert, a tool that monitors open-source vulnerabilities in your software by analyzing your package-lock.json file. Visit Vulert Scanner to check for vulnerabilities without needing to sign up.

If you have installed the paella-notthedevs package, it is recommended to uninstall it immediately and check for any alternative packages that are safe to use.

Yes, using npm packages can pose risks, especially if they contain malicious code. It is crucial to monitor and audit your dependencies regularly.

To prevent similar vulnerabilities, regularly update your dependencies, use tools like Vulert for monitoring, and review package sources before installation.

How To Fix

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

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