Malicious Code Injection in seblakkuah7 Package: A Threat to npm Ecosystem
Summary
MAL-2025-108480: Malicious code in seblakkuah7 (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 seblakkuah7 package is part of the npm ecosystem and appears to be associated with the tea.xyz token reward campaign. This package is designed to automate the generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. Its functionality is compromised by malicious scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability originates from the seblakkuah7 package, which contains malicious code that 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 dependent applications. The malicious payload can affect developers by inflating reputation scores fraudulently and may lead to security risks for applications relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall seblakkuah7If 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, you can avoid using the seblakkuah7 package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes.
Conclusion
The seblakkuah7 package poses a significant threat to the npm ecosystem due to its malicious code that alters package metadata and repopulates the registry with potentially harmful variants. It is essential for developers to take immediate action to remove this package and monitor their projects for vulnerabilities.
See every vulnerability recorded for seblakkuah7 →
FAQ
The seblakkuah7 package is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated publishing of derivative packages.
The vulnerability can lead to the pollution of the npm registry, potentially introducing malicious code into your application and compromising its security.
You should immediately uninstall the seblakkuah7 package and monitor your project for any unauthorized changes. Consider using alternative packages.
Yes, you can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
