Malicious Code Injection in seblakkuah1 Package: A Threat to npm Ecosystem
Summary
MAL-2025-108446: Malicious code in seblakkuah1 (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 seblakkuah1 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been linked to a malicious campaign aimed at inflating developer reputation scores through the tea.xyz token reward system. It is designed to automatically generate and publish derivative packages with randomized names, which can lead to pollution of the npm registry and compromise the integrity of the ecosystem.
Vulnerability Detail
The vulnerability in the seblakkuah1 package originates from its association with the tea.xyz token reward campaign. It contains malicious scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only affects the affected package but also contributes to the overall degradation of the npm registry by flooding it with numerous variants, making it difficult for developers to find legitimate packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall seblakkuah1If 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 seblakkuah1 package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project's dependencies using tools like Vulert, which can alert you to open-source vulnerabilities in real-time.
Conclusion
The seblakkuah1 package poses a significant threat to the npm ecosystem due to its malicious behavior aimed at inflating developer reputation scores. It is crucial for developers to be aware of this vulnerability, take immediate action to remove the affected package, and utilize tools like Vulert to monitor their projects for potential risks.
See every vulnerability recorded for seblakkuah1 →
FAQ
The seblakkuah1 package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through automated publishing of derivative packages.
The vulnerability can lead to the pollution of the npm registry, making it harder to find legitimate packages and potentially exposing your project to further security risks.
You should uninstall the package immediately using 'npm uninstall seblakkuah1' and look for alternative packages that do not have known vulnerabilities.
You can use Vulert to monitor your project for open-source vulnerabilities. It requires only the package-lock.json file to provide real-time alerts about any vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
