Malicious Code Injection in present_bovid-appteadev: npm Package Vulnerability

present_bovid-appteadev Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107224: Malicious code in present_bovid-appteadev (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The present_bovid-appteadev package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate certain functionalities related to token rewards but has been compromised, leading to significant security risks. The vulnerability stems from malicious scripts that manipulate the package's metadata and behavior, posing a threat to developers and users alike.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the present_bovid-appteadev package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The intent is to inflate developer reputation scores through the automatic generation and publication of derivative packages. This behavior can lead to the pollution of the npm registry, making it difficult for developers to trust legitimate packages and potentially exposing them to further security risks.

How To Fix

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

npm uninstall present_bovid-appteadev

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 measure, avoid using the present_bovid-appteadev package until it has been confirmed safe. Regularly monitor your project's dependencies and consider using tools like Vulert to check for vulnerabilities in your package-lock.json file. You can use Vulert's playground at https://vulert.com/scanner to assess if your application is affected by this vulnerability without needing to sign up.

Conclusion

The present_bovid-appteadev package has been identified as containing malicious code that poses a significant security risk. It is crucial for developers to take immediate action by removing the package and monitoring their projects for vulnerabilities. Utilizing tools like Vulert can help in maintaining the security of your applications.

See every vulnerability recorded for present_bovid-appteadev →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to facilitate token rewards.

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

You should uninstall the package immediately using 'npm uninstall present_bovid-appteadev' and monitor your project for any unusual behavior.

Yes, regularly audit your dependencies, use tools like Vulert to monitor vulnerabilities, and only install packages from trusted sources.

Yes, you can use Vulert's playground at Vulert Scanner to check for vulnerabilities in your application without needing to sign up.

How To Fix

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

npm uninstall present_bovid-appteadev

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