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

bored_bird-tool Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-100047: Malicious code in bored_bird-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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The bored_bird-tool package is part of the npm ecosystem, primarily used for various development tasks. However, it has been identified as part of a malicious campaign that aims to exploit npm's package publishing system. This package is linked to the tea.xyz token reward scheme, which has been associated with numerous other malicious packages flooding the npm registry.

Vulnerability Detail

The vulnerability in bored_bird-tool stems from its malicious code that modifies the package.json file to remove private flags and changes version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to manipulate developer reputation scores for token rewards. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, leading to potential security breaches in their applications.

How To Fix

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

npm uninstall bored_bird-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, avoid using the bored_bird-tool package and consider alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file for any open-source vulnerabilities.

Conclusion

The bored_bird-tool package poses a significant risk due to its malicious code that manipulates npm's publishing system. It is crucial for developers to be aware of such vulnerabilities and take immediate action to remove affected packages and monitor their projects for security threats.

See every vulnerability recorded for bored_bird-tool →

Share this vulnerability

FAQ

bored_bird-tool is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

The malicious code can lead to unauthorized changes in your project's dependencies, potentially compromising the security and integrity of your application.

You should uninstall the package immediately using 'npm uninstall bored_bird-tool' and monitor your project for any further vulnerabilities.

You can use Vulert's playground at Vulert Scanner to analyze your package-lock.json file for vulnerabilities without requiring any signup.

Yes, consider using other npm packages that provide similar functionality but have a good reputation and are not associated with malicious activities.

How To Fix

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

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