Malicious Code Injection in Ameliascott Package: npm Vulnerability Overview

ameliascott Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170827: Malicious code in ameliascott (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The Ameliascott package is part of the npm ecosystem, which is widely used for JavaScript package management. It is designed to facilitate the development and distribution of JavaScript applications. However, this package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the creation of derivative packages with randomized names, leading to potential security risks for users.

Vulnerability Detail

The vulnerability in the Ameliascott package originates from its association with the tea.xyz token reward campaign. This campaign utilizes malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. The continuous republishing of these variants can pollute the npm registry, making it difficult for developers to trust the integrity of packages. The ramifications include potential exposure to malicious code and compromised application security.

How To Fix

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

npm uninstall ameliascott

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

Conclusion

The Ameliascott package has been compromised by malicious code that poses significant risks to developers and their applications. It is crucial to take immediate action by updating or removing the package to safeguard your projects. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.

See every vulnerability recorded for ameliascott →

Share this vulnerability

FAQ

Ameliascott is a package in the npm ecosystem used for JavaScript development, but it has been identified as part of a malicious campaign.

The vulnerability can lead to the injection of malicious code, compromising the security and integrity of your application.

You should update the package to the latest version or uninstall it until a secure version is released.

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

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected without any signup.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall ameliascott

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