Malicious Code Injection in aoifeoconnor Package: npm Vulnerability
Summary
MAL-2025-170900: Malicious code in aoifeoconnor (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 aoifeoconnor 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 sharing of code within the JavaScript community. However, it has been identified as part of a malicious campaign that exploits the npm registry by flooding it with derivative packages to inflate developer reputation scores for token rewards. This vulnerability poses significant risks to developers relying on npm for secure package management.
Vulnerability Detail
The aoifeoconnor package contains malicious code that modifies the package.json file to remove private flags and changes version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to compromised developer environments, potential data breaches, and a degradation 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 aoifeoconnorIf 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 aoifeoconnor package and replace it with a trusted alternative. Additionally, regularly audit your npm packages using 'npm audit' to identify and address vulnerabilities in your dependencies.
Conclusion
The aoifeoconnor package presents a significant security risk due to its malicious code designed to manipulate the npm registry. Developers should take immediate action to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the integrity of your projects.
See every vulnerability recorded for aoifeoconnor →
FAQ
The aoifeoconnor package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
The vulnerability can compromise your project's security by introducing malicious code that alters your package.json and floods the npm registry with unwanted packages.
You should uninstall the aoifeoconnor package immediately and check your package-lock.json for any references to it.
You can use tools like Vulert, which monitors and alerts you in real-time for open-source vulnerabilities using just your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
