Malicious Code Injection in seblakkuah30: A Threat to npm Ecosystem
Summary
MAL-2025-108468: Malicious code in seblakkuah30 (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 package 'seblakkuah30' is part of a series of malicious npm packages associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to modify critical files and republish variants, thereby polluting the npm registry.
Vulnerability Detail
The vulnerability in 'seblakkuah30' originates from its design to execute autopublish scripts that alter the package.json file. This includes removing private flags, changing version numbers, and generating random package names. The continuous republishing of these variants can lead to a cluttered npm registry, making it difficult for developers to find legitimate packages. The malicious payload poses a risk of reputation damage and potential security breaches for developers who inadvertently use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall seblakkuah30If 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, avoid using the 'seblakkuah30' package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your dependencies using tools like npm audit to identify and mitigate vulnerabilities.
Conclusion
The 'seblakkuah30' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package files and republish variants. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for seblakkuah30 →
FAQ
The main issue is that it contains malicious code designed to modify package.json files and republish variants, which can lead to npm registry pollution.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit the Vulert playground at Vulert Scanner to check your application without any signup.
If you have installed seblakkuah30, you should uninstall it immediately using 'npm uninstall seblakkuah30' and review your project's dependencies for any other malicious packages.
Yes, tools like npm audit can help identify vulnerabilities in your dependencies, and Vulert can provide real-time monitoring for open-source vulnerabilities.
Using compromised packages can lead to security breaches, reputation damage, and difficulties in maintaining a clean and reliable codebase.
