Malicious Code Injection in Yabbering Caterpillar Replicate Automation Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-111142: Malicious code in yabbering_caterpillar_replicate_automation (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

Yabbering Caterpillar Replicate Automation is an npm package that is part of a broader token reward campaign associated with the tea.xyz protocol. This package is designed to automate certain tasks, but it has been compromised to include malicious scripts that manipulate its functionality. The vulnerability arises from the package's design, which allows for the automatic generation and publication of derivative packages, potentially leading to reputation inflation for developers involved in the campaign.

Vulnerability Detail

The vulnerability in the Yabbering Caterpillar Replicate Automation package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags and alters version numbers. It generates random package names and continuously republishes variants to pollute the npm registry. This not only affects the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these compromised packages, leading to potential security breaches in their applications.

How To Fix

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

npm uninstall yabbering_caterpillar_replicate_automation

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 remove the Yabbering Caterpillar Replicate Automation package from your project if it is not essential. Use the following command to uninstall it: npm uninstall yabbering_caterpillar_replicate_automation. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.

Conclusion

The Yabbering Caterpillar Replicate Automation package has been identified as containing malicious code that can compromise the security of applications using it. It is crucial for developers to take immediate action by updating or removing the package and utilizing tools like Vulert to monitor for vulnerabilities in their projects.

See every vulnerability recorded for yabbering_caterpillar_replicate_automation →

Share this vulnerability

FAQ

It is an npm package that automates certain tasks but has been compromised to include malicious scripts.

The vulnerability can lead to the inclusion of malicious code in your application, potentially compromising its security.

You should immediately update or uninstall the package to prevent any security risks.

You can use Vulert, which monitors your package-lock.json 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 yabbering_caterpillar_replicate_automation

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