Malicious Code Injection in aoifereilly Package: A Threat to npm Users
Summary
MAL-2025-170901: Malicious code in aoifereilly (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 aoifereilly package is part of the npm ecosystem, often utilized in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign that aims to exploit npm's publishing system. This package is linked to the tea.xyz token reward scheme, which has led to the proliferation of numerous derivative packages designed to manipulate developer reputation scores.
Vulnerability Detail
The vulnerability in the aoifereilly package stems from its involvement in a malicious campaign that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to clutter the npm registry. This not only compromises the integrity of the npm ecosystem but also poses a risk to developers who may unknowingly use these malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall aoifereillyIf 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 aoifereilly package until a secure version is released. Additionally, consider using alternative packages that provide similar functionalities without the associated risks.
Conclusion
The aoifereilly package poses a significant threat to the npm ecosystem due to its malicious code that alters package metadata and floods the registry with derivative packages. It is essential for developers to stay informed about such vulnerabilities and take proactive measures to secure their projects.
See every vulnerability recorded for aoifereilly →
FAQ
The aoifereilly package is an npm package that has been identified as part of a malicious campaign targeting the npm ecosystem.
If your project uses the aoifereilly package, it may be at risk of having its package.json modified and could inadvertently publish malicious variants to the npm registry.
You should immediately update the package to the latest version or remove it from your project to mitigate any risks.
Yes, tools like Vulert can monitor your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by the aoifereilly vulnerability without needing to sign up.
