Malicious Code Injection in liquid_donkey_0xrequest Package

liquid_donkey_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105202: Malicious code in liquid_donkey_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 liquid_donkey_0xrequest package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate token rewards through automated publishing scripts. However, it has been identified as malicious due to its functionality that modifies package metadata and floods the npm registry with derivative packages.

Vulnerability Detail

The vulnerability originates from the malicious intent behind the liquid_donkey_0xrequest package, which includes scripts that automatically alter the package.json file. These alterations remove private flags, change version numbers, and generate random package names, leading to a polluted npm registry. The ramifications include potential security risks for developers who inadvertently use these packages, as they may unknowingly contribute to the proliferation of malicious software.

How To Fix

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

npm uninstall liquid_donkey_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 manually remove the liquid_donkey_0xrequest package from your project by running the command: npm uninstall liquid_donkey_0xrequest. Additionally, avoid using any packages that are part of the tea.xyz campaign until further notice.

Conclusion

The liquid_donkey_0xrequest package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is essential to remove this package from your projects and monitor for any related vulnerabilities to maintain the integrity of your software.

See every vulnerability recorded for liquid_donkey_0xrequest →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to automate the publishing of derivative packages.

The vulnerability can lead to the introduction of malicious code into your project, potentially compromising security and functionality.

You should uninstall the liquid_donkey_0xrequest package immediately and monitor your project for any unusual behavior.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just package-lock.json. You can check your application for vulnerabilities using the Vulert playground without any signup.

Regularly update your packages, monitor for vulnerabilities using tools like Vulert, and review your package.json and package-lock.json files for any suspicious entries.

How To Fix

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

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