Malicious Code Injection in outside_aardvark_0xrequest Package

outside_aardvark_0xrequest Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106839: Malicious code in outside_aardvark_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 outside_aardvark_0xrequest package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been linked to various malicious activities. It is designed to facilitate the automatic generation and publication of derivative packages, potentially compromising the integrity of the npm registry.

Vulnerability Detail

The vulnerability stems from malicious code embedded within the outside_aardvark_0xrequest package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants, leading to pollution of the npm registry and potentially damaging the reputation of developers and their projects. The source of this vulnerability has been traced back to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms.

How To Fix

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

npm uninstall outside_aardvark_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 prevent the installation of the outside_aardvark_0xrequest package by using npm's package-lock.json file to monitor dependencies. This can help you identify and avoid malicious packages. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The outside_aardvark_0xrequest package contains malicious code that can compromise your project's integrity. It is essential to remove this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help you stay informed and secure your applications against potential threats.

See every vulnerability recorded for outside_aardvark_0xrequest →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, which has been linked to malicious activities.

The vulnerability can lead to the pollution of the npm registry and compromise the integrity of your project by introducing malicious code.

You can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without needing to sign up.

Uninstall the affected package and monitor your dependencies using tools like Vulert to stay informed about vulnerabilities.

Currently, there is no specific patch for the outside_aardvark_0xrequest package, so it is recommended to uninstall it and monitor for updates.

How To Fix

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

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