Malicious Code Vulnerability in cormackelly Package: Exploitation of npm Registry
Summary
MAL-2025-171067: Malicious code in cormackelly (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 cormackelly package is part of the npm ecosystem, which is widely used for JavaScript package management. It is often utilized by developers to manage dependencies in their projects. However, this package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. This vulnerability poses a significant risk to developers and users relying on the integrity of npm packages.
Vulnerability Detail
The vulnerability originates from the cormackelly package being associated with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts that modify the package.json file, removing private flags and changing version numbers. They generate random package names and continuously republish variants, leading to pollution of the npm registry. This not only compromises the integrity of the npm ecosystem but also exposes developers to potential security risks and reputation damage.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall cormackellyIf 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 cormackelly package and any packages that are part of the tea.xyz token reward campaign. Additionally, consider using a tool 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 cormackelly package poses a significant risk due to its association with a malicious campaign aimed at manipulating the npm registry. Developers should take immediate action to remove this package and utilize monitoring tools like Vulert to safeguard their projects against potential vulnerabilities.
See every vulnerability recorded for cormackelly →
FAQ
The cormackelly package is an npm package used for managing dependencies in JavaScript projects, but it has been identified as part of a malicious campaign.
The vulnerability can lead to the pollution of the npm registry, compromising the integrity of your dependencies and potentially exposing your project to security risks.
You should remove the cormackelly package from your project and monitor for any updates or patches that may be released.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
