Malicious Code Injection in cormacflynn Package: A Threat to npm Users
Summary
MAL-2025-171066: Malicious code in cormacflynn (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 cormacflynn package is part of the npm ecosystem, primarily used for JavaScript development. It is often leveraged by developers to manage dependencies in their projects. However, this package has been identified as part of a malicious campaign that floods the npm registry with harmful scripts designed to manipulate package metadata and inflate developer reputation scores.
Vulnerability Detail
The vulnerability stems from the cormacflynn package being associated with a malicious campaign that 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, which pollutes the npm registry and can compromise the integrity of projects relying on this package. The malicious payload is designed to exploit the npm ecosystem, making it a significant threat to developers and their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall cormacflynnIf 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 cormacflynn package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities in real-time. 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 cormacflynn package poses a significant risk to developers using npm. It is essential to remove this package from your projects and monitor for any vulnerabilities using tools like Vulert. By staying informed and proactive, you can protect your applications from malicious threats.
See every vulnerability recorded for cormacflynn →
FAQ
The cormacflynn package is a JavaScript package available on npm, which has been identified as part of a malicious campaign to manipulate package metadata.
This vulnerability can lead to the pollution of the npm registry and compromise the integrity of your project by introducing malicious code.
You should uninstall the cormacflynn package immediately using the command npm uninstall cormacflynn.
Yes, tools like Vulert can help monitor your project for open-source vulnerabilities in real-time using just the package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
