Malicious Code Injection in joko-mangut55-breki: A Threat to npm Ecosystem
Summary
MAL-2025-73738: Malicious code in joko-mangut55-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 package 'joko-mangut55-breki' is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate npm's publishing system by creating numerous derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for rewards, posing a significant risk to the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'joko-mangut55-breki' stems from its inclusion in a malicious campaign that utilizes autopublish scripts to modify package.json files. These scripts remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants that pollute the npm registry. This not only compromises the security of the affected package but also affects the overall trustworthiness of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall joko-mangut55-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 restrict the use of this package by using npm's package-lock.json to prevent it from being installed. You can also monitor your dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time without requiring code access or installation. To check if your application is affected, visit the Vulert playground at https://vulert.com/scanner.
Conclusion
The 'joko-mangut55-breki' package poses a significant threat due to its malicious code designed to manipulate npm's publishing system. It is essential to remove this package from your projects and monitor your dependencies for similar vulnerabilities. Utilizing tools like Vulert can enhance your security posture by providing real-time alerts for open-source vulnerabilities.
See every vulnerability recorded for joko-mangut55-breki →
FAQ
The main risk is that it can modify your project's package.json file, leading to unauthorized changes and potential security vulnerabilities.
You can check your package.json and package-lock.json files for any references to 'joko-mangut55-breki'.
You should immediately uninstall the package using 'npm uninstall joko-mangut55-breki' and check for any unauthorized changes in your project.
Yes, tools like Vulert can help monitor your dependencies for vulnerabilities in real-time.
Regularly audit your dependencies and use tools like Vulert to stay informed about potential vulnerabilities in your packages.
