Malicious Code Injection in supreme_hummingbird_requirement Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96883: Malicious code in supreme_hummingbird_requirement (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 supreme_hummingbird_requirement package is part of the npm ecosystem, often utilized for various JavaScript applications. This package has been identified as part of a broader malicious campaign that exploits npm's package management system. Its primary functionality is to facilitate the installation of dependencies for JavaScript projects, but it has been compromised to serve malicious purposes.

Vulnerability Detail

The vulnerability stems from the package being associated with the tea.xyz token reward campaign, which has led to the proliferation of malicious packages in the npm registry. The malicious code within supreme_hummingbird_requirement modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior can lead to the pollution of the npm registry, potentially affecting developers' reputations and the integrity of their projects.

How To Fix

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

npm uninstall supreme_hummingbird_requirement

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 supreme_hummingbird_requirement package from your project by executing the command: npm uninstall supreme_hummingbird_requirement. This will prevent any malicious code from executing while you seek a secure alternative.

Conclusion

The supreme_hummingbird_requirement package has been identified as containing malicious code that can compromise the integrity of JavaScript projects. It is crucial to update or remove this package to protect your applications from potential threats. Utilizing tools like Vulert can help you stay informed about vulnerabilities in your dependencies.

See every vulnerability recorded for supreme_hummingbird_requirement →

Share this vulnerability

FAQ

It is an npm package used in JavaScript applications, but it has been compromised to include malicious code.

The malicious code modifies your package.json file, potentially leading to the publication of unauthorized packages and affecting your project's integrity.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground at Vulert Scanner without signing up.

As a temporary measure, you can uninstall the package to prevent any malicious actions while you look for a secure alternative.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert and keep your packages updated to their latest secure versions.

How To Fix

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

npm uninstall supreme_hummingbird_requirement

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