Malicious Code Vulnerability in extra_tarantula_0xrequest Package

extra_tarantula_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102434: Malicious code in extra_tarantula_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 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 extra_tarantula_0xrequest package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores. However, it has been identified as containing malicious scripts that compromise the integrity of the npm registry.

Vulnerability Detail

The vulnerability originates from the package's malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants that pollute the npm registry, potentially affecting other developers and users by cluttering the ecosystem and undermining trust in package authenticity.

How To Fix

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

npm uninstall extra_tarantula_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 workaround, avoid using the extra_tarantula_0xrequest package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your dependencies using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The extra_tarantula_0xrequest package has been identified as containing malicious code that compromises the npm registry. It is crucial for developers to remove this package from their projects and to utilize tools like Vulert for ongoing monitoring of vulnerabilities in their dependencies.

See every vulnerability recorded for extra_tarantula_0xrequest →

Share this vulnerability

FAQ

The extra_tarantula_0xrequest package is an npm package involved in the tea.xyz token reward campaign, which has been identified as containing malicious code.

The malicious code modifies your package.json file, removes private flags, and generates random package names, leading to potential pollution of the npm registry and compromising the integrity of your project.

You should uninstall the extra_tarantula_0xrequest package immediately using the command: npm uninstall extra_tarantula_0xrequest.

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

Yes, consider using other reputable packages that provide similar functionality without the associated risks. Always review package details and community feedback before installation.

How To Fix

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

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