Malicious Code Injection in aoifeobrien Package: npm Vulnerability Alert
Summary
MAL-2025-170899: Malicious code in aoifeobrien (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 aoifeobrien 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 deployment of JavaScript applications. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages, potentially compromising the integrity of applications that depend on it.
Vulnerability Detail
The vulnerability originates from the aoifeobrien package being linked to a malicious campaign that utilizes autopublish scripts to generate and publish derivative packages with randomized names. This activity is designed to inflate developer reputation scores for token rewards associated with the tea protocol. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and continuously republishing variants, which can lead to pollution of the npm registry and potential exploitation in dependent applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall aoifeobrienIf 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 aoifeobrien package and any other packages that may be part of the malicious campaign. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The aoifeobrien package has been identified as a vector for malicious code injection, which poses significant risks to applications relying on it. Immediate action is required to remove this package and monitor for any potential vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your software.
See every vulnerability recorded for aoifeobrien →
FAQ
The aoifeobrien package is an npm package used in JavaScript development, but it has been identified as part of a malicious campaign.
This vulnerability can lead to the pollution of the npm registry and may compromise the integrity of applications that rely on the aoifeobrien package.
You should remove the aoifeobrien package from your project immediately and monitor for any updates or patches.
You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without any signup.
