Malicious Code Injection in conorniamhkellymccarthy Package: A Threat to npm Users
Summary
MAL-2025-171059: Malicious code in conorniamhkellymccarthy (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 conorniamhkellymccarthy package is part of the npm ecosystem, typically used for various JavaScript functionalities. However, it has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the tea.xyz token reward system. This package, like others in the campaign, is designed to automatically generate and publish derivative packages with altered metadata, posing significant risks to users and the integrity of the npm registry.
Vulnerability Detail
The vulnerability stems from the package's malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the security of applications that depend on this package. The origin of this issue is linked to a broader campaign that exploits npm's publishing mechanisms for fraudulent gain.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall conorniamhkellymccarthyIf 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 conorniamhkellymccarthy package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using npm audit to identify and address vulnerabilities in your dependencies.
Conclusion
The conorniamhkellymccarthy package poses a significant threat to npm users due to its malicious behavior aimed at manipulating the npm registry. It is crucial to remove this package from your projects and monitor for any updates or patches. Utilizing tools like Vulert can help you stay informed about vulnerabilities in your dependencies.
See every vulnerability recorded for conorniamhkellymccarthy →
FAQ
It is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.
The vulnerability can lead to the injection of malicious code into your application, potentially compromising its security and integrity.
You should remove the conorniamhkellymccarthy package from your project and look for alternatives. If a patched version is available, update to that version.
Yes, you can use tools like Vulert, which monitors your package-lock.json file for 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 any signup.
