Malicious Code Injection in classical_partridge_z3n: A Threat to npm Users
Summary
MAL-2025-93574: Malicious code in classical_partridge_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 'classical_partridge_z3n' is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for rewards associated with the tea protocol. The package's functionality is compromised due to the presence of malicious scripts that alter package metadata.
Vulnerability Detail
The vulnerability originates from malicious code embedded within the 'classical_partridge_z3n' package. This code modifies the package.json file by removing private flags, changing version numbers, and generating random package names. The scripts continuously republish these variants, leading to pollution of the npm registry. The ramifications include potential security risks for developers who unknowingly use these packages, as they may inadvertently incorporate malicious code into their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall classical_partridge_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, you can avoid using the 'classical_partridge_z3n' package and its derivatives. If you need similar functionality, consider using alternative packages that are well-reviewed and have a good security track record.
Conclusion
The 'classical_partridge_z3n' package poses a significant security risk due to its malicious code that alters package metadata and pollutes the npm registry. Developers are advised to uninstall this package and monitor their projects for vulnerabilities using tools like Vulert.
See every vulnerability recorded for classical_partridge_z3n →
FAQ
The malicious code can lead to the unintentional inclusion of harmful scripts in your project, potentially compromising security and functionality.
You can use Vulert to monitor your project for vulnerabilities. By analyzing your package-lock.json file, Vulert can alert you to any open-source vulnerabilities in real-time.
No patched version is available for classical_partridge_z3n. The best course of action is to uninstall the package and avoid using it.
Uninstall the package immediately and review your project for any unintended consequences caused by the malicious code.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
