Malicious Code Injection in shared_amphibian_z3n Package
Summary
MAL-2025-96552: Malicious code in shared_amphibian_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 shared_amphibian_z3n package is part of the npm ecosystem, which is widely used for JavaScript development. This package has been identified as part of a malicious campaign associated with the tea.xyz token reward system. It is designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names, which can lead to pollution of the npm registry and potential security risks for developers using these packages.
Vulnerability Detail
The vulnerability originates from the malicious code embedded within the shared_amphibian_z3n package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, primarily themed around Indonesian culture. The continuous republishing of these variants can lead to a cluttered npm registry, making it difficult for developers to find legitimate packages and increasing the risk of inadvertently using compromised software.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall shared_amphibian_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 workaround, you can avoid using the shared_amphibian_z3n package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.
Conclusion
The shared_amphibian_z3n package poses significant security risks due to its malicious code designed to manipulate package metadata and inflate developer reputation scores. It is crucial to remove this package from your projects and monitor for similar vulnerabilities using tools like Vulert.
See every vulnerability recorded for shared_amphibian_z3n →
FAQ
It is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.
Using the shared_amphibian_z3n package can lead to security risks, including the potential for your project to be associated with malicious activities and the pollution of the npm registry.
You should uninstall the shared_amphibian_z3n package immediately and check your project for any other potentially compromised packages.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can also check your application using the Vulert playground at Vulert Scanner without any signup.
Yes, you should look for well-reviewed and actively maintained packages that offer similar functionality without the associated risks of malicious code.
