Malicious Code Injection in only_parakeet_z3n: A Threat to npm Packages
Summary
MAL-2025-106734: Malicious code in only_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
Background
The package 'only_parakeet_z3n' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often include scripts designed to manipulate package metadata and inflate developer reputation scores, making them a significant threat to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'only_parakeet_z3n' originates from its association with malicious scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants that pollute the npm registry. This not only compromises the security of the affected package but also affects the overall trustworthiness of the npm ecosystem, potentially leading to further exploitation by malicious actors.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall only_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 workaround, you can remove the 'only_parakeet_z3n' package from your project by executing the command: 'npm uninstall only_parakeet_z3n'. This will prevent any malicious scripts from executing while you seek a secure alternative.
Conclusion
The 'only_parakeet_z3n' package poses a significant security risk due to its malicious code that alters package metadata. It is crucial for developers to stay informed about vulnerabilities and take proactive measures, such as updating packages and using tools like Vulert, to ensure the security of their applications.
See every vulnerability recorded for only_parakeet_z3n →
FAQ
The vulnerability involves malicious code that modifies package metadata and repackages it under random names, compromising the integrity of the npm registry.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. By utilizing the Vulert playground, you can check if your application is affected without any signup.
The consequences include the risk of your application being compromised, as well as contributing to the pollution of the npm registry, which can affect other developers.
It is advisable to check for updates regularly. If a patched version is available, you can update the package using 'npm update only_parakeet_z3n'.
If immediate updates are not possible, consider uninstalling the package as a temporary measure to prevent any potential exploitation.
