Malicious Code Injection in diverse_tapir_0xrequest Package

diverse_tapir_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101678: Malicious code in diverse_tapir_0xrequest (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 diverse_tapir_0xrequest package is part of the npm ecosystem, primarily used for various JavaScript applications. It is designed to facilitate specific functionalities within applications but has been compromised as part of a larger malicious campaign targeting npm packages. This vulnerability allows attackers to manipulate the package's metadata and behavior, leading to potential security risks for developers and users alike.

Vulnerability Detail

The vulnerability originates from the package being part of a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts that automatically modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only inflates developer reputation scores for token rewards but also pollutes the npm registry, making it difficult to identify legitimate packages. The malicious payload can lead to unauthorized access, data breaches, and a compromised development environment.

How To Fix

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

npm uninstall diverse_tapir_0xrequest

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 diverse_tapir_0xrequest package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your npm packages for vulnerabilities using tools like npm audit.

Conclusion

The diverse_tapir_0xrequest package has been identified as a vector for malicious code injection, posing significant risks to developers and their applications. Immediate action is required to remove the package and mitigate potential security threats. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.

See every vulnerability recorded for diverse_tapir_0xrequest →

Share this vulnerability

FAQ

It is an npm package that has been compromised and is part of a malicious campaign to manipulate package metadata and inflate developer reputation scores.

The vulnerability can lead to unauthorized modifications in your package.json file, potentially exposing your application to security risks and making it difficult to manage dependencies.

You should uninstall the diverse_tapir_0xrequest package immediately and look for alternative packages. Regularly audit your dependencies for vulnerabilities.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can check your application using the Vulert playground without any signup.

Regularly audit your dependencies, use trusted packages, and consider implementing automated tools that monitor for vulnerabilities in your open-source libraries.

How To Fix

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

npm uninstall diverse_tapir_0xrequest

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