Malicious Code Injection in broken_otter_z3n Package
Summary
MAL-2025-100132: Malicious code in broken_otter_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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The broken_otter_z3n package is part of the npm ecosystem, which is widely used for JavaScript development. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary functionality of this package is to serve as a token reward mechanism, but it has been compromised to include malicious code that affects its integrity and security.
Vulnerability Detail
The vulnerability originates from the broken_otter_z3n package being part of a malicious campaign that employs scripts to automatically generate and publish derivative packages with randomized names. This malicious payload modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, leading to pollution of the npm registry. The ramifications include potential security risks for developers using this package, as it can lead to unauthorized access and manipulation of their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall broken_otter_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 broken_otter_z3n package and look for alternative packages that provide similar functionality without the associated risks. Always validate the integrity of packages before installation.
Conclusion
The broken_otter_z3n package has been identified as containing malicious code that poses significant risks to developers. It is crucial to remove this package from your projects and ensure that you are using secure alternatives. Regularly monitoring your dependencies with tools like Vulert can help maintain the integrity of your applications.
See every vulnerability recorded for broken_otter_z3n →
FAQ
The broken_otter_z3n package is an npm package associated with the tea.xyz token reward campaign, which has been compromised to include malicious code.
The malicious code modifies your package.json file, removes private flags, and can lead to unauthorized republishing of your packages, posing security risks.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without requiring any signup.
If you have installed the broken_otter_z3n package, you should uninstall it immediately using 'npm uninstall broken_otter_z3n' and look for secure alternatives.
Yes, you should look for other npm packages that provide similar functionality but have a verified reputation and do not contain malicious code.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
