Malicious Code Injection in seblakkuah24: A Threat to npm Packages
Summary
MAL-2025-108461: Malicious code in seblakkuah24 (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
seblakkuah24 is an npm package that has been identified as part of a malicious campaign targeting the npm ecosystem. This package is associated with the tea.xyz token reward initiative, which 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 manipulate package metadata and republish variants, thereby polluting the npm registry.
Vulnerability Detail
The vulnerability in seblakkuah24 originates from its design to execute autopublish scripts that alter the package.json file by removing private flags and changing version numbers. This allows the package to generate random names and continuously republish itself and its variants, leading to potential abuse of the npm registry and compromising the integrity of the ecosystem. The malicious payload can lead to unintentional exposure of sensitive information and can affect developers relying on the npm registry for legitimate packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall seblakkuah24If 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, you can avoid using the seblakkuah24 package and replace it with a trusted alternative. Additionally, regularly audit your npm packages using tools like npm audit to identify and mitigate vulnerabilities.
Conclusion
The seblakkuah24 package poses a significant threat to the npm ecosystem due to its malicious code that alters package metadata and republish variants. It is essential for developers to remove this package and monitor their projects for vulnerabilities to maintain the integrity of their applications.
See every vulnerability recorded for seblakkuah24 →
FAQ
seblakkuah24 is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through automated package publishing.
The vulnerability can lead to the pollution of the npm registry, potentially exposing your project to malicious packages and compromising its integrity.
You should uninstall the package immediately using 'npm uninstall seblakkuah24' and check your package-lock.json for any references to it.
You can use tools like npm audit or Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
