Malicious Code Injection in kurnia-klanting66-breki Package
Summary
MAL-2025-73952: Malicious code in kurnia-klanting66-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 kurnia-klanting66-breki package is part of the npm ecosystem, primarily used for JavaScript development. It is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious packages that flood the npm registry. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing significant risks to developers and their projects.
Vulnerability Detail
The vulnerability in the kurnia-klanting66-breki package stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to continuously republish variants of the package, polluting the npm registry and potentially compromising other projects that depend on it. The origin of this vulnerability is tied to the tea.xyz token reward campaign, which incentivizes the creation of such malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall kurnia-klanting66-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 kurnia-klanting66-breki package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for any unauthorized changes to package.json and other critical files.
Conclusion
The kurnia-klanting66-breki package poses a significant risk due to its malicious code that alters package metadata and repopulates the npm registry with harmful variants. It is essential to remove this package from your projects and monitor for any unauthorized changes. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for kurnia-klanting66-breki →
FAQ
It is an npm package linked to the tea.xyz token reward campaign, often used in JavaScript development.
The vulnerability can lead to unauthorized modifications of your package metadata, potentially compromising your project's integrity and security.
You should uninstall the kurnia-klanting66-breki package immediately and check for any unauthorized changes in your project.
Yes, tools like Vulert can monitor your package-lock.json file for 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 signing up.
