Malicious Code Injection in siska-liwet99-breki: A Threat to npm Packages
Summary
MAL-2025-75489: Malicious code in siska-liwet99-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 'siska-liwet99-breki' is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package lies in its ability to modify critical files and republish variants, thereby polluting the npm registry.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded within the 'siska-liwet99-breki' package. This payload alters the package.json file by removing private flags and changing version numbers, allowing the package to be republished with randomized names. The intent behind this is to exploit the npm registry by flooding it with numerous variants of the package, which can lead to confusion among developers and potential security risks. The package is part of a broader scheme associated with the tea.xyz token reward campaign, which aims to manipulate developer reputation scores.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall siska-liwet99-breki
If 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-liwet99-breki' package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which can alert you to any open-source vulnerabilities in real-time.
Conclusion
The 'siska-liwet99-breki' package poses a significant threat due to its malicious code designed to manipulate the npm registry. It is essential for developers to be vigilant and remove such packages from their projects to maintain the integrity of their applications. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.
See every vulnerability recorded for siska-liwet99-breki →
FAQ
The 'siska-liwet99-breki' package is an npm package that has been identified as malicious, designed to manipulate the npm registry by flooding it with derivative packages.
This vulnerability can lead to confusion and potential security risks as it modifies critical files and repopulates the npm registry with malicious variants.
You should uninstall the 'siska-liwet99-breki' package immediately and monitor your project for any further vulnerabilities.
Yes, you can use tools like Vulert, which allows you to monitor and alert for open-source vulnerabilities in your software without requiring access to the code.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.