Malicious Code Injection in wily_aardwolf_requirement Package

wily_aardwolf_requirement Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-97384: Malicious code in wily_aardwolf_requirement (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 wily_aardwolf_requirement 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, often with randomized names, to inflate developer reputation scores for token rewards. Its functionality is compromised due to the presence of malicious code that alters package metadata.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the wily_aardwolf_requirement package. This payload modifies the package.json file by removing private flags, changing version numbers, and generating random package names that are often themed around Indonesian culture. The malicious scripts (auto.js, autopublish.js, etc.) continuously republish these variants, leading to pollution of the npm registry and potential misuse of developer reputation systems.

How To Fix

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

npm uninstall wily_aardwolf_requirement

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 restrict access to the npm registry or monitor your package dependencies closely to ensure that no malicious packages are being introduced. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.

Conclusion

The wily_aardwolf_requirement package contains malicious code that poses a significant risk to developers and their projects. Immediate action is required to remove the package and prevent further exploitation. Utilizing tools like Vulert can help maintain the security of your dependencies.

See every vulnerability recorded for wily_aardwolf_requirement →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation and publication of packages.

The malicious code modifies your package.json, potentially leading to unauthorized package republishing and reputation inflation.

You should uninstall the package immediately and monitor your project for any unauthorized changes.

Yes, Vulert allows you to monitor your package-lock.json for vulnerabilities in real-time without requiring code access or installation.

Regularly audit your dependencies, use tools like Vulert, and stay informed about known vulnerabilities in the npm ecosystem.

How To Fix

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

npm uninstall wily_aardwolf_requirement

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