Malicious Code Injection in inquisitive_centipede-appteadev: A Threat to npm Packages

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104241: Malicious code in inquisitive_centipede-appteadev (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 Penetration testing for web, API and mobile 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 inquisitive_centipede-appteadev is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores for token rewards, making them a significant concern for developers relying on npm for their projects.

Vulnerability Detail

The vulnerability stems from the malicious code embedded within the inquisitive_centipede-appteadev package. It modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which leads to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also poses a risk of unintentional dependency on compromised packages, potentially leading to security breaches in applications that utilize them.

How To Fix

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

npm uninstall inquisitive_centipede-appteadev

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 inquisitive_centipede-appteadev package and instead rely on alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your npm packages using the command: npm audit.

Conclusion

The inquisitive_centipede-appteadev package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. It is essential for developers to remove this package and monitor their dependencies closely to maintain the security of their applications.

See every vulnerability recorded for inquisitive_centipede-appteadev →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

The vulnerability can lead to the injection of malicious code into your application, potentially compromising its security and integrity.

You should immediately remove the inquisitive_centipede-appteadev package from your project and check for any dependencies that may have been affected.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.

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 inquisitive_centipede-appteadev

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