Malicious Code Injection in sari-kacang14-breki: A Threat to npm Packages
Summary
MAL-2025-75376: Malicious code in sari-kacang14-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 'sari-kacang14-breki' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts that automate the generation and publication of derivative packages, potentially harming developers' reputations and polluting the npm registry.
Vulnerability Detail
The vulnerability in 'sari-kacang14-breki' originates from its association with malicious scripts designed to manipulate package metadata. These scripts remove private flags from package.json, alter version numbers, and create random package names, leading to the continuous republishing of these variants. This not only inflates developer reputation scores fraudulently but also compromises the integrity of the npm registry, making it difficult for developers to trust the packages they use.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall sari-kacang14-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 'sari-kacang14-breki' package and look for alternative packages that provide similar functionality without the associated risks. Always validate the source and integrity of packages before installation.
Conclusion
The 'sari-kacang14-breki' package poses a significant risk due to its malicious code designed to manipulate npm package metadata. It is crucial for developers to remove this package and monitor their dependencies to maintain the integrity of their applications.
See every vulnerability recorded for sari-kacang14-breki →
FAQ
The vulnerability can lead to the pollution of the npm registry and compromise the integrity of package management, affecting developers' ability to trust the packages they use.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.
If you have installed 'sari-kacang14-breki', you should uninstall it immediately using 'npm uninstall sari-kacang14-breki' and review your other dependencies for potential vulnerabilities.
No, there are currently no patches available for 'sari-kacang14-breki'. The best course of action is to remove the package entirely.
Regularly audit your dependencies, use tools like Vulert for monitoring vulnerabilities, and ensure you only install packages from trusted sources.
