Malicious Code Injection in capable_limpet_z3n: A Threat to npm Packages

capable_limpet_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-93466: Malicious code in capable_limpet_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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

capable_limpet_z3n is an npm package that has been identified as part of a malicious campaign targeting the npm ecosystem. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package lies in its ability to manipulate other packages within the npm registry, potentially leading to widespread issues for developers relying on these packages.

Vulnerability Detail

The vulnerability in capable_limpet_z3n originates from its design to include autopublish scripts that automatically generate and publish derivative packages with randomized names. This behavior is intended to remove private flags from package.json, alter version numbers, and continuously republish variants, thereby polluting the npm registry. The ramifications of this vulnerability include the potential for developers to unknowingly use compromised packages, leading to security risks and integrity issues within their applications.

How To Fix

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

npm uninstall capable_limpet_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 capable_limpet_z3n package altogether until a secure version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The capable_limpet_z3n package poses a significant threat due to its malicious code that manipulates npm packages. Developers should take immediate action to remove this package and monitor their applications for vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your software.

See every vulnerability recorded for capable_limpet_z3n →

Share this vulnerability

FAQ

capable_limpet_z3n is an npm package involved in a malicious campaign that aims to inflate developer reputation scores by publishing derivative packages.

This vulnerability can lead to the inclusion of compromised packages in your application, which may introduce security risks and affect the integrity of your software.

If you have used capable_limpet_z3n, it is crucial to remove it from your project and update to a secure version or use alternative packages.

You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file.

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

How To Fix

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

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