Malicious Code Injection in joko-lapis67-breki Package
Summary
MAL-2025-73729: Malicious code in joko-lapis67-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-lapis67-breki package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to manipulate the npm registry by creating numerous derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, making them a significant threat to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability stems from the malicious code embedded within the joko-lapis67-breki package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which leads to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also poses risks to developers who may unknowingly use these compromised packages, potentially leading to security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall joko-lapis67-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-lapis67-breki package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The joko-lapis67-breki package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers and their applications. It is vital to take immediate action by removing the package and monitoring for any vulnerabilities in your projects. Utilizing tools like Vulert can aid in maintaining the security of your software.
See every vulnerability recorded for joko-lapis67-breki →
FAQ
The malicious code can lead to the pollution of the npm registry and may compromise the security of applications that use this package.
You can check your package-lock.json file or use tools like Vulert to monitor your project for vulnerabilities.
Regularly audit your dependencies and use tools that monitor for vulnerabilities, such as Vulert.
Uninstall the package immediately and check your project for any potential security issues that may have arisen from its use.
While many packages are trustworthy, it is crucial to regularly audit and monitor your dependencies for vulnerabilities.
