Malicious Code Injection in sinta-serabi62-breki: A Threat to npm Ecosystem
Summary
MAL-2025-75462: Malicious code in sinta-serabi62-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 'sinta-serabi62-breki' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages with randomized names, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'sinta-serabi62-breki' originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially affecting other packages and developers by inflating reputation scores fraudulently. The malicious scripts (auto.js, autopublish.js, etc.) are designed to automate this process, making it a significant threat to the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall sinta-serabi62-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 'sinta-serabi62-breki' package in your project. Additionally, consider using a tool like Vulert to monitor your package-lock.json for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The 'sinta-serabi62-breki' package poses a significant threat to the npm ecosystem due to its malicious code that modifies package files and republish variants. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities effectively.
See every vulnerability recorded for sinta-serabi62-breki →
FAQ
The main issue is that it contains malicious code that modifies package.json files and republish variants to pollute the npm registry.
You can check your package.json and package-lock.json files for the presence of 'sinta-serabi62-breki'.
You should uninstall the package immediately using 'npm uninstall sinta-serabi62-breki' and monitor your project for any further vulnerabilities.
Yes, you can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
