Malicious Code Injection in iwan-tempe64-breki: A Threat to npm Ecosystem
Summary
MAL-2025-73608: Malicious code in iwan-tempe64-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 'iwan-tempe64-breki' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior not only clutters the npm registry but also poses a significant security risk to developers and their applications.
Vulnerability Detail
The vulnerability in 'iwan-tempe64-breki' originates from its malicious intent to modify the package.json file by removing private flags and altering version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants. This can lead to the pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially introducing security risks into their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall iwan-tempe64-breki
If 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
Currently, there are no specific workarounds to mitigate the effects of this vulnerability other than removing the affected package. Ensure to monitor your dependencies regularly and avoid using packages with suspicious origins.
Conclusion
The 'iwan-tempe64-breki' package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying package files and flooding the registry with unwanted packages. It is crucial for developers to remove this package and monitor their dependencies to maintain the integrity and security of their applications.
See every vulnerability recorded for iwan-tempe64-breki →
FAQ
The main risk is that it modifies your package.json file, potentially introducing vulnerabilities and cluttering the npm registry with malicious packages.
You can use Vulert, which monitors open-source vulnerabilities in your software. By simply using your package-lock.json file, you can check for vulnerabilities without any installation.
You should uninstall the package immediately using 'npm uninstall iwan-tempe64-breki' to prevent any potential security risks.
As of now, there are no patched versions available. It is recommended to remove the package until a secure version is released.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by vulnerabilities without needing to sign up.