Malicious Code Injection in purring_silverfish_requirement Package
Summary
MAL-2025-96122: Malicious code in purring_silverfish_requirement (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 purring_silverfish_requirement package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate automated publishing of derivative packages, which can inflate developer reputation scores for token rewards. Its functionality is compromised by malicious scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded within the purring_silverfish_requirement package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The intent is to continuously republish these variants, polluting the npm registry and potentially leading to security risks for developers who unknowingly use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall purring_silverfish_requirementIf 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 remove the purring_silverfish_requirement package from your project by executing: npm uninstall purring_silverfish_requirement. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The purring_silverfish_requirement package contains a significant vulnerability due to malicious code that alters package metadata and repopulates the npm registry with compromised packages. It is crucial to update or remove this package to safeguard your project.
See every vulnerability recorded for purring_silverfish_requirement →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to automate the publishing of derivative packages.
The malicious code modifies your package.json file and can lead to the publication of compromised packages, affecting your project's integrity.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.
Absolutely! You can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
If an immediate update is not possible, consider uninstalling the package as a temporary measure to mitigate risks.
