Malicious Code Vulnerability in ameliamurray Package
Summary
MAL-2025-170825: Malicious code in ameliamurray (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The ameliamurray 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 of applications by providing reusable code. However, it has been identified as part of a malicious campaign that aims to manipulate the npm registry and inflate developer reputation scores through the creation of derivative packages.
Vulnerability Detail
The vulnerability in the ameliamurray package stems from its association with a malicious campaign that generates and publishes numerous derivative packages with randomized names. These packages contain scripts designed to modify the package.json file by removing private flags, altering version numbers, and continuously republishing variants. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to security breaches and loss of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ameliamurrayIf 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 ameliamurray package and consider using alternative packages that provide similar functionality without the associated risks. Always review package dependencies and their reputations before including them in your project.
Conclusion
The ameliamurray package poses significant risks due to its malicious nature, which can compromise the integrity of your project and the npm registry. It is essential to remove this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help you stay informed about potential threats in your open-source software.
See every vulnerability recorded for ameliamurray →
FAQ
The ameliamurray package is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.
Using the ameliamurray package can lead to security risks, including the potential for malicious code execution and pollution of the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without requiring any signup.
If you have used the ameliamurray package, it is recommended to uninstall it immediately and replace it with a secure alternative.
Yes, there are many reputable npm packages available that provide similar functionalities. Always ensure to review the package's reputation and security before use.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
