Malicious Code Injection in Sensitive Bovid Dumbs Package

sensitive_bovid_dumbs Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-108539: Malicious code in sensitive_bovid_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 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 'sensitive_bovid_dumbs' package is part of a broader campaign targeting npm packages, specifically designed to exploit the npm registry. It is associated with the tea.xyz token reward initiative, which incentivizes developers to publish numerous packages. This package is intended to automate the publication of derivative packages, often with randomized names, to enhance developer reputation scores for token rewards.

Vulnerability Detail

The vulnerability in 'sensitive_bovid_dumbs' arises from the presence of malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which employs autopublish scripts to inflate developer reputation scores. The ramifications include potential security risks for developers who inadvertently use these packages, as well as the degradation of the npm registry's integrity.

How To Fix

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

npm uninstall sensitive_bovid_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 temporary workaround, you can avoid using the 'sensitive_bovid_dumbs' package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time.

Conclusion

The 'sensitive_bovid_dumbs' package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. Developers are advised to remove this package and monitor their dependencies for vulnerabilities using tools like Vulert.

See every vulnerability recorded for sensitive_bovid_dumbs →

Share this vulnerability

FAQ

It is an npm package associated with a token reward campaign that automates the publication of derivative packages.

The vulnerability can lead to the introduction of malicious code into your project, compromising its security and integrity.

You should remove the package from your project and monitor for any updates or patches that may address the vulnerability.

You can use tools like Vulert, which monitors 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 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 sensitive_bovid_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