Malicious Code Injection in liquid_dingo_z3n: A Threat to npm Packages
Summary
MAL-2025-105201: Malicious code in liquid_dingo_z3n (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The package liquid_dingo_z3n is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, often with randomized names. Its primary function is to inflate developer reputation scores for token rewards, but it has been compromised to include malicious scripts that can manipulate package metadata.
Vulnerability Detail
The vulnerability in liquid_dingo_z3n stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of other packages. The origin of this issue is linked to a broader trend of malicious packages flooding the npm ecosystem, aimed at exploiting the reward systems in place.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall liquid_dingo_z3nIf 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 installation of this package by adding it to your project's .npmrc file with the following line: 'package-lock=false'. This will help mitigate the risk until a permanent fix is applied.
Conclusion
The liquid_dingo_z3n package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain the integrity of their applications.
See every vulnerability recorded for liquid_dingo_z3n →
FAQ
liquid_dingo_z3n is an npm package that is part of a token reward campaign but has been identified as containing malicious code.
The malicious code modifies your package.json file, potentially exposing your project to further vulnerabilities and pollution of the npm registry.
You should uninstall the package immediately using 'npm uninstall liquid_dingo_z3n' and monitor your project for any other vulnerabilities.
Yes, you can use Vulert to monitor and alert for open-source vulnerabilities in your software. You can check your application using the Vulert playground at Vulert Scanner without any signup.
Yes, the behavior of liquid_dingo_z3n can lead to the pollution of the npm registry, which may affect other packages and their integrity.
