Malicious Code Injection in siska-liwet9-breki Package: A Threat to npm Users
Summary
MAL-2025-75488: Malicious code in siska-liwet9-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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The siska-liwet9-breki package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary function of this package is to serve as a tool for developers, but it has been compromised to include harmful scripts that can affect the integrity of the npm registry and the applications that depend on it.
Vulnerability Detail
The vulnerability in the siska-liwet9-breki package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, which leads to the continuous republishing of variants. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which incentivizes the creation of derivative packages to inflate developer reputation scores. The ramifications include potential pollution of the npm registry and risks to applications that rely on this package, as it can lead to unauthorized access and manipulation of project dependencies.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall siska-liwet9-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-liwet9-breki package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using npm audit to check for vulnerabilities in your project dependencies.
Conclusion
The siska-liwet9-breki package poses a significant risk to npm users due to its malicious code that alters project dependencies. It is crucial to remove this package from your projects and monitor for any potential vulnerabilities using tools like Vulert. By staying informed and proactive, you can protect your applications from such threats.
See every vulnerability recorded for siska-liwet9-breki →
FAQ
The siska-liwet9-breki package is an npm package that has been compromised to include malicious code aimed at manipulating the npm registry.
The malicious code modifies your package.json file, potentially leading to unauthorized changes in your project dependencies and affecting the integrity of your application.
You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.
If you have installed the siska-liwet9-breki package, you should uninstall it immediately using the command: npm uninstall siska-liwet9-breki.
Yes, tools like Vulert can help monitor your project for vulnerabilities in real-time using just the package-lock.json file.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
