Malicious Code Injection in gothic_alpaca_z3n: A Threat to npm Packages
Summary
MAL-2025-94722: Malicious code in gothic_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 package gothic_alpaca_z3n is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing significant risks to users and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in gothic_alpaca_z3n stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to create numerous derivative packages that pollute the npm registry, making it difficult for developers to find legitimate packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which incentivizes the creation of such malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall gothic_alpaca_z3n
If 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 measure, you can avoid using the gothic_alpaca_z3n package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your npm packages using tools like npm audit to identify and address vulnerabilities.
Conclusion
The gothic_alpaca_z3n package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. It is essential to remove this package from your projects and regularly audit your dependencies to maintain security. Utilizing tools like Vulert can aid in monitoring vulnerabilities in real-time.
See every vulnerability recorded for gothic_alpaca_z3n →
FAQ
gothic_alpaca_z3n is an npm package that has been identified as malicious due to its involvement in the tea.xyz token reward campaign, which aims to inflate developer reputation scores.
This vulnerability can compromise the integrity of your project by introducing malicious code that modifies package metadata and floods the npm registry with unwanted packages.
You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
If you have installed gothic_alpaca_z3n, you should uninstall it immediately using the command npm uninstall gothic_alpaca_z3n and audit your other dependencies for vulnerabilities.
Yes, tools like npm audit and Vulert can help you identify and manage vulnerabilities in your npm packages effectively.