Malicious Code Injection in quail_amethyst-73: A Threat to npm Ecosystem

quail_amethyst-73 Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-98285: Malicious code in quail_amethyst-73 (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

quail_amethyst-73 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. The package's functionality is compromised due to the presence of malicious scripts that manipulate its metadata and behavior.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the quail_amethyst-73 package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. It continuously republishes these variants to pollute the npm registry, posing a significant risk to developers relying on the integrity of npm packages. The malicious code can lead to unauthorized access, data leakage, and a compromised development environment.

How To Fix

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

npm uninstall quail_amethyst-73

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, avoid using the quail_amethyst-73 package and monitor your project for any unauthorized changes. Regularly check your package-lock.json file for any unexpected modifications.

Conclusion

The quail_amethyst-73 package poses a significant risk due to its embedded malicious code that alters package metadata and republish behavior. It is crucial to uninstall this package and monitor your project for any unauthorized changes. Utilizing tools like Vulert can help maintain the security of your software.

See every vulnerability recorded for quail_amethyst-73 →

Share this vulnerability

FAQ

quail_amethyst-73 is an npm package involved in the tea.xyz token reward campaign, which has been found to contain malicious code.

The malicious code modifies your package.json file, removes private flags, and can lead to the publication of unauthorized packages, compromising your project's integrity.

You should uninstall the package immediately using the command: npm uninstall quail_amethyst-73.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check your application for vulnerabilities using the Vulert playground at Vulert Scanner.

Regularly update your dependencies, monitor for vulnerabilities, and utilize tools like Vulert to receive real-time alerts.

How To Fix

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

npm uninstall quail_amethyst-73

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