Malicious Code Vulnerability in unknown_guppy_replicate_automation Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-110150: Malicious code in unknown_guppy_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

The unknown_guppy_replicate_automation package is part of a broader ecosystem of npm packages that have been associated with the tea.xyz token reward campaign. This package, like others in this category, is designed to automate the generation and publication of derivative packages. Its primary functionality is to inflate developer reputation scores through the creation of numerous packages with randomized names, which can lead to pollution of the npm registry.

Vulnerability Detail

The vulnerability in the unknown_guppy_replicate_automation package stems from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these tainted packages, potentially leading to security breaches in their applications.

How To Fix

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

npm uninstall unknown_guppy_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 avoid using the unknown_guppy_replicate_automation package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your package.json and package-lock.json files to identify and remove any suspicious packages.

Conclusion

The unknown_guppy_replicate_automation package poses a significant risk due to its malicious behavior, which can compromise the integrity of your applications. It is crucial to remove this package and any associated dependencies from your projects. Regular audits and the use of monitoring tools like Vulert can help maintain the security of your software.

See every vulnerability recorded for unknown_guppy_replicate_automation →

Share this vulnerability

FAQ

It is an npm package that is part of a campaign to inflate developer reputation scores by automatically generating and publishing derivative packages.

The malicious code can compromise your application's integrity by introducing unwanted changes and potentially harmful packages into your project.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

You should uninstall the package immediately and review your dependencies for any other potentially harmful packages.

Yes, tools like Vulert can help you monitor your dependencies for vulnerabilities and provide alerts in real-time.

How To Fix

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

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