Malicious Code Injection in kurniawan-rangi23-breki: A Threat to npm Users
Summary
MAL-2025-74021: Malicious code in kurniawan-rangi23-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 kurniawan-rangi23-breki is part of a broader campaign involving the tea.xyz token reward system, which has been known to flood the npm registry with malicious packages. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior not only compromises the integrity of the npm ecosystem but also poses significant risks to developers who may unknowingly use these packages.
Vulnerability Detail
The vulnerability in kurniawan-rangi23-breki stems from its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, which can lead to the pollution of the npm registry. This behavior is part of a larger scheme to inflate developer reputation scores for token rewards, making it a serious concern for the integrity of the npm ecosystem. The package's origin is linked to a malicious campaign identified by Amazon Inspector, which highlights its potential to disrupt normal package management and usage.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall kurniawan-rangi23-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 kurniawan-rangi23-breki package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your dependencies using tools like npm audit to identify and mitigate vulnerabilities.
Conclusion
The kurniawan-rangi23-breki package poses a significant threat to npm users due to its malicious behavior aimed at manipulating the npm registry. It is essential to remove this package from your projects and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for kurniawan-rangi23-breki →
FAQ
kurniawan-rangi23-breki is an npm package that has been identified as part of a malicious campaign aimed at manipulating developer reputation scores.
Using this package can lead to the pollution of the npm registry and compromise the integrity of your project, potentially introducing security risks.
You should uninstall the package immediately using the command npm uninstall kurniawan-rangi23-breki.
Yes, tools like Vulert can monitor your package-lock.json file for open-source vulnerabilities in real-time without requiring code access.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
