Malicious Code Injection in managerial_alpaca_z3n Package
Summary
MAL-2025-105584: Malicious code in managerial_alpaca_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 managerial_alpaca_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate token rewards by generating and publishing derivative packages. However, it has been identified as containing malicious code that modifies its own package.json file, leading to potential security risks and reputation inflation for developers.
Vulnerability Detail
The vulnerability in the managerial_alpaca_z3n package stems from its malicious code, which is designed to remove private flags from package.json, alter version numbers, and generate random package names. This behavior is part of a broader scheme to flood the npm registry with derivative packages, potentially compromising the integrity of the registry and affecting developers' reputations. The malicious payload can lead to unauthorized access and manipulation of package data, posing significant risks to users and developers alike.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall managerial_alpaca_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 managerial_alpaca_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes.
Conclusion
The managerial_alpaca_z3n package contains malicious code that poses significant risks to developers and users by altering package data and flooding the npm registry. It is crucial to remove this package and monitor your projects for vulnerabilities to maintain security and integrity.
See every vulnerability recorded for managerial_alpaca_z3n →
FAQ
The managerial_alpaca_z3n package is part of the npm ecosystem and is involved in the tea.xyz token reward campaign, which aims to inflate developer reputation scores.
The malicious code modifies your package.json file, potentially removing important flags and altering version numbers, which can lead to security vulnerabilities and reputation issues.
If you have installed the managerial_alpaca_z3n package, it is advised to remove it immediately and monitor your project for any unauthorized changes.
Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time. Vulert analyzes your package-lock.json file to alert you of any issues.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
