Malicious Code Injection in double_caterpillar_0xrequest Package

double_caterpillar_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101739: Malicious code in double_caterpillar_0xrequest (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 double_caterpillar_0xrequest package is part of the npm ecosystem, primarily used for handling HTTP requests. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages aimed at inflating developer reputation scores for token rewards. This package, like others in the campaign, is designed to manipulate its own metadata and publish variants to the registry.

Vulnerability Detail

The vulnerability in the double_caterpillar_0xrequest package originates from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of the software supply chain. The malicious payload can affect developers by inflating their reputation scores through deceptive practices.

How To Fix

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

npm uninstall double_caterpillar_0xrequest

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 double_caterpillar_0xrequest package and replace it with a trusted alternative for handling HTTP requests. Additionally, you can monitor your project for any malicious packages using tools like Vulert, which analyzes your package-lock.json file for vulnerabilities.

Conclusion

The double_caterpillar_0xrequest package has been identified as a malicious entity within the npm ecosystem, capable of compromising project integrity. It is crucial to remove this package and monitor your dependencies for vulnerabilities to maintain a secure development environment.

See every vulnerability recorded for double_caterpillar_0xrequest →

Share this vulnerability

FAQ

It is an npm package used for handling HTTP requests but has been identified as part of a malicious campaign.

The vulnerability can lead to the pollution of the npm registry and compromise the integrity of your software supply chain.

You should remove the double_caterpillar_0xrequest package from your project immediately.

You can use Vulert to monitor your package-lock.json file for open-source vulnerabilities in real-time.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without any signup.

How To Fix

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

npm uninstall double_caterpillar_0xrequest

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