Malicious Code Injection in pear-notthedevs: A Threat to npm Users
Summary
MAL-2025-107015: Malicious code in pear-notthedevs (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The package 'pear-notthedevs' 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 are designed to inflate developer reputation scores through automated publishing scripts. The vulnerability stems from the package's ability to modify critical files, such as package.json, which can lead to severe security risks for developers and their applications.
Vulnerability Detail
The vulnerability in 'pear-notthedevs' originates from its association with the tea.xyz token reward campaign. It contains scripts that automatically generate and publish derivative packages with randomized names, effectively polluting the npm registry. The malicious payload alters the package.json file by removing private flags and changing version numbers, which can lead to unintentional exposure of sensitive information and the proliferation of potentially harmful packages. This poses a significant risk to developers who may unknowingly incorporate these malicious packages into their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall pear-notthedevsIf 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 'pear-notthedevs' and any packages that depend on it. Regularly audit your package-lock.json file for any dependencies that may introduce vulnerabilities. You can also use tools like Vulert to monitor your project for vulnerabilities in real-time without needing to access the code directly.
Conclusion
The pear-notthedevs package poses a significant security risk due to its malicious code designed to manipulate package files and flood the npm registry. Developers should take immediate action to remove this package and monitor their projects for vulnerabilities using tools like Vulert. Staying informed and proactive is essential to maintaining the security of your applications.
See every vulnerability recorded for pear-notthedevs →
FAQ
The main issue is that it contains malicious code designed to modify package.json files and flood the npm registry with harmful derivative packages.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
If you have installed pear-notthedevs, you should uninstall it immediately using 'npm uninstall pear-notthedevs' and audit your project for any other affected packages.
Currently, there is no patched version of pear-notthedevs available. It is recommended to remove the package entirely.
Vulert uses your package-lock.json file to monitor and alert you in real-time for open-source vulnerabilities in your software, ensuring you stay informed about potential risks.
