Malicious Code Vulnerability in ciarabyrne Package
Summary
MAL-2025-171040: Malicious code in ciarabyrne (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 ciarabyrne package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit npm's publishing mechanisms. It is designed to generate and publish derivative packages with randomized names, thereby inflating developer reputation scores for token rewards associated with the tea.xyz protocol. The functionality of ciarabyrne is compromised, making it a potential risk for developers and users relying on npm packages.
Vulnerability Detail
The vulnerability in the ciarabyrne package originates from its association with the tea.xyz token reward campaign. It contains malicious code that modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants that pollute the npm registry, posing a risk of dependency confusion and potential exploitation of applications relying on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ciarabyrneIf 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 ciarabyrne package and replace it with a trusted alternative. Additionally, you can monitor your package-lock.json file for any unauthorized changes or additions that may indicate the presence of malicious packages.
Conclusion
The ciarabyrne package poses a significant risk due to its malicious code that alters package metadata and repopulates the npm registry with harmful variants. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to ensure the security of their applications.
See every vulnerability recorded for ciarabyrne →
FAQ
The ciarabyrne package is an npm package that has been identified as part of a malicious campaign to exploit npm's publishing mechanisms.
The vulnerability can lead to dependency confusion, where malicious packages may be installed unintentionally, potentially compromising your application's security.
If you have installed ciarabyrne, you should uninstall it immediately and check for any dependencies that may rely on it.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application using the Vulert playground at Vulert Scanner.
To prevent similar vulnerabilities, regularly audit your dependencies, use trusted packages, and monitor for updates and security advisories.
