Malicious Code Injection in Unsightly Bison Requirement Package

unsightly_bison_requirement Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-97173: Malicious code in unsightly_bison_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 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 'unsightly_bison_requirement' package is part of a series of npm packages that have been linked to the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. This behavior poses significant risks to the integrity of the npm registry and the security of applications relying on these packages.

Vulnerability Detail

The vulnerability originates from the malicious design of the 'unsightly_bison_requirement' package, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names and continuously republishes variants, leading to pollution of the npm registry. This can result in unintended consequences for developers, including the introduction of insecure code into their applications and potential exploitation by malicious actors.

How To Fix

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

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

If you cannot immediately update the package, consider removing it from your project and replacing it with a secure alternative. Additionally, you can monitor your dependencies for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file to identify potential risks.

Conclusion

The 'unsightly_bison_requirement' package poses a significant security risk due to its malicious design. It is crucial for developers to be aware of this vulnerability and take appropriate action to protect their applications. Regularly updating dependencies and utilizing monitoring tools like Vulert can help mitigate these risks.

See every vulnerability recorded for unsightly_bison_requirement →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation of derivative packages.

The vulnerability can introduce malicious code into your application, potentially compromising its security and integrity.

You should update the package to the latest version or remove it entirely and replace it with a secure alternative.

You can use tools like Vulert, which analyzes your package-lock.json file to alert you of any open-source vulnerabilities in real-time.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

How To Fix

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

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