Malicious Code Injection in joint_centipede_z3n Package

joint_centipede_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104566: Malicious code in joint_centipede_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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The joint_centipede_z3n package is part of the npm ecosystem, which is widely used for JavaScript development. This package has been identified as part of a malicious campaign that aims to exploit npm's publishing system. It is designed to generate and publish derivative packages with randomized names, thereby inflating developer reputation scores for token rewards in the tea.xyz protocol. The package's functionality is compromised due to its malicious intent, making it a significant threat to developers and users relying on npm packages.

Vulnerability Detail

The vulnerability in the joint_centipede_z3n package originates from its association with the tea.xyz token reward campaign. The package contains scripts that automatically modify the package.json file to remove private flags, change version numbers, and create random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially introducing security risks to applications that depend on these packages. The malicious payload can compromise the integrity of the npm ecosystem and affect the reputation of legitimate developers.

How To Fix

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

npm uninstall joint_centipede_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 workaround, you can avoid using the joint_centipede_z3n package altogether. If it is already in your project, consider replacing it with a trusted alternative that provides similar functionality without the associated risks.

Conclusion

The joint_centipede_z3n package poses a significant risk due to its malicious code designed to exploit the npm ecosystem. It is crucial for developers to be vigilant and remove any instances of this package from their projects. Utilizing tools like Vulert can help in monitoring and identifying vulnerabilities in real-time.

See every vulnerability recorded for joint_centipede_z3n →

Share this vulnerability

FAQ

The joint_centipede_z3n package is an npm package that has been identified as part of a malicious campaign to exploit the npm publishing system.

This vulnerability can compromise the integrity of your application by introducing malicious code and potentially leading to security breaches.

You should uninstall the joint_centipede_z3n package immediately and check your project for any references to it in your package-lock.json file.

Yes, tools like Vulert can monitor your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.

How To Fix

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

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