Malicious Code Injection in joni-keripik79-breki: A Threat to npm Users
Summary
MAL-2025-73803: Malicious code in joni-keripik79-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 joni-keripik79-breki is part of a broader campaign targeting npm users, where malicious packages are created to exploit the npm registry. These packages are often linked to token reward schemes that incentivize developers to inflate their reputation scores. The joni-keripik79-breki package specifically modifies essential files like package.json, making it a significant threat to developers relying on npm for package management.
Vulnerability Detail
The vulnerability in joni-keripik79-breki stems from its design to execute malicious scripts that alter the package.json file. This includes removing private flags, changing version numbers, and generating random package names, which can lead to the proliferation of derivative packages in the npm registry. The origin of this vulnerability is tied to the tea.xyz token reward campaign, which encourages the creation of such malicious packages to manipulate developer reputation scores. The ramifications include potential exposure of sensitive data, pollution of the npm registry, and a compromised development environment.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall joni-keripik79-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 prevent the execution of the malicious scripts by avoiding the installation of the joni-keripik79-breki package and monitoring your package.json file for unauthorized changes. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities.
Conclusion
The joni-keripik79-breki package poses a significant threat to npm users due to its malicious design aimed at manipulating the npm registry. It is essential to remove this package and monitor your project for any unauthorized changes. Utilizing tools like Vulert can help in maintaining the security of your open-source dependencies.
See every vulnerability recorded for joni-keripik79-breki →
FAQ
joni-keripik79-breki is an npm package that has been identified as malicious, designed to exploit the npm registry and manipulate developer reputation scores.
The vulnerability can lead to unauthorized modifications of your package.json file, potentially exposing sensitive data and polluting the npm registry with malicious packages.
If you have installed joni-keripik79-breki, it is crucial to remove it immediately and monitor your project for any unauthorized changes.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay informed about known vulnerabilities in the packages you use.
