Malicious Code Injection in artificial_armadillo_green-12: A Threat to npm Packages

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99612: Malicious code in artificial_armadillo_green-12 (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The package 'artificial_armadillo_green-12' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to generate and publish derivative packages automatically, often with randomized names, to inflate developer reputation scores for token rewards. Its functionality, while seemingly innocuous, has been compromised by malicious code that alters its behavior.

Vulnerability Detail

The vulnerability in 'artificial_armadillo_green-12' originates from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious payload modifies the package.json file to remove private flags, changes version numbers, and generates random package names, leading to pollution of the npm registry. This can result in developers unknowingly using compromised packages, which may lead to security breaches in their applications.

How To Fix

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

npm uninstall artificial_armadillo_green-12

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 'artificial_armadillo_green-12' package from your project by executing the command: 'npm uninstall artificial_armadillo_green-12'. This will prevent any malicious code from executing until a secure version is available.

Conclusion

The 'artificial_armadillo_green-12' package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to be vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.

See every vulnerability recorded for artificial_armadillo_green-12 →

Share this vulnerability

FAQ

The package contains malicious code that modifies package.json files and floods the npm registry with compromised packages.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.

If you have installed 'artificial_armadillo_green-12', you should uninstall it immediately and check for any updates or patches.

Regularly monitor your dependencies using tools like Vulert and keep your packages updated to their latest secure versions.

Using a compromised package can lead to security breaches, data leaks, and unauthorized access to your application and its users.

How To Fix

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

npm uninstall artificial_armadillo_green-12

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