Malicious Code Injection in internal_tapir_0xrequest Package

internal_tapir_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104357: Malicious code in internal_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 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 internal_tapir_0xrequest package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate interactions within the npm registry but has been compromised to include malicious scripts that manipulate package metadata. The vulnerability stems from its association with a broader trend of malicious packages that aim to inflate developer reputation scores through automated publishing.

Vulnerability Detail

The vulnerability in the internal_tapir_0xrequest package involves 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 these variants. The origin of this vulnerability is linked to a campaign that floods the npm registry with derivative packages, which can severely impact the integrity of the registry and the reputation of developers. The ramifications include potential exposure of sensitive data and the pollution of the npm ecosystem with untrustworthy packages.

How To Fix

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

npm uninstall internal_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, you can remove the internal_tapir_0xrequest package from your project by executing: npm uninstall internal_tapir_0xrequest. This will prevent the execution of the malicious code until a patched version is available.

Conclusion

The internal_tapir_0xrequest package has been identified as containing malicious code that can compromise the integrity of your project. It is crucial to take immediate action by updating or removing the package to protect your application from potential threats. Regular monitoring of your dependencies using tools like Vulert can help maintain the security of your software.

See every vulnerability recorded for internal_tapir_0xrequest →

Share this vulnerability

FAQ

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

The vulnerability can lead to the modification of your package.json file, potentially exposing sensitive data and polluting the npm registry.

You should immediately update or uninstall the internal_tapir_0xrequest package to mitigate the risks associated with this vulnerability.

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 use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.

How To Fix

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

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