Malicious Code Injection in joko-tempe90-breki: A Threat to npm Ecosystem
Summary
MAL-2025-73790: Malicious code in joko-tempe90-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-tempe90-breki' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. It is designed to facilitate the automatic generation and publication of derivative packages. This functionality is exploited to inflate developer reputation scores for token rewards, making it a target for malicious activities.
Vulnerability Detail
The vulnerability in 'joko-tempe90-breki' originates from its inclusion in a campaign that floods the npm registry with malicious packages. The package contains scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the integrity of the ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall joko-tempe90-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-tempe90-breki' package from your project by executing the command: 'npm uninstall joko-tempe90-breki'. This will prevent any malicious scripts from executing until a patch is available.
Conclusion
The 'joko-tempe90-breki' package poses a significant risk due to its malicious code that alters package configurations and floods the npm registry. It is crucial to take immediate action by updating or removing the package to safeguard your projects and maintain the integrity of the npm ecosystem.
See every vulnerability recorded for joko-tempe90-breki →
FAQ
The impact includes potential pollution of the npm registry and compromise of developer reputation scores, leading to a loss of trust in the ecosystem.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
If immediate updates are not possible, consider removing the package as a temporary measure to mitigate risks.
Yes, tools like Vulert can monitor your package-lock.json file to alert you in real-time for open-source vulnerabilities.
Regularly update your dependencies, use automated vulnerability scanning tools, and review package sources before installation.
