Malicious Code Injection in decisive_flamingo_z3n: A Threat to npm Packages
Summary
MAL-2025-93938: Malicious code in decisive_flamingo_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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The package 'decisive_flamingo_z3n' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This campaign has been known to flood the npm registry with packages that contain malicious scripts. These scripts are designed to automatically generate and publish derivative packages, which can lead to reputation inflation for developers involved in the tea protocol token rewards. The presence of such malicious packages poses a significant risk to the integrity of the npm registry and the security of applications that depend on these packages.
Vulnerability Detail
The vulnerability in 'decisive_flamingo_z3n' originates from its association with a malicious campaign that utilizes autopublish scripts to manipulate package metadata. The malicious payload modifies the package.json file by removing private flags and altering version numbers. It also generates random package names, contributing to the pollution of the npm registry. This vulnerability can lead to unauthorized access, reputation damage for developers, and potential exploitation of applications that rely on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall decisive_flamingo_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 avoid using the 'decisive_flamingo_z3n' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use the following command to audit your npm packages for vulnerabilities: 'npm audit'.
Conclusion
The decisive_flamingo_z3n package poses a significant threat 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 future vulnerabilities. Utilizing tools like Vulert can help you stay informed about the security status of your dependencies.
See every vulnerability recorded for decisive_flamingo_z3n →
FAQ
The decisive_flamingo_z3n package contains malicious code that modifies package metadata and floods the npm registry with derivative packages.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.
You should uninstall the decisive_flamingo_z3n package immediately using 'npm uninstall decisive_flamingo_z3n' and look for alternative packages.
While specific exploits have not been detailed, the manipulation of package metadata can lead to unauthorized access and reputation damage.
Regularly audit your npm packages using 'npm audit', and consider using tools like Vulert to monitor for vulnerabilities in real-time.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
