Malicious Code Injection in Dangerous Parakeet Z3N: A Threat to npm Packages
Summary
MAL-2025-98669: Malicious code in dangerous_parakeet_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
Dangerous Parakeet Z3N is an npm package that has been identified as part of a malicious campaign targeting the npm ecosystem. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The package's functionality is compromised, making it a vector for malicious activities.
Vulnerability Detail
The vulnerability originates from the package's design, which includes autopublish scripts that modify the package.json file to remove private flags and change version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only affects the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these compromised packages, leading to potential security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall dangerous_parakeet_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 measure, avoid using the dangerous_parakeet_z3n package and consider using alternative packages that provide similar functionality without the associated risks. Always validate the source of your npm packages before installation.
Conclusion
The dangerous_parakeet_z3n package poses significant risks due to its malicious behavior of modifying package metadata and flooding the npm registry. It is crucial for developers to remove this package from their projects and adopt safer practices when managing dependencies. Utilizing tools like Vulert can help in identifying vulnerabilities and maintaining the security of applications.
See every vulnerability recorded for dangerous_parakeet_z3n →
FAQ
It is an npm package identified as part of a malicious campaign that modifies package metadata and floods the npm registry with derivative packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application against the vulnerability using the Vulert playground at Vulert Scanner.
Using compromised packages can lead to security vulnerabilities, data breaches, and potential exploitation of your application by malicious actors.
There is no patch available for this specific package. The recommended action is to uninstall it and avoid using it.
Regularly audit your dependencies, use trusted sources for packages, and employ 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.
