Malicious Code Injection in grainnemccarthy Package: npm Vulnerability Overview
Summary
MAL-2025-171280: Malicious code in grainnemccarthy (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The grainnemccarthy package is part of the npm ecosystem, often utilized for various JavaScript applications. It has been identified as part of a broader campaign that aims to exploit npm's package publishing system. This package, like others in the campaign, is designed to inflate developer reputation scores through the automatic generation and publication of derivative packages with randomized names.
Vulnerability Detail
The vulnerability in the grainnemccarthy package stems from its malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is part of a strategy to pollute the npm registry and manipulate developer reputation metrics. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has been flooding the npm registry with such malicious packages. The ramifications include potential security risks for applications relying on this package, as well as the degradation of the npm ecosystem's integrity.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall grainnemccarthyIf 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 workaround, you can avoid using the grainnemccarthy package altogether 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. 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 grainnemccarthy package poses significant security risks due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain the integrity of their applications.
See every vulnerability recorded for grainnemccarthy →
FAQ
The grainnemccarthy package is an npm package that has been identified as part of a malicious campaign aimed at manipulating developer reputation scores.
This vulnerability can lead to security risks, including the potential for your application to be associated with malicious activities and the degradation of the npm ecosystem.
You should uninstall the grainnemccarthy package immediately and look for alternative packages that do not have these vulnerabilities.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.
You can check your application for vulnerabilities using the Vulert playground at Vulert Scanner without needing to sign up.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
