Malicious Code Injection in Giant Dog Replicate Automation Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-103118: Malicious code in giant_dog_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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The 'giant_dog_replicate_automation' package is part of the npm ecosystem and is designed to automate certain tasks related to package management. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities. This package is associated with the tea.xyz token reward scheme, which has led to the proliferation of numerous derivative packages aimed at inflating developer reputation scores.

Vulnerability Detail

The vulnerability originates from malicious code embedded within the 'giant_dog_replicate_automation' package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which are often themed around Indonesian culture. The malicious payload continuously republishes these variants, leading to pollution of the npm registry and potential security risks for developers who may unknowingly use these compromised packages.

How To Fix

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

npm uninstall giant_dog_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 'giant_dog_replicate_automation' package from your project by executing the command: 'npm uninstall giant_dog_replicate_automation'. This will prevent any malicious code from executing until a secure version is available.

Conclusion

The 'giant_dog_replicate_automation' package poses a significant security risk due to its embedded malicious code. It is crucial for developers to stay informed about such vulnerabilities and take immediate action to protect their projects. Regular updates and monitoring using tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for giant_dog_replicate_automation →

Share this vulnerability

FAQ

It is an npm package designed for automation tasks, but it has been compromised with malicious code.

The malicious code modifies your package.json, removes private flags, and can lead to the publication of harmful variants, affecting your project's integrity.

You should uninstall the package immediately and check your project for any unauthorized changes.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access.

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

How To Fix

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

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