Malicious Code Injection in chubby_leopon_replicate_automation Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-100411: Malicious code in chubby_leopon_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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The chubby_leopon_replicate_automation package is part of the npm ecosystem and is associated with automated publishing scripts. It is designed to facilitate the generation and publication of derivative packages, often to inflate developer reputation scores within the tea.xyz token reward campaign. This package, however, has been identified as containing malicious code that compromises its integrity and the security of the npm registry.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the chubby_leopon_replicate_automation package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which are often Indonesian-themed. The primary risk is that it enables the continuous republishing of these variants, leading to pollution of the npm registry and potential exploitation of developers' reputations. The malicious nature of this package can lead to severe ramifications, including unauthorized access to sensitive data and disruption of legitimate package management processes.

How To Fix

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

npm uninstall chubby_leopon_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 measure, you can avoid using the chubby_leopon_replicate_automation package altogether. If you have dependencies relying on it, consider replacing them with alternative packages that do not have known vulnerabilities.

Conclusion

The chubby_leopon_replicate_automation package has been identified as containing malicious code that poses significant risks to developers and the npm ecosystem. Immediate action is required to remove the package and prevent further exploitation. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.

See every vulnerability recorded for chubby_leopon_replicate_automation →

Share this vulnerability

FAQ

It is an npm package designed for automated publishing of derivative packages, often linked to the tea.xyz token reward campaign.

The malicious code modifies your package.json file and can lead to the pollution of the npm registry, potentially harming your project's reputation.

You should uninstall the package immediately using npm uninstall chubby_leopon_replicate_automation and check for any alternative solutions.

Yes, you can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.

Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated on security advisories related to the packages you use.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

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