Malicious Code Injection in joko-botok43-breki Package
Summary
MAL-2025-73680: Malicious code in joko-botok43-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 joko-botok43-breki package is part of the npm ecosystem, often associated with token reward campaigns. It is designed to facilitate the automatic generation and publication of derivative packages. However, this package has been identified as malicious, containing scripts that manipulate package metadata and flood the npm registry with unwanted variants.
Vulnerability Detail
The vulnerability originates from the package's malicious scripts, which modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior is intended to inflate developer reputation scores for token rewards, leading to pollution of the npm registry and potential security risks for users who inadvertently install these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall joko-botok43-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 joko-botok43-breki package and monitor your dependencies for any malicious activity. Regularly audit your npm packages using the command: npm audit.
Conclusion
The joko-botok43-breki package poses significant risks due to its malicious code that alters package metadata and floods the npm registry. It is crucial to remove this package and monitor your dependencies to maintain the security of your applications.
See every vulnerability recorded for joko-botok43-breki →
FAQ
The malicious code can lead to unauthorized modifications of your project's package.json, potentially compromising your application's integrity and security.
You can use tools like Vulert to monitor your package-lock.json for vulnerabilities. Visit Vulert Scanner to check your application without any signup.
Immediately remove the joko-botok43-breki package from your project and audit your dependencies for any other vulnerabilities.
Consider using well-established and actively maintained packages that serve similar functionalities without the associated risks.
Regularly audit your dependencies, stay updated on security advisories, and use tools like Vulert for real-time monitoring of open-source vulnerabilities.
