Malicious Code Injection in flexible_armadillo_requirement Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-94541: Malicious code in flexible_armadillo_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 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 flexible_armadillo_requirement package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is designed to facilitate specific functionalities within applications that utilize the npm registry. However, it has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages.

Vulnerability Detail

The vulnerability stems from the package's involvement in the tea.xyz token reward campaign, which has been flooding the npm registry with malicious packages. These packages contain scripts that automatically modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly install these malicious packages, leading to potential exploitation of their applications.

How To Fix

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

npm uninstall flexible_armadillo_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 remove the flexible_armadillo_requirement package from your project by executing the following command: npm uninstall flexible_armadillo_requirement. This will prevent any malicious code from executing while you seek a secure alternative.

Conclusion

The flexible_armadillo_requirement package has been identified as a vector for malicious code injection, posing significant risks to developers and their applications. It is essential to take immediate action by updating or removing the package to safeguard your projects.

See every vulnerability recorded for flexible_armadillo_requirement →

Share this vulnerability

FAQ

It is an npm package used in JavaScript applications, but it has been identified as part of a malicious campaign.

The vulnerability can lead to the installation of malicious code that compromises your application's integrity and security.

You should uninstall the package immediately and check for any updates or patches that may address the vulnerability.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without requiring any signup.

How To Fix

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

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