Malicious Code Injection in senior_tapir_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-96515: Malicious code in senior_tapir_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 'senior_tapir_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 derivative packages with randomized names. This behavior is primarily aimed at inflating developer reputation scores for token rewards, making the package a potential vector for malicious activities.
Vulnerability Detail
The vulnerability in 'senior_tapir_z3n' stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This results in the continuous republishing of variants that can pollute the npm registry, leading to potential security risks and loss of trust in the ecosystem. The malicious payload can compromise the integrity of the npm registry and affect developers relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall senior_tapir_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 workaround, you can temporarily avoid using the 'senior_tapir_z3n' package by removing it from your project dependencies. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The 'senior_tapir_z3n' package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for senior_tapir_z3n →
FAQ
The primary risk is that it modifies package.json files and repopulates the npm registry with potentially harmful packages, which can compromise the integrity of your project.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time. You can check your application against this vulnerability using the Vulert playground at Vulert Scanner.
Currently, there is no patch available. It is advisable to remove the package from your project until a secure version is released.
You should remove the package immediately and review your project for any potential impacts caused by its use.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about the latest security advisories related to the packages you use.
