Malicious Code Injection in weak_swordfish-tool: A Threat to npm Packages

weak_swordfish-tool Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-110767: Malicious code in weak_swordfish-tool (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

The weak_swordfish-tool package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate development by providing reusable code. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to potential security risks for developers and their applications.

Vulnerability Detail

The vulnerability in weak_swordfish-tool stems from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts designed to modify the package.json file, removing private flags and changing version numbers. The malicious payload generates random package names and continuously republishes variants, which can lead to pollution of the npm registry and compromise the integrity of dependent applications. This vulnerability poses significant risks, including unauthorized access to sensitive data and disruption of development workflows.

How To Fix

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

npm uninstall weak_swordfish-tool

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 workaround, you can remove the weak_swordfish-tool package from your project by executing the following command: npm uninstall weak_swordfish-tool. This will prevent any potential malicious activity associated with the package until a fix is applied.

Conclusion

The weak_swordfish-tool package presents a significant security risk due to its malicious code injection vulnerability. It is essential for developers to take immediate action by updating or removing the package and utilizing monitoring tools like Vulert to safeguard their applications against potential threats.

See every vulnerability recorded for weak_swordfish-tool →

Share this vulnerability

FAQ

weak_swordfish-tool is an npm package that has been identified as part of a malicious campaign targeting the npm registry.

The vulnerability can lead to unauthorized modifications of your package.json file, potentially compromising your application's integrity and security.

You should uninstall the package immediately and monitor your application for any unusual behavior.

Yes, you can use Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.

Regularly update your dependencies, use tools like Vulert for monitoring, and review package sources before installation.

How To Fix

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

npm uninstall weak_swordfish-tool

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