Malicious Code Injection in seblakkuah32: A Threat to npm Packages
Summary
MAL-2025-108470: Malicious code in seblakkuah32 (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 package seblakkuah32 is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This campaign has been known to flood the npm registry with packages that contain malicious scripts. These scripts are designed to automatically generate and publish derivative packages with randomized names, aimed at inflating developer reputation scores for token rewards. The presence of such malicious packages poses a significant risk to developers and users relying on npm for package management.
Vulnerability Detail
The vulnerability in seblakkuah32 originates from its malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of other packages. The malicious payload can affect developers' reputations and lead to unintended consequences in applications that rely on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall seblakkuah32If 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 seblakkuah32 package and monitor your project for any dependencies that may have been affected by this malicious code. Regularly check your package-lock.json file for any unauthorized changes.
Conclusion
The seblakkuah32 package poses a significant threat due to its malicious code that manipulates package metadata and inflates developer reputation scores. It is crucial to remove this package from your project and monitor your dependencies for any unauthorized changes. Utilizing tools like Vulert can help you stay informed about vulnerabilities in your software.
See every vulnerability recorded for seblakkuah32 →
FAQ
Seblakkuah32 is an npm package that has been identified as containing malicious code aimed at manipulating package metadata and inflating developer reputation scores.
The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project's dependencies, potentially affecting application performance and security.
You should uninstall the package immediately using 'npm uninstall seblakkuah32' and review your project for any other affected dependencies.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. Visit Vulert Scanner to check your application.
Regularly audit your dependencies, use trusted sources for packages, and keep your packages updated to their latest versions to minimize the risk of vulnerabilities.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
