Malicious Code Injection in siska-mendut67-breki Package
Summary
MAL-2025-75494: Malicious code in siska-mendut67-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 siska-mendut67-breki package is part of the npm ecosystem, often used for various JavaScript applications. This package has been identified as part of a larger malicious campaign that aims to manipulate the npm registry by creating numerous derivative packages with randomized names. The functionality of this package is compromised due to its involvement in autopublishing scripts that inflate developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability in the siska-mendut67-breki package originates from its design to automatically generate and publish derivative packages. This malicious behavior includes modifying the package.json file to remove private flags, changing version numbers, and creating random package names. The continuous republishing of these variants leads to pollution of the npm registry, which can affect developers relying on legitimate packages and compromise the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall siska-mendut67-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 siska-mendut67-breki package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes.
Conclusion
The siska-mendut67-breki package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package and monitor their projects for any unauthorized changes. Utilizing tools like Vulert can help in maintaining the security of your applications.
See every vulnerability recorded for siska-mendut67-breki →
FAQ
siska-mendut67-breki is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.
The vulnerability can lead to the pollution of the npm registry, potentially affecting the integrity of your application and its dependencies.
You should uninstall the siska-mendut67-breki package immediately and check for any dependencies that may be affected.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
