Malicious Code Injection in bottom_opossum_z3n: A Threat to npm Users
Summary
MAL-2025-100064: Malicious code in bottom_opossum_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 bottom_opossum_z3n is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant pollution of the npm registry and potential security risks for users.
Vulnerability Detail
The vulnerability in bottom_opossum_z3n originates from its involvement in the tea.xyz token reward campaign. It contains malicious scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly install these malicious packages, leading to potential data breaches or system compromises.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall bottom_opossum_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 bottom_opossum_z3n package and monitor your project for any dependencies that may inadvertently include it. You can also use tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.
Conclusion
The bottom_opossum_z3n package poses a significant threat due to its malicious code designed to exploit the npm registry. It is crucial for developers to be aware of such vulnerabilities and take proactive measures to secure their projects. By uninstalling affected packages and using monitoring tools like Vulert, developers can protect their applications from potential risks.
See every vulnerability recorded for bottom_opossum_z3n →
FAQ
bottom_opossum_z3n is an npm package that has been identified as part of a malicious campaign to flood the npm registry with derivative packages.
The vulnerability can lead to the installation of malicious packages that may compromise your project's security and integrity.
You should uninstall the package immediately using the command 'npm uninstall bottom_opossum_z3n' and check your project for any other affected dependencies.
Regularly update your dependencies, monitor your package-lock.json with tools like Vulert, and be cautious of packages that are newly published or have low download counts.
Vulert is a tool that monitors your package-lock.json for open-source vulnerabilities in real-time. You can use the Vulert playground to check if your application is affected by this vulnerability without any signup.
