Malicious Code Injection in seblakkuah25 Package: A Threat to npm Users
Summary
MAL-2025-108462: Malicious code in seblakkuah25 (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 seblakkuah25 package 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 floods the npm registry with harmful packages. Its primary function appears to be related to the tea.xyz token reward system, which incentivizes the creation of numerous derivative packages to inflate developer reputation scores. The malicious nature of this package poses significant risks to developers and their projects.
Vulnerability Detail
The vulnerability in the seblakkuah25 package originates from its design to automatically generate and publish derivative packages with randomized names. This is achieved through scripts that modify the package.json file, removing private flags and altering version numbers. The continuous republishing of these variants leads to pollution of the npm registry, making it difficult for developers to trust the integrity of packages. The malicious payload can compromise the security of applications that depend on this package, potentially leading to unauthorized access or data breaches.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall seblakkuah25If 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 measure, avoid using the seblakkuah25 package and monitor your project for any dependencies that may inadvertently include it. Regularly audit your npm packages using tools like npm audit to identify and address vulnerabilities.
Conclusion
The seblakkuah25 package poses a significant threat to npm users due to its malicious code designed to manipulate package integrity and inflate developer reputation scores. It is crucial to remove this package from your projects and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for seblakkuah25 →
FAQ
The seblakkuah25 package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the creation of numerous derivative packages.
The vulnerability can lead to the pollution of the npm registry, making it difficult to trust the integrity of packages and potentially compromising the security of your application.
You should uninstall the seblakkuah25 package immediately using the command npm uninstall seblakkuah25 and check your project for any dependencies that may include it.
You can use tools like npm audit to regularly check your project for vulnerabilities. Additionally, Vulert can monitor your package-lock.json file for real-time alerts on open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
