Malicious Code Injection in prickly_whippet-biggestdev Package
Summary
MAL-2025-107256: Malicious code in prickly_whippet-biggestdev (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 prickly_whippet-biggestdev 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. However, it has been identified as containing malicious code that modifies package metadata and repackages itself under various names.
Vulnerability Detail
The vulnerability originates from the malicious intent behind the package, which includes scripts that alter the package.json file to remove private flags, change version numbers, and generate random package names. This behavior leads to the pollution of the npm registry and can compromise the integrity of projects that depend on this package. The malicious payload is designed to continuously republish variants, making it difficult to track and mitigate.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall prickly_whippet-biggestdevIf 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 prickly_whippet-biggestdev package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use tools like Vulert to monitor your project for vulnerabilities.
Conclusion
The prickly_whippet-biggestdev package poses a significant risk due to its malicious code that alters package metadata and repackages itself. It is crucial to remove this package from your project and monitor for vulnerabilities using tools like Vulert to ensure the security of your applications.
See every vulnerability recorded for prickly_whippet-biggestdev →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.
The malicious code modifies package metadata and can lead to the pollution of the npm registry, potentially compromising your project's integrity.
You should uninstall the package immediately using the command: npm uninstall prickly_whippet-biggestdev.
Yes, you can use Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without any signup.
