Malicious Code Injection in yelling_macaw_replicate_automation Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-111286: Malicious code in yelling_macaw_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 yelling_macaw_replicate_automation package is part of the npm ecosystem, primarily used for automation tasks. It is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious packages that flood the npm registry. These packages are designed to inflate developer reputation scores through the automatic generation and publication of derivative packages.

Vulnerability Detail

This vulnerability originates from a malicious payload embedded within the yelling_macaw_replicate_automation package. It modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which can lead to the pollution of the npm registry. The malicious scripts are designed to continuously republish these variants, potentially compromising the integrity of the npm ecosystem and affecting developers who rely on these packages.

How To Fix

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

npm uninstall yelling_macaw_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 prevent the package from being used in your project by removing it from your dependencies and ensuring that your package-lock.json file does not reference it. Additionally, consider using a tool like Vulert to monitor your project for vulnerabilities in real-time.

Conclusion

The yelling_macaw_replicate_automation package contains a serious vulnerability that can compromise the integrity of the npm ecosystem. It is crucial to uninstall this package and monitor your project for any potential vulnerabilities using tools like Vulert.

See every vulnerability recorded for yelling_macaw_replicate_automation →

Share this vulnerability

FAQ

It is an npm package associated with automation tasks but has been compromised with malicious code.

The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project by introducing unwanted packages.

You should uninstall the yelling_macaw_replicate_automation package immediately and check for any dependencies that may be affected.

You can use 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 without signing up.

How To Fix

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

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