Malicious Code Injection in complete_takin_z3n: A Threat to npm Packages
Summary
MAL-2025-93676: Malicious code in complete_takin_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 'complete_takin_z3n' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to automate the generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'complete_takin_z3n' originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of these variants, polluting the npm registry and potentially affecting other developers and users relying on legitimate packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall complete_takin_z3n
If 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 'complete_takin_z3n' package from your project by executing: 'npm uninstall complete_takin_z3n'. This will prevent any malicious code from executing in your environment.
Conclusion
The 'complete_takin_z3n' package poses a significant threat due to its malicious code designed to manipulate npm packages. It is crucial to take immediate action by updating or removing the package to safeguard your application and maintain the integrity of the npm ecosystem.
See every vulnerability recorded for complete_takin_z3n →
FAQ
The package contains malicious code that modifies package.json files and republish variants to pollute the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
Using this package can lead to the exposure of your project to malicious scripts, affecting the integrity of your application and potentially compromising user data.
Regularly monitor your dependencies using tools like Vulert and keep your packages updated to minimize the risk of vulnerabilities.
If immediate removal is not possible, ensure that your project is isolated and monitor it closely for any unusual behavior until you can safely remove the package.