Malicious Code Injection in quiet_shrimp_z3n: A Threat to npm Packages
Summary
MAL-2025-107665: Malicious code in quiet_shrimp_z3n (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 'quiet_shrimp_z3n' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. This behavior is primarily aimed at inflating developer reputation scores for token rewards, making it a significant concern for developers relying on npm for package management.
Vulnerability Detail
The vulnerability in 'quiet_shrimp_z3n' stems from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, which leads to the continuous republishing of these variants. This not only pollutes the npm registry but also poses a risk of unintentional dependency on these malicious packages, potentially compromising the security of applications that use them.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall quiet_shrimp_z3nIf 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 'quiet_shrimp_z3n' package and replace it with a trusted alternative. Always verify the integrity and reputation of packages before including them in your project.
Conclusion
The 'quiet_shrimp_z3n' package poses a significant threat due to its malicious code that alters package configurations and floods the npm registry. Developers are advised to remove this package and monitor their dependencies closely to maintain the security of their applications.
See every vulnerability recorded for quiet_shrimp_z3n →
FAQ
The main issue is that it contains malicious code that modifies package.json files and republish variants to pollute the npm registry.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.
You should uninstall the package immediately using 'npm uninstall quiet_shrimp_z3n' and review your dependencies for any other potentially malicious packages.
Yes, using this package can lead to security vulnerabilities in your application, including unauthorized access and data breaches due to the malicious modifications it performs.
Regularly audit your dependencies, use trusted sources for packages, and consider using tools like Vulert to monitor for vulnerabilities in real-time.
