Malicious Code Injection in aislingobrien Package: npm Vulnerability Overview
Summary
MAL-2025-170744: Malicious code in aislingobrien (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 aislingobrien package is part of the npm ecosystem, primarily used for various JavaScript applications. It has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is designed to manipulate developer reputation scores through the automatic generation and publication of numerous variants, which can lead to significant pollution of the npm registry.
Vulnerability Detail
The vulnerability in the aislingobrien package stems from its association with a malicious campaign that employs scripts to modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, which are then republished continuously. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which aims to inflate developer reputation scores. The ramifications include potential security risks for applications relying on this package, as well as the degradation of the npm registry's integrity.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall aislingobrienIf 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 aislingobrien package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your dependencies using tools like Vulert, which can alert you to vulnerabilities in your package-lock.json file.
Conclusion
The aislingobrien package poses a significant security risk due to its malicious nature and association with a campaign aimed at manipulating npm registry integrity. It is essential to remove this package from your projects and monitor your dependencies for vulnerabilities to maintain application security.
See every vulnerability recorded for aislingobrien →
FAQ
The aislingobrien package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic generation of derivative packages.
This vulnerability can lead to security risks, including the potential for malicious code execution and the pollution of the npm registry, which may affect the integrity of your application's dependencies.
You should uninstall the aislingobrien package immediately using the command npm uninstall aislingobrien and look for alternative packages.
Yes, you can use Vulert, which monitors 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 this vulnerability without needing to sign up.
