Malicious Code Injection in melted_sawfish_0xrequest: A Threat to npm Ecosystem

melted_sawfish_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105789: Malicious code in melted_sawfish_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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package 'melted_sawfish_0xrequest' is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate npm's publishing system by generating and publishing derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for rewards, but it introduces significant risks to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in 'melted_sawfish_0xrequest' stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This allows the package to continuously republish variants, polluting the npm registry and potentially leading to the distribution of compromised software. The origin of this vulnerability is linked to the broader trend of malicious packages flooding the npm ecosystem, specifically targeting developers involved in the tea protocol token rewards.

How To Fix

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

npm uninstall melted_sawfish_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 prevent the installation of this malicious package by using npm's package-lock.json to monitor your dependencies. Additionally, consider using tools like Vulert to alert you in real-time for open-source vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The 'melted_sawfish_0xrequest' package poses a significant risk due to its malicious code designed to manipulate the npm ecosystem. It is crucial for developers to remove this package and utilize tools like Vulert to monitor for vulnerabilities in their projects.

See every vulnerability recorded for melted_sawfish_0xrequest →

Share this vulnerability

FAQ

'melted_sawfish_0xrequest' is an npm package that has been identified as malicious, designed to manipulate the npm registry for token reward schemes.

This vulnerability can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.

You should remove the 'melted_sawfish_0xrequest' package from your project and monitor for any updates or patches.

Yes, regularly audit your dependencies, use tools like Vulert for real-time monitoring, and be cautious of packages with unusual behaviors.

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

How To Fix

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

npm uninstall melted_sawfish_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