Malicious Code Injection in joko-klanting55-breki Package
Summary
MAL-2025-73719: Malicious code in joko-klanting55-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-klanting55-breki package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises its integrity and security.
Vulnerability Detail
The vulnerability in the joko-klanting55-breki package originates from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the pollution of the npm registry. This can result in significant security risks, including unauthorized access to sensitive information and the potential for further exploitation by malicious actors.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall joko-klanting55-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 remove the joko-klanting55-breki package from your project by executing the command: npm uninstall joko-klanting55-breki. This will prevent the execution of any malicious code associated with the package until a secure version is available.
Conclusion
The joko-klanting55-breki package has been identified as containing malicious code that poses significant security risks. It is crucial to update or remove this package to protect your application from potential exploitation. Utilizing tools like Vulert can aid in monitoring and managing open-source vulnerabilities effectively.
See every vulnerability recorded for joko-klanting55-breki →
FAQ
The malicious code can lead to unauthorized modifications of your project's package.json file, potentially exposing sensitive information and allowing further exploitation.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By using the Vulert playground at Vulert Scanner, you can check if your application is affected without any signup.
Regularly auditing your dependencies and using tools like Vulert can help identify and mitigate vulnerabilities before they impact your application.
If an immediate update is not possible, consider removing the package from your project as a temporary measure to mitigate risks.
Detailed information about this vulnerability can be found in the official npm registry and security advisories related to the joko-klanting55-breki package.
