Malicious Code Injection in surya-tempe34-breki: A Threat to npm Ecosystem
Summary
MAL-2025-75556: Malicious code in surya-tempe34-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-tempe34-breki' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This campaign has been known to flood the npm registry with packages that contain malicious scripts. These scripts are designed to manipulate package metadata and inflate developer reputation scores through the automatic generation and publication of derivative packages.
Vulnerability Detail
The vulnerability in 'surya-tempe34-breki' originates from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This not only compromises the integrity of the npm ecosystem but also poses a risk to developers who may unknowingly use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall surya-tempe34-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 measure, avoid using the 'surya-tempe34-breki' package and consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The surya-tempe34-breki package poses a significant threat to the npm ecosystem due to its malicious code that alters package metadata and floods the registry. It is crucial for developers to remove this package and monitor their applications for vulnerabilities using tools like Vulert.
See every vulnerability recorded for surya-tempe34-breki →
FAQ
The surya-tempe34-breki package contains malicious code that modifies package metadata and floods the npm registry with derivative packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
Remove the package from your project immediately and check for any updates or patches that may address the vulnerability.
Yes, consider using other reputable packages that provide similar functionalities without the associated risks.
Vulert uses your package-lock.json file to monitor and alert you in real-time for any open-source vulnerabilities in your software.
