Malicious Code Injection in joint_alpaca_z3n Package - npm Vulnerability

joint_alpaca_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104563: Malicious code in joint_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 joint_alpaca_z3n package is part of the npm ecosystem, often used for various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has led to the proliferation of malicious packages designed to inflate developer reputation scores. This package, like others in the campaign, is susceptible to exploitation due to its design, which allows for the automatic generation and publishing of derivative packages.

Vulnerability Detail

The vulnerability in the joint_alpaca_z3n package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which aims to manipulate npm's registry by flooding it with these malicious packages. The ramifications include potential security risks for users who unknowingly install these packages, as they can lead to further exploitation or pollution of the npm registry.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall joint_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 workaround, you can remove the joint_alpaca_z3n package from your project by executing: npm uninstall joint_alpaca_z3n. This will prevent any malicious code from executing until a secure version is available.

Conclusion

The joint_alpaca_z3n package has been identified as containing malicious code that poses a significant risk to users. It is crucial to take immediate action by updating or removing the package to safeguard your application. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for joint_alpaca_z3n →

Share this vulnerability

FAQ

The joint_alpaca_z3n package is an npm package associated with the tea.xyz token reward campaign, often used in JavaScript applications.

The vulnerability can lead to unauthorized modifications in your package.json file, potentially compromising your application's integrity and security.

If you have installed the joint_alpaca_z3n package, it is recommended to uninstall it immediately and check for any updates or patches.

You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software by analyzing your package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall joint_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