Malicious Code Injection in ameliabrown Package: npm Vulnerability Overview
Summary
MAL-2025-170822: Malicious code in ameliabrown (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 ameliabrown package is part of the npm ecosystem, often used for various JavaScript applications. It is primarily involved in token reward campaigns, which have been exploited to manipulate developer reputation scores. This package has been identified as part of a larger scheme that floods the npm registry with malicious variants, affecting the integrity of the ecosystem.
Vulnerability Detail
The vulnerability in the ameliabrown package stems from its association with the tea.xyz token reward campaign. The package contains malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of these variants, polluting the npm registry and potentially compromising the security of applications that depend on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ameliabrownIf 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 ameliabrown package from your project by executing: npm uninstall ameliabrown. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The ameliabrown package has been identified as a vector for malicious code injection, posing significant risks to applications relying on it. It is crucial to monitor for vulnerabilities and take appropriate action to secure your projects. Regularly updating dependencies and using tools like Vulert can help maintain the integrity of your software.
See every vulnerability recorded for ameliabrown →
FAQ
The ameliabrown package is an npm package that has been linked to malicious activities aimed at manipulating developer reputation scores through token reward campaigns.
The vulnerability can lead to the injection of malicious code into your application, potentially compromising its security and integrity.
Yes, you can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.
Absolutely! You can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
If you cannot update the package, consider removing it from your project and looking for alternative packages that do not have known vulnerabilities.
