Malicious Code Injection in Respective_flea_z3n Package
Summary
MAL-2025-107959: Malicious code in respective_flea_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 respective_flea_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic 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 can compromise the integrity of the npm registry.
Vulnerability Detail
The vulnerability in the respective_flea_z3n package 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 variants, polluting the npm registry and potentially affecting other developers and projects relying on npm packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall respective_flea_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 remove the respective_flea_z3n package from your project by executing 'npm uninstall respective_flea_z3n'. This will prevent any malicious code from executing while you seek a secure alternative.
Conclusion
The respective_flea_z3n package has been identified as containing malicious code that can compromise the integrity of the npm registry. It is crucial for developers to take immediate action by updating or uninstalling the package to safeguard their projects. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.
See every vulnerability recorded for respective_flea_z3n →
FAQ
The malicious code can lead to the pollution of the npm registry, affecting the reputation of developers and potentially compromising other projects that depend on npm packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit the Vulert playground at Vulert Scanner to check your application without any signup.
If an immediate update is not possible, consider uninstalling the package as a temporary measure to mitigate risks associated with the vulnerability.
While specific exploits have not been detailed, the nature of the malicious code suggests potential for widespread impact on the npm ecosystem.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about vulnerabilities in the packages you use.
