Malicious Code Injection in relevant_centipede_z3n Package - npm Vulnerability

relevant_centipede_z3n Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107851: Malicious code in relevant_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 relevant_centipede_z3n package 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 linked to a series of malicious activities aimed at inflating developer reputation scores. The package's functionality is compromised by malicious scripts that manipulate its metadata and behavior, leading to potential security risks for users.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the relevant_centipede_z3n package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The scripts are designed to autopublish derivative packages, which can pollute the npm registry and compromise the integrity of the ecosystem. Users of this package may unknowingly contribute to the spread of malicious code, leading to further security vulnerabilities in their applications.

How To Fix

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

npm uninstall relevant_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 temporary workaround, you can prevent the installation of the relevant_centipede_z3n package by using npm's package-lock.json file to lock your dependencies. This will help avoid inadvertently installing the malicious package until a fix is implemented.

Conclusion

The relevant_centipede_z3n package poses a significant security risk due to its embedded malicious code. Users are advised to uninstall the package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications by providing real-time alerts for open-source vulnerabilities.

See every vulnerability recorded for relevant_centipede_z3n →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, which has been identified as containing malicious code.

The malicious code modifies your package.json file and can lead to the publication of derivative packages, potentially compromising your application's security.

You should uninstall the relevant_centipede_z3n package immediately and check your project for any other affected dependencies.

You can use Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.

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

How To Fix

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

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