Malicious Code Injection in violent_thrush_replicate_automation Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-110566: Malicious code in violent_thrush_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 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 'violent_thrush_replicate_automation' package is part of a broader ecosystem that has been exploited for malicious purposes. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with derivative packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores for token rewards. The vulnerability stems from the package's ability to modify its own package.json file, leading to potential security risks.

Vulnerability Detail

The vulnerability in the 'violent_thrush_replicate_automation' package is rooted in its malicious payload, which modifies the package.json file to remove private flags and change version numbers. This allows the package to generate and publish numerous derivative packages with randomized names, effectively polluting the npm registry. The origin of this issue is linked to the tea.xyz token reward campaign, which incentivizes the creation of such malicious packages. The ramifications include compromised package integrity, potential security breaches, and a degraded npm ecosystem.

How To Fix

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

npm uninstall violent_thrush_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 'violent_thrush_replicate_automation' package from your project by executing the command: 'npm uninstall violent_thrush_replicate_automation'. This will prevent any malicious code from executing while you seek a secure alternative.

Conclusion

The 'violent_thrush_replicate_automation' package poses a significant security risk due to its malicious code that alters package metadata. It is crucial to take immediate action by updating or removing the package to safeguard your project. Utilizing tools like Vulert can help you monitor for such vulnerabilities effectively.

See every vulnerability recorded for violent_thrush_replicate_automation →

Share this vulnerability

FAQ

It is an npm package that has been associated with malicious activities, specifically linked to the tea.xyz token reward campaign.

The vulnerability can lead to unauthorized modifications of your package.json file, potentially compromising your project's integrity and security.

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

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.

How To Fix

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

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