Malicious Code Injection in putra-kacang26-breki: A Threat to npm Packages
Summary
MAL-2025-74927: Malicious code in putra-kacang26-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 'putra-kacang26-breki' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. It is designed to generate and publish derivative packages with randomized names, which can inflate developer reputation scores for token rewards. This package is particularly vulnerable due to its malicious payload that modifies essential files like package.json.
Vulnerability Detail
The vulnerability originates from the malicious design of the 'putra-kacang26-breki' package, which includes scripts that automatically publish variants of itself with altered package names and version numbers. This behavior can lead to the pollution of the npm registry, making it difficult for developers to find legitimate packages. The payload also removes private flags from package.json, potentially exposing sensitive information.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall putra-kacang26-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 prevent the installation of this malicious package by using npm's 'no-optional' flag when installing other packages: 'npm install --no-optional'. This will help avoid inadvertently installing packages that may depend on 'putra-kacang26-breki'.
Conclusion
The 'putra-kacang26-breki' package poses a significant threat due to its malicious code that alters package files and floods the npm registry. It is essential to remove this package and monitor your dependencies for any vulnerabilities to maintain the integrity of your software.
See every vulnerability recorded for putra-kacang26-breki →
FAQ
The malicious code can lead to the pollution of the npm registry, making it harder for developers to find legitimate packages and potentially exposing sensitive information.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By using the Vulert playground, you can check if your application is affected without any signup.
You should uninstall the package immediately using 'npm uninstall putra-kacang26-breki' and check your package-lock.json for any references to it.
As of now, there are no patched versions available. It is recommended to remove the package entirely.
Vulert uses your package-lock.json to monitor and alert you in real-time for open-source vulnerabilities, ensuring your application remains secure.
