Malicious Code Injection in gacorkangsss Package - npm Vulnerability
Summary
MAL-2025-103013: Malicious code in gacorkangsss (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 gacorkangsss package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and distribution of JavaScript applications. However, it has been identified as part of a malicious campaign that aims to manipulate the npm registry by publishing numerous derivative packages with altered metadata, thereby inflating developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability in the gacorkangsss package stems from its association 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 these variants, which pollutes the npm registry and can potentially compromise the integrity of applications relying on these packages. The malicious code is designed to execute autopublish scripts that automate the creation and distribution of these harmful packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall gacorkangsssIf 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 gacorkangsss package and any other packages that may be part of the same malicious campaign. Regularly audit your package-lock.json file to identify and remove any suspicious packages.
Conclusion
The gacorkangsss package poses a significant risk due to its malicious behavior of altering package metadata and flooding the npm registry. It is essential to remove this package from your project and regularly audit your dependencies to maintain the security of your applications.
See every vulnerability recorded for gacorkangsss →
FAQ
The gacorkangsss package is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.
This vulnerability can compromise the integrity of your application by introducing malicious code that alters package metadata and floods the npm registry with harmful variants.
You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without needing to sign up.
If you have installed the gacorkangsss package, you should uninstall it immediately using the command npm uninstall gacorkangsss.
There are no patches available for the gacorkangsss package, as it is recommended to remove it entirely from your project.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
