Malicious Code Injection in ameliawalker Package: A Threat to npm Users
Summary
MAL-2025-170828: Malicious code in ameliawalker (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 ameliawalker package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate development 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 automatic generation of derivative packages.
Vulnerability Detail
The vulnerability in the ameliawalker package originates from its association with the tea.xyz token reward campaign. This package contains scripts that automatically modify the package.json file to remove private flags, alter version numbers, and generate random package names. The malicious payload continuously republishes these variants, leading to pollution of the npm registry and potential security risks for developers who unknowingly use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ameliawalkerIf 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 measure, you can avoid using the ameliawalker package and replace it with a trusted alternative. Always verify the integrity of packages before installation.
Conclusion
The ameliawalker package poses a significant risk due to its malicious code that alters package configurations and floods the npm registry. It is essential to remove this package from your projects and stay vigilant about the packages you use. Regular monitoring and updates can help mitigate such vulnerabilities.
See every vulnerability recorded for ameliawalker →
FAQ
Ameliawalker is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.
The vulnerability can lead to the installation of compromised packages that may alter your project's dependencies and introduce security risks.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Check your package-lock.json file using the Vulert playground at Vulert Scanner.
You should uninstall the ameliawalker package immediately and review your project's dependencies for any other potentially compromised packages.
Yes, consider using well-established and trusted packages that serve similar functionalities without the associated risks.
