Malicious Code Injection in Theoretical Salmon 0xRequest Package

theoretical_salmon_0xrequest Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109592: Malicious code in theoretical_salmon_0xrequest (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

Theoretical Salmon 0xRequest is an npm package that is part of the tea.xyz token reward campaign. It is designed to facilitate interactions with the tea protocol, which incentivizes developers through token rewards. However, this package has been compromised, leading to significant security concerns.

Vulnerability Detail

The vulnerability originates from malicious code embedded within the theoretical_salmon_0xrequest package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants to the npm registry, which can lead to reputation inflation for developers and pollution of the registry with potentially harmful packages.

How To Fix

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

npm uninstall theoretical_salmon_0xrequest

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 temporary measure, you can avoid using the theoretical_salmon_0xrequest package and look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The theoretical_salmon_0xrequest package poses a significant security risk due to its embedded malicious code. It is essential to uninstall this package and monitor your project for any vulnerabilities to maintain the integrity of your software.

See every vulnerability recorded for theoretical_salmon_0xrequest →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed for interactions with the tea protocol.

The malicious code modifies your package.json file, removes private flags, and can lead to the publication of harmful packages in the npm registry.

You should uninstall the package immediately using the command npm uninstall theoretical_salmon_0xrequest.

Yes, consider looking for other npm packages that provide similar functionality without the security risks.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can also check your application for vulnerabilities using the Vulert playground at Vulert Scanner.

How To Fix

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

npm uninstall theoretical_salmon_0xrequest

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