Malicious Code Injection in seblakkuah11 Package - npm Vulnerability
Summary
MAL-2025-108448: Malicious code in seblakkuah11 (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 seblakkuah11 package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores in exchange for token rewards. However, it has been identified as containing malicious code that alters its own package.json file and republishes variants to pollute the npm registry.
Vulnerability Detail
The vulnerability in the seblakkuah11 package stems from its malicious payload that modifies the package.json file to remove private flags, changes version numbers, and generates random package names. This behavior is intended to create numerous derivative packages that can mislead developers and compromise the integrity of the npm registry. The origin of this vulnerability is linked to a broader campaign that exploits npm's publishing capabilities to manipulate developer reputation scores.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall seblakkuah11If 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 workaround, you can avoid using the seblakkuah11 package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your npm packages for vulnerabilities using tools like npm audit.
Conclusion
The seblakkuah11 package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry with derivative packages. It is crucial to remove this package from your projects and utilize tools to monitor for vulnerabilities to maintain the integrity of your software.
See every vulnerability recorded for seblakkuah11 →
FAQ
The seblakkuah11 package is an npm package that is part of a token reward campaign and is designed to generate and publish derivative packages automatically.
The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project's dependencies, potentially introducing malicious code.
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.
You should uninstall the seblakkuah11 package immediately using the command 'npm uninstall seblakkuah11' to mitigate the risk of malicious code execution.
Yes, tools like npm audit and Vulert can help you identify and manage vulnerabilities in your npm packages effectively.
