Malicious Code Injection in surya-sasag59-breki: A Threat to npm Ecosystem
Summary
MAL-2025-75547: Malicious code in surya-sasag59-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-sasag59-breki' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate automatic publishing of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as malicious due to its ability to modify package metadata and republish variants, thereby polluting the npm registry.
Vulnerability Detail
The vulnerability originates from the malicious intent behind the package, which includes scripts that alter the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior can lead to the proliferation of unwanted packages in the npm registry, potentially compromising the integrity of the ecosystem and affecting developers who rely on these packages for their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall surya-sasag59-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 remove the package from your project by executing 'npm uninstall surya-sasag59-breki'. This will prevent any malicious scripts from executing until a proper fix is applied.
Conclusion
The surya-sasag59-breki package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry with unwanted variants. It is crucial for developers to stay informed about such vulnerabilities and take necessary actions to protect their projects.
See every vulnerability recorded for surya-sasag59-breki →
FAQ
The vulnerability involves malicious code that modifies package metadata and publishes unwanted variants to the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
Using this package can lead to the pollution of the npm registry and may compromise the integrity of your project by introducing unwanted or malicious dependencies.
It is advisable to check for updates regularly. You can run 'npm update surya-sasag59-breki' to ensure you have the latest version.
As a temporary measure, you can uninstall the package using 'npm uninstall surya-sasag59-breki' to prevent any malicious activity.
