Malicious Code Injection in automatic_tuna_z3n: A Threat to npm Packages
Summary
MAL-2025-93309: Malicious code in automatic_tuna_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 'automatic_tuna_z3n' is part of a series of npm packages that have been 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.
Vulnerability Detail
The vulnerability in 'automatic_tuna_z3n' stems from its inclusion in a malicious campaign that employs scripts to modify package.json files. These modifications remove private flags, alter version numbers, and create random package names, leading to the continuous republishing of these variants. This not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to security breaches and loss of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall automatic_tuna_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 'automatic_tuna_z3n' package and any other packages that may be part of the tea.xyz campaign. Regularly audit your npm packages to ensure that no malicious packages are present.
Conclusion
The 'automatic_tuna_z3n' package poses a significant risk due to its malicious behavior aimed at manipulating the npm registry. It is crucial for developers to be vigilant and take immediate action to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your projects.
See every vulnerability recorded for automatic_tuna_z3n →
FAQ
It is an npm package associated with a malicious campaign that aims to inflate developer reputation scores through the creation of numerous derivative packages.
The vulnerability can lead to the introduction of malicious code into your project, potentially compromising security and functionality.
You should uninstall the 'automatic_tuna_z3n' package immediately and audit your project for any other potentially malicious packages.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without requiring any signup.
