Malicious Code Injection in gabisa-kopling: A Threat to npm Users
Summary
MAL-2025-171234: Malicious code in gabisa-kopling (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
gabisa-kopling is an npm package that is part of the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The presence of malicious code in this package poses a significant risk to users and the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in gabisa-kopling originates from its association with the tea.xyz token reward campaign. It contains scripts that modify the package.json file to remove private flags, change version numbers, and generate random package names. This malicious behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising user projects. The ramifications include unauthorized access to sensitive data and the potential for further exploitation of affected systems.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall gabisa-koplingIf 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 prevent the malicious scripts from executing by avoiding the installation of the gabisa-kopling package. Additionally, consider using a package-lock.json file to lock your dependencies and prevent unwanted changes.
Conclusion
The gabisa-kopling package poses a significant risk due to its malicious code designed to manipulate the npm registry. Users are advised to uninstall the package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for gabisa-kopling →
FAQ
gabisa-kopling is an npm package that is part of a campaign to manipulate developer reputation scores by flooding the npm registry with derivative packages.
The malicious code modifies your package.json file, potentially exposing your project to further vulnerabilities and unauthorized access.
You should uninstall the package immediately using 'npm uninstall gabisa-kopling' and check your project for any unauthorized changes.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json. You can check your application at Vulert Scanner without any signup.
Regularly update your dependencies, use tools like Vulert for monitoring, and review package sources before installation to ensure they are trustworthy.
