Malicious Code Injection in surya-mieaceh40-breki: A Threat to npm Packages
Summary
MAL-2025-75535: Malicious code in surya-mieaceh40-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-mieaceh40-breki' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to generate and publish derivative packages with randomized names, aimed at inflating developer reputation scores for token rewards. Its functionality is compromised by malicious scripts that alter package metadata.
Vulnerability Detail
The vulnerability in 'surya-mieaceh40-breki' originates from malicious code embedded within the package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall surya-mieaceh40-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-mieaceh40-breki' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time without requiring code access.
Conclusion
The 'surya-mieaceh40-breki' package poses a significant security risk due to its malicious code that alters package metadata and repackages it. It is crucial for developers to remove this package from their projects and monitor their dependencies for vulnerabilities using tools like Vulert. Staying informed and proactive can help mitigate potential security threats.
See every vulnerability recorded for surya-mieaceh40-breki →
FAQ
The main issue is the presence of malicious code that modifies package metadata and repackages it, leading to potential security risks.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
If you have installed the package, you should uninstall it immediately using 'npm uninstall surya-mieaceh40-breki' and look for alternatives.
While specific alternatives depend on your use case, consider searching npm for similar packages that do not have known vulnerabilities.
Vulert uses your package-lock.json file to monitor and alert you in real-time for open-source vulnerabilities in your software, ensuring you stay informed about potential risks.
