Malicious Code Injection in superior_vulture-tool: A Threat to npm Users

superior_vulture-tool Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109316: Malicious code in superior_vulture-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 superior_vulture-tool is an npm package that has been implicated in a malicious campaign targeting developers through the tea.xyz token reward system. This package is designed to automate the generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. Its functionality has been compromised, leading to significant security concerns.

Vulnerability Detail

The vulnerability in superior_vulture-tool stems from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to pollute the npm registry with numerous variants, potentially leading to security risks for developers who unknowingly use these compromised packages. The malicious payload can affect the integrity of applications relying on this package, exposing them to further vulnerabilities.

How To Fix

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

npm uninstall superior_vulture-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 avoid using the superior_vulture-tool package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for 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 superior_vulture-tool package has been identified as a source of malicious code that can compromise the security of applications using it. Developers are advised to uninstall this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can provide additional security measures.

See every vulnerability recorded for superior_vulture-tool →

Share this vulnerability

FAQ

The superior_vulture-tool is an npm package that was part of a malicious campaign aimed at inflating developer reputation scores through automated package publishing.

The vulnerability can lead to the inclusion of malicious code in your application, compromising its security and integrity.

You should uninstall the superior_vulture-tool package immediately and monitor your application for any signs of compromise.

Yes, tools like Vulert can help monitor your project for open-source vulnerabilities in real-time using just the package-lock.json file.

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

How To Fix

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

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