Malicious Code Injection in surya-getuk58-breki: A Threat to npm Ecosystem
Summary
MAL-2025-75518: Malicious code in surya-getuk58-breki (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 package 'surya-getuk58-breki' is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. This behavior aims to inflate developer reputation scores for token rewards, making it a significant concern for developers relying on npm for package management.
Vulnerability Detail
The vulnerability in 'surya-getuk58-breki' originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of other packages. The malicious scripts included in the package (auto.js, autopublish.js, etc.) are designed to automate this process, making it difficult for developers to detect and mitigate the issue.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall surya-getuk58-brekiIf 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 'surya-getuk58-breki' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.
Conclusion
The 'surya-getuk58-breki' package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. Developers should take immediate action to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can enhance security by providing real-time alerts for open-source vulnerabilities.
See every vulnerability recorded for surya-getuk58-breki →
FAQ
The main issue is that it contains malicious code that modifies package.json files and floods the npm registry with derivative packages.
You can use Vulert to check your package-lock.json for vulnerabilities without needing to install any software. Visit Vulert Scanner for more information.
You should uninstall the package immediately using 'npm uninstall surya-getuk58-breki' and review your project for any potential impacts.
Yes, consider looking for other npm packages that provide similar functionality but do not have a history of malicious behavior.
Regularly update your dependencies, monitor your package-lock.json with tools like Vulert, and review package sources before installation.
