Malicious Code Detected in obedient_centipede_z3n: A Threat to npm Ecosystem

obedient_centipede_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-95702: Malicious code in obedient_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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

obedient_centipede_z3n is an npm package that appears to be part of a token reward campaign associated with the tea.xyz protocol. This package is designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. It is particularly vulnerable due to its malicious payload that alters package metadata.

Vulnerability Detail

The vulnerability in obedient_centipede_z3n originates from its association with a campaign that floods the npm registry with malicious packages. The malicious code modifies the package.json file to remove private flags, changes version numbers, and generates random package names. This behavior can lead to pollution of the npm registry, potentially compromising the integrity of other packages and affecting developers' workflows.

How To Fix

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

npm uninstall obedient_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 avoid using the obedient_centipede_z3n package and look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The obedient_centipede_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 monitor for any updates or patches. Utilizing tools like Vulert can help in identifying and managing vulnerabilities effectively.

See every vulnerability recorded for obedient_centipede_z3n →

Share this vulnerability

FAQ

obedient_centipede_z3n is an npm package involved in a token reward campaign that generates and publishes malicious packages.

The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your project and other packages.

You should uninstall the obedient_centipede_z3n package immediately and check for any updates or patches.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just package-lock.json.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

How To Fix

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

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