Malicious Code Injection in typical_cuckoo_z3n: A Threat to npm Packages
Summary
MAL-2025-109897: Malicious code in typical_cuckoo_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 typical_cuckoo_z3n is part of the npm ecosystem and appears to be associated with the tea.xyz token reward campaign. This campaign has been known to flood the npm registry with packages that contain malicious scripts designed to manipulate package metadata and inflate developer reputation scores. The typical functionality of such packages is to automate the publishing process, but in this case, it has been exploited for malicious purposes.
Vulnerability Detail
The vulnerability in typical_cuckoo_z3n originates from its inclusion in a malicious campaign that modifies 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 can lead to a loss of trust in the npm ecosystem, potential security risks for applications relying on these packages, and an overall degradation of the quality of available packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall typical_cuckoo_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 using npm's package-lock.json to lock your dependencies. Ensure that your project does not include typical_cuckoo_z3n by checking your package.json and removing any references to it.
Conclusion
The typical_cuckoo_z3n package poses a significant threat due to its malicious code designed to manipulate npm package metadata. It is crucial for developers to be vigilant, remove affected packages, and utilize tools like Vulert to monitor for vulnerabilities in their applications.
See every vulnerability recorded for typical_cuckoo_z3n →
FAQ
Typical_cuckoo_z3n is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.
The vulnerability can lead to the installation of malicious code, which may compromise your application's security and integrity.
You should uninstall the package immediately and check your application for any potential security issues.
Yes, you can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about known vulnerabilities in the npm ecosystem.
