Malicious Code Injection in ameliarichards Package: npm Vulnerability Overview
Summary
MAL-2025-170826: Malicious code in ameliarichards (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The ameliarichards package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and distribution of JavaScript applications. However, it has been identified as part of a malicious campaign that seeks to exploit the npm registry by flooding it with derivative packages that have randomized names, ultimately aiming to inflate developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability in the ameliarichards package stems from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of these variants, which pollutes the npm registry and can compromise the integrity of the ecosystem. The malicious code is designed to execute autopublish scripts that automate the creation and publication of these harmful packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ameliarichardsIf 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 avoid using the ameliarichards package and any other packages that may be part of the malicious campaign. Monitor your package-lock.json file for any unexpected changes or additions that may indicate the presence of malicious packages.
Conclusion
The ameliarichards package poses a significant risk due to its malicious behavior aimed at manipulating the npm registry. It is essential to take immediate action by removing this package and monitoring your dependencies for any vulnerabilities. Utilizing tools like Vulert can help you stay informed about potential threats in your open-source projects.
See every vulnerability recorded for ameliarichards →
FAQ
The ameliarichards package is an npm package that has been identified as part of a malicious campaign aimed at flooding the npm registry with harmful derivative packages.
This vulnerability can compromise the integrity of your project by introducing malicious code that alters package configurations and can lead to further exploitation.
If you have installed the ameliarichards package, you should uninstall it immediately using the command npm uninstall ameliarichards.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
