Malicious Code Injection in armansatria Package: npm Vulnerability Overview

armansatria Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170911: Malicious code in armansatria (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 armansatria package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate token rewards through the generation of derivative packages. However, it has been identified as containing malicious code that can compromise the integrity of the npm registry.

Vulnerability Detail

The vulnerability in the armansatria package stems from its inclusion in a campaign that floods the npm registry with malicious packages. These packages contain scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. The malicious payload continuously republishes these variants, polluting the npm registry and potentially affecting other developers and users relying on the integrity of the npm ecosystem.

How To Fix

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

npm uninstall armansatria

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 measure, you can avoid using the armansatria package and any other packages associated with the tea.xyz token reward campaign. Additionally, consider using npm audit to identify and address vulnerabilities in your project's dependencies.

Conclusion

The armansatria package has been identified as containing malicious code that compromises the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their projects.

See every vulnerability recorded for armansatria →

Share this vulnerability

FAQ

The armansatria package is part of the npm ecosystem and is linked to a token reward campaign that generates derivative packages to inflate developer reputation scores.

The vulnerability can lead to the pollution of the npm registry, potentially affecting your project's dependencies and the overall integrity of the npm ecosystem.

You should remove the armansatria package from your project immediately and monitor for any updates or patches that may address the vulnerability.

You can use tools like npm audit to scan your project for vulnerabilities and receive alerts about any issues in your dependencies.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground at Vulert Scanner without any signup.

How To Fix

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

npm uninstall armansatria

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