Malicious Code Injection in subjective_tuna_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-109232: Malicious code in subjective_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
subjective_tuna_z3n is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which has been known to flood the npm ecosystem with numerous derivative packages. The primary functionality of these packages is to inflate developer reputation scores through automated publishing scripts, which can lead to significant pollution of the npm registry.
Vulnerability Detail
The vulnerability in subjective_tuna_z3n arises from the presence of malicious code designed to manipulate the package.json file. This code removes private flags, alters version numbers, and generates random package names, primarily themed around Indonesian culture. The malicious payload continuously republishes these variants, contributing to the degradation of the npm registry's integrity. This poses risks such as unintentional dependency on compromised packages, potential data breaches, and overall trust erosion in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall subjective_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 workaround, you can avoid using the subjective_tuna_z3n package and replace it with a trusted alternative. Regularly audit your dependencies using tools like npm audit to identify and mitigate vulnerabilities in your project.
Conclusion
The subjective_tuna_z3n package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package metadata and flood the registry with derivative packages. It is crucial for developers to take immediate action by removing this package and monitoring their dependencies for vulnerabilities.
See every vulnerability recorded for subjective_tuna_z3n →
FAQ
The malicious code can lead to the pollution of the npm registry, making it difficult to trust packages and potentially exposing users to security risks.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without needing to sign up.
If you have installed this package, it is recommended to uninstall it immediately and review your project's dependencies for any other potentially malicious packages.
Yes, tools like npm audit and Vulert can help you identify and manage vulnerabilities in your npm packages effectively.
Regularly audit your dependencies, keep your packages updated, and use trusted sources for package installations to minimize the risk of vulnerabilities.
