Malicious Code Injection in joko-sego57-breki Package - npm Vulnerability
Summary
MAL-2025-73777: Malicious code in joko-sego57-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-sego57-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 the security of the npm registry.
Vulnerability Detail
The vulnerability originates from the malicious scripts embedded within the joko-sego57-breki package. These scripts are designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can potentially harm developers by inflating reputation scores fraudulently. The malicious payload can also expose users to further security risks if they inadvertently use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall joko-sego57-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-sego57-breki package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your npm packages using tools like npm audit to identify and mitigate vulnerabilities.
Conclusion
The joko-sego57-breki package has been identified as containing malicious code that poses significant risks to developers and the integrity of the npm registry. It is essential to remove this package from your projects and stay vigilant by using tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for joko-sego57-breki →
FAQ
The impact includes potential exposure to malicious code, pollution of the npm registry, and fraudulent inflation of developer reputation scores.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit the Vulert playground at Vulert Scanner to check your application without requiring any signup.
If you have used the compromised package, you should uninstall it immediately and audit your project for any other vulnerable packages.
Yes, tools like npm audit and Vulert can help you identify and manage vulnerabilities in your npm packages.
While npm packages can be safe, it is crucial to regularly audit and monitor them for vulnerabilities, as malicious packages can occasionally be published.
