Malicious Code Injection in surya-sate82-breki: A Threat to npm Packages
Summary
MAL-2025-75549: Malicious code in surya-sate82-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-sate82-breki' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages with randomized names, aimed at inflating developer reputation scores for token rewards. The malicious nature of this package lies in its ability to alter package metadata and continuously republish variants, thereby polluting the npm registry.
Vulnerability Detail
The vulnerability in 'surya-sate82-breki' originates from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, which can lead to a significant pollution of the npm registry. This not only affects the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these compromised packages. The malicious payload is designed to execute autopublish scripts that facilitate the continuous republishing of these altered packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall surya-sate82-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-sate82-breki' package altogether. If you have dependencies that require it, consider replacing them with alternative packages that do not have known vulnerabilities.
Conclusion
The 'surya-sate82-breki' package poses a significant threat due to its malicious code that alters package metadata and repopulates the npm registry with compromised versions. It is crucial for developers to remove this package and monitor their projects for vulnerabilities using tools like Vulert.
See every vulnerability recorded for surya-sate82-breki →
FAQ
The main issue is that it contains malicious code that modifies package metadata and republish variants, leading to npm registry pollution.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.
You should uninstall the package immediately using 'npm uninstall surya-sate82-breki' and look for alternative packages.
Currently, there is no patched version available. It is recommended to remove the package until a fix is released.
Using this package can lead to the exposure of your project to malicious code, affecting its integrity and security.
