Malicious Code Injection in serious_macaw_0xrequest Package

serious_macaw_0xrequest Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-108561: Malicious code in serious_macaw_0xrequest (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 serious_macaw_0xrequest package is part of a series of npm packages that have been linked to the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for rewards associated with the tea protocol.

Vulnerability Detail

The vulnerability in the serious_macaw_0xrequest package stems from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. This not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to further exploitation or reputation damage.

How To Fix

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

npm uninstall serious_macaw_0xrequest

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 serious_macaw_0xrequest package until a secure version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The serious_macaw_0xrequest package contains a significant vulnerability due to its malicious code that alters package metadata and floods the npm registry. It is essential for developers to take immediate action by updating or removing the package and utilizing tools like Vulert for ongoing monitoring.

See every vulnerability recorded for serious_macaw_0xrequest →

Share this vulnerability

FAQ

It is an npm package linked to the tea.xyz token reward campaign, designed to manipulate the npm registry.

The vulnerability can lead to the injection of malicious code, which may compromise your application's integrity and security.

You should update to the latest patched version of the package or consider removing it from your project until a fix is available.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

How To Fix

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

npm uninstall serious_macaw_0xrequest

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