Malicious Code Injection in implicit_salmon_z3n: A Threat to npm Packages

implicit_salmon_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-103993: Malicious code in implicit_salmon_z3n (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

implicit_salmon_z3n is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package, like others in the campaign, is designed to exploit the npm ecosystem by generating and publishing derivative packages with randomized names. Its primary function is to inflate developer reputation scores for token rewards associated with the tea protocol, making it a significant concern for developers relying on npm for package management.

Vulnerability Detail

The vulnerability in implicit_salmon_z3n stems from its malicious code that modifies the package.json file to remove private flags and change version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants, leading to pollution of the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly install these malicious packages, potentially leading to security breaches in their applications.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall implicit_salmon_z3n

If 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 remove the implicit_salmon_z3n package from your project by running 'npm uninstall implicit_salmon_z3n'. Additionally, consider using tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time, allowing you to stay informed about potential threats without needing to access the code directly.

Conclusion

The implicit_salmon_z3n package poses a significant threat due to its malicious code designed to manipulate the npm registry. Developers are urged to take immediate action by updating or removing the package and utilizing tools like Vulert to monitor for vulnerabilities. Staying informed and proactive is essential in maintaining the security of your applications.

See every vulnerability recorded for implicit_salmon_z3n →

Share this vulnerability

FAQ

implicit_salmon_z3n is an npm package that has been identified as part of a malicious campaign aimed at exploiting the npm ecosystem.

The vulnerability can lead to the installation of malicious packages that compromise the integrity of your application and may expose it to security risks.

You should immediately uninstall the implicit_salmon_z3n package and check for any other affected packages in your project.

Yes, you can use Vulert to monitor your package-lock.json for vulnerabilities in real-time without requiring access to the code or installation.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall implicit_salmon_z3n

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback