Malicious Code Injection in gothic_alpaca_z3n: A Threat to npm Packages

gothic_alpaca_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-94722: Malicious code in gothic_alpaca_z3n (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

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 →

Share this vulnerability

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.

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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback