Malicious Code Injection in conventional_salmon_z3n Package
Summary
MAL-2025-93796: Malicious code in conventional_salmon_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 conventional_salmon_z3n package is part of the npm ecosystem and appears to be 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 compromised to include malicious scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability originates from the presence of malicious code within the conventional_salmon_z3n package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants, leading to pollution of the npm registry and potential exploitation by attackers. The primary risk involves the compromise of developer environments and the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall conventional_salmon_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 conventional_salmon_z3n package and any packages that depend on it until a secure version is released. Monitor your package-lock.json file for any dependencies that may introduce this vulnerability.
Conclusion
The conventional_salmon_z3n package has been identified as containing malicious code that can compromise the integrity of the npm ecosystem. It is crucial for developers to take immediate action by removing this package and monitoring their dependencies for similar vulnerabilities. Utilizing tools like Vulert can aid in maintaining a secure development environment.
See every vulnerability recorded for conventional_salmon_z3n →
FAQ
It is an npm package that was part of a token reward campaign but has been found to contain malicious code.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application against the vulnerability using the Vulert playground at Vulert Scanner.
The risks include the compromise of your development environment, potential data breaches, and the pollution of the npm registry.
Currently, the best course of action is to uninstall the affected package and monitor for any updates or patches from the package maintainers.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about vulnerabilities in the packages you use.
