Malicious Code Vulnerability in kind_aardvark_0xrequest Package

kind_aardvark_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104821: Malicious code in kind_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 kind_aardvark_0xrequest package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is implicated in a malicious campaign that aims to exploit the npm registry by generating and publishing numerous derivative packages with altered metadata. The primary functionality of this package is overshadowed by its malicious intent, which involves manipulating package information to inflate developer reputation scores for token rewards.

Vulnerability Detail

The vulnerability originates from the kind_aardvark_0xrequest package being part of a broader malicious campaign associated with the tea.xyz token reward system. The package contains scripts that automatically modify package.json files to remove private flags, change version numbers, and create random package names. This leads to the continuous republishing of these variants, which pollutes the npm registry and can compromise the integrity of the ecosystem. The ramifications include potential security risks for developers who unknowingly use these packages, as well as damage to the reputation of the npm registry itself.

How To Fix

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

npm uninstall kind_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 workaround, you can replace the functionality provided by kind_aardvark_0xrequest with a trusted alternative package that serves a similar purpose. Always verify the integrity and reputation of any package before including it in your project.

Conclusion

The kind_aardvark_0xrequest package is associated with a malicious campaign that poses significant risks to developers and the npm ecosystem. Immediate action is required to remove this package and replace it with trusted alternatives. Regular monitoring of dependencies is crucial to maintain the security of your projects.

See every vulnerability recorded for kind_aardvark_0xrequest →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.

Using this package can lead to security risks and may compromise the integrity of your project's dependencies.

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

Yes, you should look for trusted alternatives that provide similar functionality without the associated risks.

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 at Vulert Scanner without needing to sign up.

How To Fix

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

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