Malicious Code Injection in surya-lupis99-breki: A Threat to npm Packages
Summary
MAL-2025-75532: Malicious code in surya-lupis99-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-lupis99-breki' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts that manipulate package metadata and publish numerous variants to inflate developer reputation scores.
Vulnerability Detail
The vulnerability in 'surya-lupis99-breki' stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants, leading to pollution of the npm registry. This not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these tainted packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall surya-lupis99-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-lupis99-breki' package and look for alternative packages that provide similar functionality without the associated risks. Always validate the source and reputation of packages before including them in your project.
Conclusion
The 'surya-lupis99-breki' package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to be vigilant, remove affected packages, and utilize tools like Vulert to monitor for vulnerabilities in their projects.
See every vulnerability recorded for surya-lupis99-breki →
FAQ
The main issue is that it contains malicious code that modifies package metadata and floods the npm registry with derivative packages.
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.
If you have installed the package, you should uninstall it immediately using 'npm uninstall surya-lupis99-breki' and review your dependencies for any other potential vulnerabilities.
Yes, there are many alternative packages available in the npm registry. Always ensure to check the credibility and reviews of these packages before use.
To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay informed about security advisories related to the packages you use.
