Malicious Code Injection in shocked_manatee_z3n Package
Summary
MAL-2025-90484: Malicious code in shocked_manatee_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 shocked_manatee_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to potential security risks for developers and users alike.
Vulnerability Detail
The vulnerability in the shocked_manatee_z3n package originates from its association with the tea.xyz token reward campaign. This campaign has led to the creation of numerous malicious packages that contain scripts designed to automatically publish derivative packages with altered metadata. The malicious payload modifies the package.json file to remove private flags, changes version numbers, and generates random package names, which can lead to reputation inflation and pollution of the npm registry. The ramifications include compromised developer accounts, potential data breaches, and a degraded trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall shocked_manatee_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 workaround, you can temporarily avoid using the shocked_manatee_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The shocked_manatee_z3n package poses a significant security risk due to its malicious code injection. It is crucial for developers to be aware of this vulnerability and take immediate action to remove the package and monitor their projects for any further risks. Utilizing tools like Vulert can aid in maintaining the security of your applications.
See every vulnerability recorded for shocked_manatee_z3n →
FAQ
The shocked_manatee_z3n package is an npm package that has been identified as part of a malicious campaign aimed at exploiting the npm registry.
This vulnerability can lead to the pollution of the npm registry, compromise developer accounts, and potentially expose sensitive data.
You should uninstall the shocked_manatee_z3n package immediately and check for any other affected packages in your project.
Yes, you can use Vulert, which monitors and alerts you in real-time for open-source vulnerabilities using just your package-lock.json.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
