Malicious Code Injection in many_centipede_dumbs: A Threat to npm Packages

many_centipede_dumbs Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105601: Malicious code in many_centipede_dumbs (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 package 'many_centipede_dumbs' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior not only clutters the npm registry but also poses significant risks to developers who may unknowingly use these compromised packages.

Vulnerability Detail

The vulnerability in 'many_centipede_dumbs' originates from its malicious payload, which modifies the package.json file by removing private flags and altering version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants, leading to pollution of the npm registry. This can result in developers inadvertently using compromised packages, exposing their applications to potential security risks.

How To Fix

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

npm uninstall many_centipede_dumbs

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 'many_centipede_dumbs' package altogether and look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The 'many_centipede_dumbs' package poses a significant threat due to its malicious behavior of modifying package files and republishing itself. It is crucial for developers to be vigilant about the packages they use and to regularly check for vulnerabilities to maintain the security of their applications.

See every vulnerability recorded for many_centipede_dumbs →

Share this vulnerability

FAQ

It is an npm package that is part of a malicious campaign to inflate developer reputation scores by flooding the npm registry with derivative packages.

Using the 'many_centipede_dumbs' package can expose your application to security risks, as it modifies critical files and repackages itself with potentially harmful code.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Simply upload your package-lock.json file to check for vulnerabilities without any installation.

You should immediately uninstall the 'many_centipede_dumbs' package and review your project's dependencies for any other potentially malicious packages.

Yes, you can use Vulert's playground at Vulert Scanner to check if your application is affected by vulnerabilities without needing to sign up.

How To Fix

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

npm uninstall many_centipede_dumbs

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