Malicious Code Injection in Subjective Bird Dumbs Package

subjective_bird_dumbs Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109227: Malicious code in subjective_bird_dumbs (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 'subjective_bird_dumbs' package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary functionality of this package is to facilitate the automatic generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. However, this functionality has been exploited to introduce malicious code that compromises the integrity of the npm registry.

Vulnerability Detail

The vulnerability originates from the package being part of a malicious campaign that utilizes autopublish scripts to modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The ramifications include potential security risks for developers who unknowingly install these packages, as well as damage to the reputation of the npm ecosystem as a whole.

How To Fix

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

npm uninstall subjective_bird_dumbs

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 workaround, you can avoid using the 'subjective_bird_dumbs' package altogether. If it is a dependency of another package, consider looking for alternative packages that do not have known vulnerabilities. Additionally, you can use tools like Vulert to monitor your package-lock.json file for vulnerabilities in real-time.

Conclusion

The 'subjective_bird_dumbs' package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the security of their applications.

See every vulnerability recorded for subjective_bird_dumbs →

Share this vulnerability

FAQ

It is an npm package associated with a malicious campaign that generates and publishes derivative packages to inflate developer reputation scores.

If you have this package installed, it can compromise your project's integrity and expose you to security risks.

You should uninstall the package immediately and check for any dependencies that may rely on it.

Yes, you can use Vulert to monitor your package-lock.json file for vulnerabilities without requiring access to the code or installation.

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

How To Fix

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

npm uninstall subjective_bird_dumbs

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