Malicious Code Injection in Joko-Jus23-Breki Package: A Threat to NPM Users
Summary
MAL-2025-73706: Malicious code in joko-jus23-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-Jus23-Breki package is part of the npm ecosystem, often utilized for various JavaScript applications. However, it has been identified as part of a malicious campaign that aims to exploit npm's package publishing system. This package is linked to the tea.xyz token reward scheme, which has been associated with the automatic generation and publication of derivative packages that can mislead developers and inflate reputation scores.
Vulnerability Detail
The vulnerability in the Joko-Jus23-Breki package stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to continuously republish variants of the package, polluting the npm registry and potentially compromising the integrity of other packages. The origin of this vulnerability is traced back to a campaign that floods npm with such malicious packages, making it crucial for developers to be vigilant.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall joko-jus23-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-Jus23-Breki package and look for alternative packages that provide similar functionality without the associated risks. Always verify the source and integrity of packages before including them in your project.
Conclusion
The Joko-Jus23-Breki package poses a significant risk due to its malicious code that alters package metadata and repopulates the npm registry with potentially harmful variants. Developers are advised to remove this package and monitor their dependencies closely to maintain the security of their applications.
See every vulnerability recorded for joko-jus23-breki →
FAQ
The Joko-Jus23-Breki package is an npm package that has been identified as part of a malicious campaign aimed at exploiting the npm registry.
This vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your application and other packages.
If you have the Joko-Jus23-Breki package installed, you should uninstall it immediately and look for alternative packages.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
